Skip to content

feat(web): fork chats after agent responses - #76

Merged
adampeterhiggins merged 1 commit into
mainfrom
ah/fork-after-agent-messages
Sep 30, 2026
Merged

adampeterhiggins merged 1 commit into
mainfrom
ah/fork-after-agent-messages

Conversation

@adampeterhiggins

@adampeterhiggins adampeterhiggins commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Agent responses had no fork action, so continuing from a completed response required going back to a human message. Web and desktop now offer Fork into new tab beside a completed agent response. The new composer contains only a summary attachment covering the conversation through that response, ready for a follow-up.

The handoff API accepts an inclusive assistant-message cutoff and excludes later dialogue, tools, checkpoints, and plan updates. Human-message retries and model/account forks keep their existing behavior. Mobile continues to use its existing tab controls without message forking.

Validation: 13 focused summary and shared thread-tab API tests passed; web/server typechecks passed; targeted lint passed with existing chat-component warnings. Verified the new fork and its summary preview in the T3 Browser panel against isolated copied state.

Before After
Agent response actions before Agent response actions with fork

New tab with only the summary attachment and its preview

Evidence is uploaded to the draft PR-assets release.

Model: GPT-6.1-Sol. Harness: Codex in T3 Code.

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