Skip to content

fix: keep composer drafts scoped to each agent - #13

Open
agocharbhatia wants to merge 1 commit into
runta-dev:mainfrom
agocharbhatia:keep-composer-drafts-per-agent
Open

agocharbhatia wants to merge 1 commit into
runta-dev:mainfrom
agocharbhatia:keep-composer-drafts-per-agent

Conversation

@agocharbhatia

Copy link
Copy Markdown

Summary

Keep composer drafts with their agent. Switching agents currently reuses the same draft text, attachments, and pending-send state. A file picker can also finish after a switch and add its selection to the visible draft.

Draft edits and asynchronous completions now update the agent that started them. Switching back restores that agent’s draft, and a pending send does not block a different agent’s composer.

Evidence

  • The same three renderer regressions failed on base and passed with the patch.
  • npm run typecheck, npm run lint, npm test and npm run build passed locally.

Scope

The change is confined to the composer’s in-memory state for the mounted session.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant