Repository navigation
feat(server): plan mode for Scient Agent - #925
Merged
Merged
Conversation
Scient Agent now reports the prompt-cache entry each reply confirmed (tier, touch time, lifetime) on its message_end. Desktop turns a one-hour entry into promptCacheExpiresAt on the turn's token usage, the field the Claude path already fills. Idle compaction then works for Scient Agent as it does for Claude: "Before the cache expires" sends /compact two minutes before the cache lapses on a thread over 200,000 tokens, and "When you return" offers the Compact chip once the cache has expired. A five-minute entry carries no expiry, so a short pause never triggers a compaction, and a cache that never expires reports none. Scient Agent instances get the same "Compact idle threads" override as Claude ones, and the setting text names both. Agents that do not report the entry keep today's behaviour. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The event schemas dropped promptCache, so idle compaction never saw the cache expiry in the live app. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 14, 2026
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
/goal now works with Scient Agent as it does with Codex and Claude. Desktop sends it to the agent's goal command instead of refusing it: an objective sets the goal (replacing one the agent holds), and pause, resume, clear and show map to the agent's ops. The agent's goal_updated events fill the thread's goal row, so the existing goal UI shows status, tokens and time, with its Resume and Clear buttons. The agent works on an active goal in turns it starts itself. Desktop turns on goal continuation over RPC in the settings file it writes for the agent, and those turns arrive through the existing path for turns the agent began. A refused goal command (goal mode off, plan mode active) is answered in the conversation, not a failed turn. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A goal continuation is a turn the agent starts by itself. Desktop ended it as soon as the buffered wake events were replayed, so each goal turn showed "Worked for 40ms" and its reply was split across turns. The turn now stays open until the agent's own end event. The event schemas also kept dropping the goal, so the goal row never showed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/plan <task> now plans with Scient Agent before it acts. Desktop turns on the agent's new RPC plan mode and sends the task as the prompt. The agent reads and drafts a plan but changes nothing; the plan it proposes shows as the existing plan card, and its Approve / Refine question uses the existing question card. Approving lets the same turn carry out the plan. Refining makes the agent ask what to change, answered in the next message. /plan alone turns plan mode on, /plan off turns it off. Upstream T3 removed the Build/Plan toggle, so this uses the surfaces that remain (decided with a Codex consult): a provider slash command, the plan card and the question card. An agent without plan mode answers "cannot plan" instead of failing the turn. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Steering a running turn with /plan sent the text to the agent as a message, so plan mode never turned on or off. /plan now has to run as its own turn, as /goal and /compact do; the user is told to queue it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yaacovcorcos
force-pushed
the
claude/goal-mode-20261113
branch
from
November 14, 2026 18:34
afc527c to
6f588b9
Compare
yaacovcorcos
force-pushed
the
claude/plan-mode-20261113
branch
from
November 14, 2026 18:34
5de821f to
47cb592
Compare
yaacovcorcos
enabled auto-merge
November 14, 2026 18:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge order: #923 → #924 → #925 → #926, all based on
mainand queued in that order; each branch sits on the one before it, so its diff shrinks to its own change as they merge.Platforms: the same server code on macOS, Windows and Linux; no platform-specific parts. Tested live on macOS only.
What
/plan <task>now plans with Scient Agent before it acts.provider/omp/OmpPlan.ts). The agent reads and drafts a plan but changes nothing.plan_proposed) shows as the existing proposed-plan card. Its Approve / Refine question uses the existing question card./planalone turns plan mode on;/plan offturns it off./plannever steers a running turn: it has to run as its own turn, as/goaland/compactdo, and the user is told to queue it (found in Codex review)./plan, so this uses the surfaces that remain: a provider slash command, the plan card and the question card. Decided with a Codex consult (recorded in the record file).Agent side: ScientFactory/scient-agent#60 (stacked on ScientFactory/scient-agent#59).
Older agents: today's published agent (0.1.10) has no plan command. It answers "Unknown command", and Desktop shows "This Scient Agent version cannot plan. Update Scient Agent to use /plan." Nothing runs. Checked live.
T3 files change only inside SCIENT-FORK seams.
Tests
OmpPlan.test.ts:/plan <task>turns plan mode on and sends the task as the prompt;/plan off,/planalone, an agent without the command (update notice) and a refusal answer in the conversation;plan_proposeddecoding.OmpAdapterV2.test.ts"refuses to steer a running Scient Agent turn with /plan": fails without the guard.pnpm run typecheck,vp fmt --check,vp lint, seam check and provenance./plan Add a file plan-check.txt ...showed the plan card and the "Carry out the plan?" question; nothing was written before the answer; Approve created the file in the same turn. With the published 0.1.10 binary, the update notice showed and nothing ran. Not checked live: Refine. Record and screenshots:reviews/scient-agent-next-20261111/build-all-20261113/agentmodes-RECORD.mdin the ScientFactory workspace.🤖 Generated with Claude Code