Repository navigation
Conversation
Reopened from pingdotgg#34628 and squashed onto current main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wSedlacek
force-pushed
the
agent/openrig-starting-maps
branch
from
November 14, 2026 22:41
b37dc02 to
5004e3f
Compare
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. |
This branch has not been deployed
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.
Problem
Agents dropped into a project often either under-orient (missing README/architecture/progress) or over-stuff the context window by loading every doc. There is no shared trailhead that says what to read first and what to do when those routes run out.
Approach
.agents/STARTING_MAP.md, thenAGENTS.md/ README / architecture / progress / area docs / roster) that returns routes only, never file contents.t3_project_orient(whoami + present routes +whenMapRunsOutguidance)..agents/STARTING_MAP.mdas the convention example.agentContextBudget.jsonfor the new tool schema and instruction line (needsagent-context-increase).Scope (approved plan)
OpenRig inspiration
OpenRig's starting map: a short trailhead (whoami → README/architecture/progress → area docs) plus explicit "when the map runs out" (search, roster, report missing route) for minimum viable competence without filling the window.
Test plan
vp test run apps/server/src/project/StartingMap.test.tsvp test run apps/server/src/mcp/toolkits/project/handlers.test.ts -t t3_project_orientvp run check:changedt3_project_orientin a live thread; confirm routes mark.agents/STARTING_MAP.mdpresent and response has no file bodiesagent-context-increaselabel (budget grew for tool list + orchestration append)🤖 Generated with Claude Code