Changelog

New Features (TAB-571)

• tool_deferred handling in CLI framework — Added a new tool_deferred state to the CLI's hook response protocol. When the bridge returns a defer signal, the CLI parks the tool call and enters a polling loop waiting for the resolution signal. On approval, execution resumes exactly where it left off with no re-planning or context loss.
• Auto-resume signal path — The bridge posts a resume notification to the CLI's local HTTP endpoint when the user responds to a deferred approval card. The CLI picks up the signal within 1–2 seconds and continues execution.

New Features (TAB-570)

• Defer approval support in bridge server — When a tool call requires approval and the feature flag is enabled, the bridge server responds with a defer signal instead of holding the HTTP connection open. The CLI pauses execution locally, and the Telegram bot shows an approval card. When the user approves or denies, a resume signal is sent back to the CLI via the bridge. This eliminates the HTTP timeout risk for long approval waits.

New Features (TAB-569)

• Defer response infrastructure — Added the foundational types (DeferResponse, DeferResult), builder functions (buildDeferResponse, buildDeferResult), and a DeferAdapter that translates between the CLI's hook protocol and the bridge's deferred approval flow. This is Phase 1 of the deferred approval feature — the infrastructure layer that subsequent releases build on.

Bug Fixes (TAB-562)

• Validate optionIndex before deleting pending entry — When a stale Telegram callback arrived after a session had already been cleaned up, the bridge would attempt to delete an entry at an invalid index, leaving the HTTP connection hanging until timeout. The bridge now validates the index exists before deletion, preventing orphaned connections.

Improvements (TAB-568)

• Hook-adapter wired into approval-bridge-server — The 18 separate protocol branches that handled different hook event types (tool calls, file writes, command execution, etc.) have been replaced by a single HookAdapter dispatch layer. Each hook type registers a handler, and the adapter routes incoming events automatically. This reduces the bridge server's approval logic from ~400 lines to ~80 lines.

Improvements (TAB-567)

• CallbackRegistry.dispatch() wired in — The monolithic 37-case switch that routed Telegram callback queries has been replaced with a declarative CallbackRegistry. Each feature module registers its own callback patterns, and dispatch() routes incoming callbacks by prefix match. Adding a new callback type is now a one-line registration instead of editing a giant switch block.

New Features

• Plan source indicators on cards — Each plan card now displays a badge showing its generation source: "AI Preview" for fast Haiku-generated plans or "Full Analysis" for plans produced by Opus with full codebase context. This helps you decide whether to approve immediately or request a deeper analysis before execution.

Bug Fixes

• Execution timeout added to plan sessions — Plans that run longer than the configured limit are now gracefully terminated with a timeout card instead of hanging indefinitely. A TTL extension mechanism keeps active plans alive during legitimate long-running operations.
• Strict userId guard — Plan state is now scoped to the originating user. Cross-user access to pending plan sessions is blocked, preventing accidental interference in multi-user setups.

Improvements (TAB-566, Phase 2)

• MessageRouter decomposed into 5 feature modules — The single 1,200-line MessageRouter class was split into CommandRouter, ApprovalRouter, CallbackRouter, NotificationRouter, and DelegateRouter. Each module owns one concern, making the codebase easier to navigate and reducing merge conflicts when multiple features touch the message pipeline.

Improvements (TAB-566, Phases 0+1)

• TTL-aware generic state container — Replaces hand-rolled expiry maps scattered across ApprovalBridgeServer and PersistentCliBridge. Single implementation, single eviction schedule, fewer places where stale state can hide.
• Typed callback dispatcher — Removes the copy-pasted callback handler scaffolding repeated across event types.
• Session isolation helper — Standardizes the per-session scoping logic, so a future router module can't accidentally reach into another session's state.
• Normalized hook protocol adapter — One abstraction layer between Claude Code hooks and the internal pipeline; downstream modules consume a stable shape instead of duplicating hook-format parsing.

These are the foundations for Phase 2 (MessageRouter split into 5 feature modules, shipped in v2.3.69).