The bridge is the part of Remote Control that picks up incoming work for this machine. If a piece of work arrives with a data.mode value set, the bridge now stops it once. It logs "Stopping work item with an unsupported mode" and records the event tengu_bridge_work_mode_unsupported.
The bridge also regularly sends a heartbeat, a small "still here" signal. While it waits because it is full, it now tracks when the next heartbeat is due instead of sending one for every skipped item. On shutdown, cleaning up worktrees (separate working copies of a project) now has a time limit for reading.
Why
Work this version cannot handle is ended cleanly rather than half-handled. A full bridge sends fewer heartbeats, and shutdown should not wait forever on worktree cleanup.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say which modes exist or where they come from.
Anthropic's release notes agreeImproved screen-reader output in /mcp: a disabled server is read as "off" instead of "pending"
