Catch the changelog and the two build docs up - #146
Merged
Conversation
The changelog gains what a person upgrading has to know and the six defects fixed since the last pass. `AGENT_TOOL_TOKEN` is generated on a laptop now, and `start.sh` stops skipping services that are already answering, which costs about five seconds on a run that rebuilds an image and is why a rotated secret now reaches the things that use it. The README gains one row. Its settings table already named the two secrets `start.sh` sets, and this is the third: without it no Bot may call a tool, and a person setting up would otherwise not learn it exists. Nothing else there changed — it says how to build and run this, not what happened to it. `docs/configuration.md` had `AGENT_TOOL_TOKEN` as "unset", which is no longer true of the documented path. It now says start.sh generates one, why the fail-closed default is right for a deployment and wrong for a laptop, and that it is one of a pair with MANAGED_AGENT_TOKEN pointing the other way — which is the thing that makes rotating either of them confusing. Also removes server/tests/routing.test.ts, an empty file I created by accident while looking for the real one and committed in #144.
davidmckayv
requested review from
MikeRyanDev,
guidovizoso and
tylerslaton
as code owners
August 22, 2026 03:40
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.
Twelve merges since the last documentation pass.
Changelog
Upgrading gains the two things an operator has to know:
AGENT_TOOL_TOKENis generated on a laptop now..env.examplestill ships it empty and a deployment not usingstart.shis unchanged, so the fail-closed default is intact.start.shno longer skips services that are already answering. A run that rebuilds an image now recreates the Bot containers, about five seconds. That is the cost of a rotated secret actually reaching the things that use it.Fixed gains six, newest first: the Bot that browsed to a vendor it had tools for; the question routed to a coworker with no way to answer it; the deny rule walked around by
computer_typewithsubmit; the refused callback that left no trace; the request for the wheel that followed a Bot between conversations;/admin/computerslisting nothing; and every component recorded twice on a first start.Each is written as what a person running this would notice, not as what the diff did.
README: one row
Its settings table already named
COMPUTER_TOKENandSUPERVISOR_TOKENas thingsstart.shsets.AGENT_TOOL_TOKENis the third, and without it no Bot may call a tool at all — a person setting up would otherwise not learn it exists until nothing worked.Nothing else. It says how to build and run this, not what happened to it.
docs/configuration.md
AGENT_TOOL_TOKENwas listed asunset, which stopped being true of the documented path.It now says
start.shgenerates one; why a default that is right for a deployment was wrong for a laptop, where it meant every granted MCP tool was refused before it reached the grant, the boundary or the trail — and a refusal at that point does not reach the transcript, so a Bot reported no results rather than an error; and that it is one of a pair withMANAGED_AGENT_TOKENpointing the other way, which is the part that makes rotating either of them confusing.Also
Removes
server/tests/routing.test.ts. Zero bytes — I created it by accident while looking for the real routing test and it went in with #144.Checked, not assumed
.env.examplealready carries the corrected form-submit rule from Let the policy see the Enter a type action presses #104, and no doc repeats it, so nothing else needed changing there.docs/plugins/google-drive.mdis accurate as written: the redirect URI, the two APIs and the preview-program note all still hold.docs/architecture.mdnames no audit event types, somcp.callback_refusedneeded no entry.bun run testbun run typecheckbun run format:check/lint