Mayor agent completes without using tools — missing GASTOWN_SESSION_TOKEN in local dev

[jrf0110]

Problem

When sending a message to the mayor (e.g., "update the readme"), the agent completes immediately without calling any tools (gt_sling, gt_list_rigs, etc.). No beads are created, no work is delegated.

Root Cause

The gastown plugin's createMayorClientFromEnv() requires four env vars: GASTOWN_API_URL, GASTOWN_SESSION_TOKEN, GASTOWN_AGENT_ID, GASTOWN_TOWN_ID. If any is missing, it throws, and the plugin fails to register tools entirely.

In local dev, GASTOWN_JWT_SECRET is bound via secrets_store_secrets in wrangler.jsonc. This uses the Cloudflare Secrets Store, which may not be available in local development. When resolveJWTSecret() returns null:

1. mintMayorToken() returns null
2. GASTOWN_SESSION_TOKEN is never set in envVars
3. kilo serve starts without the token in its env
4. The gastown plugin calls createMayorClientFromEnv(), which throws
5. The plugin fails to load — zero mayor tools are registered
6. The LLM receives a system prompt describing tools that don't exist
7. With no tools available, the LLM responds conversationally and completes immediately

Evidence

• Wrangler logs show POST /mayor/completed arriving seconds after POST /mayor/message
• No POST /api/rigs/.../sling or tool-related requests from the mayor
• Streamed events show session.error followed by immediate session.idle and agent.exited

Fix Options

1. Add a .dev.vars file in cloudflare-gastown/ with GASTOWN_JWT_SECRET=<dev-secret> so it's available in local dev
2. Add a fallback in mintMayorToken() that uses a hardcoded dev secret when ENVIRONMENT === 'development'
3. Log the error — currently the plugin failure is silent. Add a console.error when createMayorClientFromEnv() throws so it's obvious in logs

Related

• Parent: Gastown Cloud: Cloud-first rewrite of Gastown as a Kilo platform feature #204
• PR [Gastown] PR 8.5: Mayor Tools — Cross-Rig Delegation #347 (mayor dispatch)
• PR [Gastown] Agent Streaming Endpoint — WebSocket-based Live Agent Observation #348 (agent streaming)

[jrf0110]

Fixed in PR #350 (merged into 204-gt-prop-d). Root causes and fixes:

1. Plugin not discovered — Dockerfiles used wrong config path (~/.config/opencode/ instead of ~/.config/kilo/) and wrong directory structure (subdirectory instead of direct file symlink). The glob {plugin,plugins}/*.{ts,js} expects files directly in plugins/.
2. Plugin deps not installed — Added npm install --omit=dev during Docker build.
3. session.idle premature completion — Mayor agents are persistent sessions; session.idle means "done with this turn" not "task finished." Added persistent flag to skip idle as a completion trigger for mayor role.
4. Stale sessions after container restart — MayorDO now retries by creating a fresh session when sendFollowUp fails, instead of surfacing a 500.
5. Mayor tools 401 in dev — mayorAuthMiddleware was skipped in dev but handlers depend on agentJWT.userId from the middleware. Now always runs.
6. Activity stream empty — Event name mismatch (message.part.updated vs message_part.updated) and tool state was an object not a string. Added session.diff rendering for file changes.