Feature request: first-class Obsidian integration/plugin support in the Codex client
What feature would you like to see?
I would like Codex to support a first-class Obsidian integration, ideally through an official Obsidian plugin or a built-in client integration that makes working with an Obsidian vault feel native.
This request is not about a specific crash or MCP configuration bug. It is about product-level support for using Codex together with Obsidian as a note-taking and knowledge-management workflow.
Why is this useful?
A lot of users keep their notes, research, drafts, prompts, and personal knowledge base in Obsidian. Right now, integrating Codex with Obsidian usually requires custom MCP servers, CLI workarounds, or manual file manipulation.
That works for advanced users, but it is fragile and not a great default experience.
A first-class integration would make it much easier to:
- read and update notes from a vault intentionally
- use vault context as part of ongoing work
- create drafts, summaries, and research notes directly into Obsidian
- move between Codex conversations and long-term personal knowledge storage
- reduce the need for custom glue code and local hacks
What could this look like?
Any of the following would help:
- an official Obsidian plugin for Codex
- built-in support in the Codex desktop client for connecting an Obsidian vault
- a safer and more guided vault permission flow
- native note search/read/write actions for Obsidian content
- a clearer workflow for turning Codex outputs into Obsidian notes
Expected behavior
From a user point of view, I should be able to connect Codex to Obsidian and then do things like:
- ask Codex to search my notes
- create or update notes in a specific folder
- turn a conversation into a note or daily note entry
- use selected notes as working context
- do this without depending on unofficial integrations
Additional context
There are already several Obsidian-related issues in this repository, but those seem focused on crashes, permissions, or MCP/server behavior. This issue is specifically a feature request for official Obsidian support in the Codex client experience.
Are you interested in implementing this feature?
_No response_
2 Comments
Following this.
I personally don't use Notion and I'm more into Obsidian so I'd love to have a streamlined way to have Codex communicate with my vault.
This is not a replacement for first-class Obsidian support, but I built a small experimental slice of this workflow that may be useful as prior art/test material: Obsidian High Recall.
Show-and-Tell thread: https://github.com/openai/codex/discussions/31169
Repo: https://github.com/ToussaintKnight/obsidian-high-recall-skill
Scope is intentionally narrow:
It still uses a skill/CLI wrapper, so it does not solve the product-level points in this issue: native vault connection, guided permissions, note create/update UX, or Obsidian deep-link/UI integration. But it may help test one concrete requirement from the request: asking Codex to search a vault without uploading raw notes.