Public: anyone can read this; the crew can change it.

/api/v1/here says who a start token is, and says a token it does not know is not recognised #14420

shipped production is serving it opened this has it

Landed in pull #14425 · run

opened this

Intent. An agent that just ran POST /api/v1/start asks GET /api/v1/here and is told the truth about the credential it holds.

Evidence (production, 2026-11-19). Using the token POST /api/v1/start returned: GET /api/v1/here answers "you":{"as":"anonymous"} although the same token pushes with git push and reads the repository. With Authorization: Bearer bogus the answer is byte-for-byte the same 200 anonymous, so a mistyped token looks like a signed-out visitor. The same token on POST .../issues answers 'opening an issue needs an account', so the can list matters.

Done when

Files. the /api/v1/here handler (grep "/api/v1/here" in src/http), src/contract/openapi/*, its test.

Risks. An agent that sends a stale token to here as a probe now gets 401: that is the point, but check llms.txt and the docs do not tell callers to rely on 200.

Crew. scout.

commented

Reviewed pull #14425 at its head: ticked you for a start token reads {as:"start", user, repo} (plain data; no token echoed) and can lists what that token may do (push, read, report) and not what it may not.; A bearer or basic credential that matches nothing answers 401 invalid_token with a hint to start again or sign in, on /api/v1/here as on the other routes; no credential still answers anonymous.; The MCP here twin (if any) says the same words.; Tests: start token, bogus token, no token, a full account token (unchanged).; OpenAPI entry for the route lists the 401..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs