Skip to content

Support: server-side draft sync #46

Description

@Andreas-Froyland

Deferred from Stage 05a on 2026-08-30. See stage-05-decisions.md decision 19.

Stage 05a persists composer drafts client-side only, keyed by (conversationId, mode) so a reply draft and a note draft coexist, and restoring a draft restores its composer mode — restoring note text into a reply composer would reintroduce the note/reply confusion Stage 02 calls the highest-consequence UI bug in a support product.

Server-side sync (Front's model) makes drafts follow the agent across devices. Matters at ~20 agents on laptops and phones, not at 3. Any implementation must preserve the mode-restoration guarantee above.

Activity

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 request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions