Skip to content

Roadmap: terminal-native product polish from context entry to autonomous task control #195

Open

Description

@qwen-code-dev-bot

Outcome

Evolve the CLI through a staged product-polish program, from low-friction context entry and session continuity to inspectable autonomous execution. Each stage must remain terminal-native, keyboard-first, deterministic, and evidence-backed.

Product principles

  • Reuse existing session, command, approval, evidence, and telemetry contracts instead of creating parallel state.
  • Implement capabilities independently; do not copy third-party source, branding, artwork, or interaction text.
  • Preserve user-owned Git and workspace changes. Destructive or ambiguous actions fail closed.
  • Bind behavioral evidence to the exact pull-request head SHA.
  • Keep narrow terminals, no-color mode, screen readers, and non-interactive behavior usable.

Delivery sequence

Foundation

  1. Workspace file and directory references in the composer.
  2. Interactive session discovery and exact-session resume.
  3. Local redacted session export.

Control

  1. Safe one-turn undo and redo.
  2. Side questions that do not disturb the main task.
  3. Inspectable session activity and efficiency statistics.

Advanced

  1. Workspace-bound language-server readiness and diagnostics.
  2. Background task monitoring, cancellation, and receipts.

Definition of done

Every child ships through Issue -> lease -> branch -> commits -> PR -> required checks -> head-bound terminal/tmux E2E -> merge -> post-merge dogfood -> cleanup. Completion requires real interaction evidence, no fabricated telemetry, released leases, closed labels, a clean workspace, and main equal to origin/main.

Activity

  1. added
    enhancementNew feature or request
    parentParent issue coordinating child work
    priority:p1High priority: address before normal work
    source:userNormalized execution work promoted from a user report
    on Jul 20, 2026
  2. qwen-code-dev-bot commented on Jul 20, 2026

    @qwen-code-dev-bot
    OwnerAuthor

    Child delivery queue:

    Deliver in dependency-aware order. A later child may be prepared in parallel only when it does not share runtime state or weaken the one-active-lease policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestparentParent issue coordinating child workpriority:p1High priority: address before normal worksource:userNormalized execution work promoted from a user report

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions