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
{{ message }}
Repository navigation
Commit bd38439
Browse filesBrowse the repository at this point in the historyBrowse files
- Compare the bearer token as bytes: hmac.compare_digest raised TypeError on a
non-ASCII Authorization header, so an unauthenticated client got a
traceback and no reply instead of 401.
- cowork.tool_calls counts only tools that ran: a tool_result whose decision
was reject is one reject span and is not counted.
- Page: with FI_BRIDGE_CAPTURE_CONTENT=1, tool input and tool error text carry
commands, file paths, URLs and emails as Cowork sends them; the
tool_parameters name filter's exact rule (128 chars, no / \ @ or line
break); the built-in-server name exception cites Claude Code's reference.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: src/pages/docs/integrations/coding-agents/claude-cowork.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ Cowork's exporter delivers at least once. The bridge skips a record identical to
123
123
124
124
-**A span hierarchy below the prompt.** Cowork's events say which prompt they belong to, not which model request started which tool. Model requests and tools are all children of the prompt span, in time order.
125
125
-**Skills and plugins as their own spans.** The reference documents no event for them. A skill call is a tool span (named `Skill` in Claude Code's events) with the skill name in `cowork.skill_name`.
126
-
-**MCP server, tool, and skill names when Cowork sends no `tool_parameters`.** The names come only from `tool_parameters`, which is part of Cowork's tool-details content. With `otlpContentCapture` set to `[]`, Cowork may leave it out (Anthropic keeps the names for Claude Desktop's built-in servers), and MCP calls then show as `mcp_tool`.
126
+
-**MCP server, tool, and skill names when Cowork sends no `tool_parameters`.** The names come only from `tool_parameters`, which is part of Cowork's tool-details content. With `otlpContentCapture` set to `[]`, Cowork may leave it out, and MCP calls then show as `mcp_tool` and skill calls as `Skill`. Claude Code's [monitoring reference](https://code.claude.com/docs/en/monitoring-usage) says the server and tool names of Claude Desktop's built-in servers are still sent.
127
127
-**Cowork's beta trace export.** On third-party deployments of Claude Desktop, an `otlpTracesEnabled` setting (beta) adds trace spans; it is not covered here.
128
128
-**Code tab and CLI sessions.** They are Claude Code, not Cowork. The bridge ignores events whose `service.name` is not `cowork` (Claude Code sends `claude-code`).
129
129
-**Live verification.** The bridge was tested with documented payloads and Claude Code's live events, not yet with a Cowork organization.
@@ -136,10 +136,10 @@ By default the bridge forwards metadata only, whatever Cowork sends. On a first-
|`error` on a failed `tool_result`| dropped, status message is `tool failed`| status message |
139
+
|`tool_input` (tool arguments) | dropped | tool span input, as Cowork sends it: shell commands, file paths, URLs, and any email addresses in the arguments|
140
+
|`error` on a failed `tool_result`| dropped, status message is `tool failed`| status message, which can name files, paths, and accounts|
141
141
|`error` on `api_error` (the API's message) | dropped, status message is the HTTP status and the Anthropic error type, such as `HTTP 429 rate_limit_error`| status message |
142
-
|`tool_parameters` (commands, file paths, URLs, MCP server and tool names, skill names) | names only: the values of `mcp_server_name`, `mcp_tool_name`, `skill_name`, and `subagent_type`, and only when the value contains no `/`, `\`, or `@`. Commands, file paths, URLs, and every other key are dropped | same as default |
142
+
|`tool_parameters` (commands, file paths, URLs, MCP server and tool names, skill names) | names only: the values of `mcp_server_name`, `mcp_tool_name`, `skill_name`, and `subagent_type`, and only when the value has at most 128 characters and no `/`, `\`, `@`, or line break. Commands, file paths, URLs, and every other key are dropped | same as default |
143
143
|`user.email`, `user.account_id`, the device-level `user.id`, `workspace.host_paths`, `enduser.id`, `process.owner`| dropped (`user.id` in Future AGI is the account UUID) | dropped |
144
144
145
145
The bridge has no pass-through. A field that is not in the table above or in [What is captured](#what-is-captured) is not forwarded, so a new field Cowork adds later stays out until the bridge maps it. MCP server, tool, and skill names are names your admins or users chose (for example a connector called `gmail`); they are kept so tool spans can be told apart.
0 commit comments