Skip to content

v0.9.10: make first run progressive instead of front-loading configuration #5522

Description

@Hmbown

Direct user feedback: Codewhale works and clearly has depth, but first launch has too much psychological cost. A non-English user encountered an English telemetry disclosure, then a wall of settings, key hints, and choices before reaching useful work.

Release acceptance:

  • Start in the selected or inferred locale; telemetry disclosure is localized and non-blocking.
  • Ask only for a genuinely missing decision. Preserve an existing configured route and preserve codew task input.
  • Use one question, one current answer, and one primary action per setup screen.
  • Keep advanced provider, permission, MCP, plugin, appearance, and config controls available later through focused surfaces.
  • Bare slash discovery shows a small starter set; the full command catalog remains searchable when typed.
  • Setup detects fresh, partial, complete, and broken configurations and opens the first required repair.
  • At Ready, show a compact receipt and let the user start work immediately.
  • Verify 40x12, normal, and wide terminal layouts in the real installed candidate.

Current implementation receipts on main:

  • 06c5a00: required-only onboarding and localized non-blocking telemetry
  • 83299d6: bounded starter slash menu with searchable long tail
  • a6df64a: progressive setup and real remote-control handoff

Still required before closing: final candidate Ghostty/Kimi first-run proof at the exact release SHA.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtuiTerminal UI behavior, rendering, or interactionuxUser experience, interaction, or presentation polish

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions