Replies: 1 comment
-
|
I am not sure there is a separate user-facing “subagent log” view in the Codex desktop app today. The closest things I would check first are:
For this specific case, it would be useful if the logs made the subagent boundary explicit: which subagent started, which MCP server/tool it called, what request failed, and whether the failure happened in the subagent, the MCP client, or the MCP server process. So I think there are two questions here:
If there is no scoped subagent log export today, that would be a very useful debugging feature. MCP issues are hard to investigate when the only visible result is that the subagent failed, but the underlying tool call / server stderr is hidden. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a subagent that calls MCP tools. There seems to be some issues with it. However, I cannot investigate the issue because I am unable to locate the logs for the subagents.
Where can I see those logs? and/or do I need to enable MCP logging somewhere? This is for the Codex desktop app.
Beta Was this translation helpful? Give feedback.
All reactions