Repository navigation
chore(agents): Captain preset follows approvals, continuations and post-merge cleanup - #254
Merged
Merged
Conversation
…st-merge cleanup Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The shipped Captain preset fell behind the user's live Captain. Its listener blocked on one
runId, so it missed command approvals and returned "completed" too early when a child resumed after background work. It also had no step for cleaning up after a merge. This PR syncs the preset with the livecaptain-event-loopskill (rev 7) and the live Captain prompt (rev 41), rewritten for any Ada user.Live vs repo
t3_thread_waiton arunId, re-waits hourlyrunId, checks for pending approvals, follows new runs throughactiveRunId, at most 240 rounds thenREARMWAITING-APPROVAL→ read the guarded command →t3_respond_to_approvalwithin scope, otherwise declineenvironmentId, falling back tot3_get_thread/t3_send_messagePushNotificationt3_reclaim_worktreedry-run then reclaim, keep shared caches, follow an existing cache-trim job instead of adding oneBLOCKED:t3_background_waitfor long waits, and norm $(...)Generalized from the live text: "JJ" → "the user", T3 → Ada, Doug/Cody/Randy → Cook/Pastry/Cleaner (already in the preset). Removed: dated
.t3/captain/retro-…evidence paths, the specific AWS profile and memory names, the npm note, Davit, and the Studio-01local.gocache-trimLaunchAgent paths, which are now the general cache-trim rule. The live skill had no Luna fallback left to remove.t3_reclaim_worktreeand the cleanup safety rules are kept word for word.The system prompt also gets one new line: "After a PR merges, run the captain-event-loop cleanup step." The user's live profile is untouched.
Checks
vp run check:changedand CI pass (one brand-name fix: a bare "t3 call" became "tool call").agentPresets.test.ts(30) doesn't pin text, so no fixtures changed.agentContextBudget.jsonis unchanged, so the agent context budget does not grow. These presets are installed library content, not built-in context.Merge risk: low. Text only, and it only affects new installs or reinstalls of the Captain preset.
🤖 Generated with Claude Code