[bk-agent-01]

Refs: no Linear ticket (requested in the T3 session by tushar; this promotion PR was asked by his Manager session after the stage smoke test).

What this does

This PR promotes the full stage to bkmain (production bkt3). It carries one PR from this session:

• #342: upstream main from 163bdeaa11 to 05b697f6a2 (178 upstream commits), with the fork features ported into the files upstream split out of ChatView, the composer, the sidebar and settings.

bkmain had no content of its own beyond the earlier promotion merge (#341). Merging it into this branch gave no conflicts and no file changes.

Merging deploys bkt3 and restarts t3-nextbkt3. That stops every live session on bkt3. Merge at a quiet time.

New database migrations: none in this sync.

Idle compaction now has modes (upstream pingdotgg#23037)

• Settings → General → Compact idle threads sets the default: "When you return", "Before the cache expires (beta)" or "Never".
• Each Claude account can override it in its provider settings ("Use default" is the default).
• The old on/off setting compactIdleThreads still works: true is read as "Before the cache expires (beta)", and false as "When you return".
• It still applies only to Claude threads above 200,000 tokens.

Other upstream changes users can see

• Approvals in full-access mode say why Claude asked (feat(server,web,mobile): approvals in full access say why Claude asked pingdotgg/t3code#22546).
• Automation messages show as compact timeline rows (feat: show automation messages as compact timeline rows pingdotgg/t3code#22638).
• Webhook filters can fan out over arrays with a [] path wildcard (feat(server): webhook filters fan out over arrays with a [] path wildcard pingdotgg/t3code#23282).
• t3 thread CLI commands start, message and read threads from the terminal (feat(cli): start, message, and read threads from the terminal with t3 thread pingdotgg/t3code#22732).

How I tested

Stagebkt3 runs this exact code: stage at e4526c7b21, server version 0.1.2-nightly.20261021.3499.upstream.g05b697f6a201. I ran these checks on 2026-10-22 between 04:23 and 04:35 UTC:

Check	Result
Deploy	deploy-stage run green; ~/.t3/stage-dev/deployed-sha = e4526c7b21; t3-stage active since 04:23:40
Runtime	The server runs on Node 24.16.0 (the deploy workflows now install pnpm 12.14.0, as upstream's packageManager asks)
Health	https://stagebkt3.dev.beknown.live/.well-known/t3/environment 200
Server log	0 event loop stalled warnings. One error: a background git fetch for the hermes-agent project (remote_unreachable). It also appeared 7 times before this deploy, so this sync did not cause it
Manager MCP tools	/mcp initialize OK; 129 tools (t3_inbox, t3_answer, t3_start_session, t3_session_webhook_create, t3_thread_launch, delegate_task …)
New session	t3_start_session (Claude Sonnet, scratch project) answered "SMOKE OK"; the server logged claude.account.placed for it

Idle compaction itself was proven on stage on 2026-10-21 (see #337). This sync changed only how the mode is chosen, not the timer.

Cleanup: the temporary operator key was removed from stage settings.json (the file matches the pre-test backup, and the key now returns 401). The smoke session was archived.

CI: every check was green on #342 (9d606b28f5). "Mobile Native Static Analysis" waits for a macOS runner that this fork does not have.

🤖 Generated with Claude Code