You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- AgentDispatchOutcome threads Started/QueuedToActiveRun{effective_run_id,
pending_input_id} from the bridge through AgentDispatcher and
InboundResult. A message queued into an already-active run now aborts the
fresh-run response subscription instead of leaking it (internal dispatch
and chat API), cron bookkeeping records the effective run id, and the
pending input carries allowlisted attribution metadata
(source/automation_id/origin_run_id) into the acknowledged user record.
- Runtime-only run metadata (garyx_mcp_auth_token, remote_mcp_servers) is
stripped at the bridge persistence chokepoint so provider wiring and MCP
env secrets never reach transcript records.
- An explicit cron target (thread-like or channel) whose thread record is
missing now fails instead of silently succeeding through the bare-run
bypass; only the thread-less cron::<job id> pseudo-target keeps it.
- Thread-bound automations reject an explicit workspace_dir (the thread's
workspace always applies) and the desktop dialog hides the agent picker
and omits agent/workspace for thread-bound automations; docs updated.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments