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
Copy file name to clipboardExpand all lines: docs/compatibility.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,7 @@ compatibility.
46
46
| Tool confirmations | Supported | Interceptable `always_ask` built-ins and MCP tools park durably. Allow executes the original server-owned call through the tool journal; deny returns an error tool result with the optional denial message. Provider-native Web Search/Fetch cannot be intercepted and reject `always_ask`. |
47
47
| User interrupt | Limited | An untargeted interrupt durably cancels an active model, outcome grader, or tool Activity across API and worker processes. PostgreSQL defines finish-vs-interrupt ordering, closes model spans, emits one idle `end_turn`, and fences uncertain started tool steps as ambiguous. Targeted multi-agent interrupts are not supported. |
48
48
| Terminal execution errors | Supported | A deterministic turn failure emits `session.error` with the documented `unknown_error` variant and `retry_status: terminal`, followed by `session.status_terminated`. MCP setup failures retain their more specific documented event variant. Older persisted histories may contain the legacy `api_error` spelling. |
49
+
| Model retry lifecycle | Supported | Retryable provider responses emit typed `model_overloaded_error`, `model_rate_limited_error`, or `model_request_failed_error` events. Each bounded retry publishes `retrying`, `session.status_rescheduled`, then `session.status_running`; exhaustion emits `exhausted`, returns idle with `retries_exhausted`, and flushes later queued messages. Provider `Retry-After` is honored up to the server cap. Infrastructure recovery remains private to Temporal. |
49
50
| MCP execution | Limited | Remote tools are discovered over unauthenticated Streamable HTTP, pinned per Session, permission-checked, journaled, and executed with large or binary results materialized in the Session sandbox. Calls publish `agent.mcp_tool_use` with the required `mcp_server_name` and the bare server-side tool name, answered by `agent.mcp_tool_result` carrying `mcp_tool_use_id`; an `always_ask` MCP call still parks for a `user.tool_confirmation` referencing `tool_use_id`. Authentication, private-network access, deprecated-SSE fallback, resources, and prompts are not supported. |
50
51
| Files, skills, memory, and vaults | Not supported | These product surfaces are outside the core harness scope. File-backed outcome rubrics and file-sourced message content are rejected explicitly; inline or URL image/document content still participates in the provider transcript and context projection. |
51
52
| Multi-agent orchestration | Not supported |`multiagent` configuration can be stored, but rosters, threads, delegation, and orchestration are not executed. |
0 commit comments