feat(clients): reload provider sessions per thread without restarting T3 Code - #6162
feat(clients): reload provider sessions per thread without restarting T3 Code#6162DavidIlie wants to merge 3 commits into
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ApprovabilityVerdict: Needs human review This PR introduces a new user-facing feature (reload agent session) with UI controls across mobile and web, backend decider logic changes, and contract modifications. New features introducing user-facing behavior warrant human review. You can customize Macroscope's approvability policy. Learn more. |
4b47385 to
4331b45
Compare
What changed
Provider processes load MCP servers and runtime configuration when they start. Existing threads therefore required a full T3 Code restart to pick up changes such as enabling Computer Use.
This adds Reload agent session to thread actions and the command palette on web/desktop, plus thread controls on mobile. It stops only that thread's provider process; the next message starts a new process and resumes the stored provider conversation with current configuration. Other threads and the environment keep running.
Reload reuses the existing stop/resume lifecycle and works across Codex, Claude Code, Cursor, Grok, and OpenCode. An idle-only precondition is checked atomically by the decider, so a stale client cannot interrupt a turn started elsewhere.
Closes #5437.
Screenshots
Validation
git diff --checkModel: GPT-5.6 Sol · Harness: Codex in T3 Code