Codex not able to interact with Obsidian #260
Unanswered
Nexus1408
asked this question in
Tech Support
Replies: 1 comment 1 reply
-
|
Apparently Codex' sandbox sets up a timeout of 120s: https://www.google.com/search?q=codex+desktop+sandbox+streamable-http+timeout&oq=codex+desktop+sandbox+streamable-http+timeout&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIHCAEQIRigATIHCAIQIRigATIHCAMQIRigATIHCAQQIRigATIHCAUQIRigATIHCAYQIRirAjIHCAcQIRirAjIHCAgQIRirAtIBCDYwMTFqMGo3qAIAsAIA&client=ubuntu-chr&sourceid=chrome&ie=UTF-8 -- you can adjust it via some configuration changes, though. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Although the MCP server is seen (in fact, Codex itself can list the available commands), once something is asked and the command is initiated everything is killed after 120 seconds of waiting time. This happens only inside Codex Desktop sandobx: when run via Codex CLI it works. Therefore, there might be an issue on how Codex Desktop handles the MCP server with Obsidian.
Beta Was this translation helpful? Give feedback.
All reactions