Skip to content

Add tmux and PTY coverage for core Ink UI journeys #2017

Description

@acoliver

Summary

Expand the dedicated interactive UI test lane beyond slash autocomplete and one approval accept path.

Suggested coverage

  • Session browser open, navigate, search or filter, and exit.
  • Provider or model switch smoke flow.
  • Clean-runner welcome or onboarding path.
  • Tool approval deny and escape paths.
  • Terminal resize behavior.
  • Unicode or wide-character composer rendering.

Test approach

Use tmux or PTY only for behavior that needs a real terminal. Keep the lane single-platform and artifact-rich with screen, scrollback, pane output, and debug logs.

Metadata

Metadata

Assignees

Labels

Code Quality / ModularizationIssues to do with the quality of llxprt code and its maintainability.Ink UIthe packages/cli Ink based UI.

Type

Projects

Status
In Progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions