Skip to content

feat(app): implement the Quiet Companion new-task flow #66

Closed

Description

@trmosala

What to build

Implement the Quiet Companion landing and new-task experience against production application state. The new interface should provide the prototype's calm landing presentation while reusing the existing prompt, model, agent, mode, attachment, draft, and session-creation behavior.

This slice must be independently demonstrable: a user can open Quiet Companion, configure and submit a real first prompt, and arrive in the created session without relying on prototype fixtures or duplicate orchestration.

Acceptance criteria

  • Quiet Companion renders a production-backed new-task landing view when no session is selected.
  • The composer uses existing model, agent, mode, attachment, and prompt submission state rather than parallel implementations.
  • Draft text and selected prompt options survive navigation and interface transitions according to existing application behavior.
  • Text input auto-resizes within a bounded height and remains usable with long prompts.
  • Empty, loading, validation, submission, and failure states are represented without trapping the user.
  • Submitting a valid prompt creates a real session and navigates to that session.
  • Repeated or interrupted submission follows existing duplicate-prevention and recovery behavior.
  • Focus order and keyboard submission behavior remain compatible with the production composer.
  • Automated tests cover landing render, option preservation, successful submission, and a failed submission.
  • The legacy interface remains unchanged while the New Interface setting is disabled.

Blocked by

Activity

  1. added
    enhancementNew feature or request
    ready-for-agentScoped work with acceptance criteria and recorded blockers
    on Oct 6, 2026
  2. trmosala commented on Oct 17, 2026

    @trmosala
    OwnerAuthor

    Implemented and verified in local commit 3d66d6530a9ffcefb8edbb65e444422450d66414 on interface-toggle.

    Quiet Companion continues to use the real production composer, options, drafts and session admission. The provider notice now participates in landing-page flow instead of covering the suggestion buttons at shorter heights.

    Checks passed for project-aware landing/suggestions, retained drafts/options across navigation and interface transitions, one saved chat after submission, and a failed first submission retaining its text/model for one explicit retry. These are real application flows against deterministic API fixtures; live WPP model inference was not exercised.

    This commit is local only: it has not been pushed, merged into dev, or released.

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 requestready-for-agentScoped work with acceptance criteria and recorded blockers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions