Skip to content

feat(app): use the New Interface toggle for Quiet Companion #63

Closed

Description

@trmosala

What to build

Reuse OpenCode's existing persisted New Interface setting and transition behavior as the rollout boundary for Quiet Companion. When the setting is enabled, the application should select the Quiet Companion interface; when disabled, it should select the legacy interface.

This is a replacement of the existing new-interface target, not a second CookieMonster-only preference. Preserve the current persisted setting, migration behavior, shared switch control, and immediate transition between settings experiences.

The change must establish a stable presentation boundary for later Quiet Companion slices without duplicating session state or reimplementing application behavior.

Acceptance criteria

  • The existing New Interface toggle enables Quiet Companion and disables back to the legacy interface.
  • The selection persists across application reloads using the existing settings persistence mechanism.
  • Toggling either direction preserves the active server, project, session, and unsent draft.
  • Both settings surfaces display and update the same preference and transition immediately to the selected interface.
  • The legacy interface remains usable when the setting is disabled.
  • The presentation boundary can host incremental Quiet Companion slices while unfinished areas continue to use existing production behavior.
  • Unbranded OpenCode behavior is either preserved or covered by an explicit branded-product condition, with a regression test for the chosen behavior.
  • Automated tests cover persistence, both transition directions, and state preservation.

Blocked by

None — can start immediately.

Design reference

Quiet Companion is defined by the prototype introduced in commit 092adf78e7. Reuse OpenCode's existing New Interface toggle and layout-selection pattern rather than introducing a parallel toggle.

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 in local commit e85ee38db34881b8a78566d546d35aa4ab7fd114 on branch interface-toggle, based on origin/dev.

    CookieMonster's existing New layout control now selects Quiet Companion through the persisted general.newLayoutDesigns preference. Both settings surfaces and the titlebar use that selection. Existing CookieMonster Quiet Companion choices migrate into it, and switching presentation keeps the router, active session, and composer mounted. Unbranded settings behavior is preserved.

    Validation: four branded browser scenarios passed for both starting states, both switch directions, draft and session preservation, reload persistence, and both migration values. Two unbranded browser checks passed, including the existing titlebar persistence regression. All 15 settings unit tests, app typecheck, E2E typecheck, formatting, and diff checks passed. Scoped lint reported no errors and existing warnings. The migration regression was also confirmed to fail against the original implementation.

    Closing as requested after the commit. This commit is local only: it has not been pushed, merged into dev, or released. Full CI and native desktop testing were not run.

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