Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Feature request: first-class Obsidian integration/plugin support in the Codex client [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18294•Fetched 2026-04-18 05:56:37
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
WyRainBowWyRainBow
Participants
raphhggraphhggWyRainBowWyRainBow
Timeline (top)
labeled ×3commented ×1unlabeled ×1

Fix Action

Fix / Workaround

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.

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

To integrate Codex with Obsidian, consider developing an official Obsidian plugin or built-in client integration for seamless note management and knowledge workflow.

Guidance

  • Investigate existing Obsidian plugins and APIs to understand the requirements for a first-class integration with Codex.
  • Design a user-friendly workflow for connecting an Obsidian vault to Codex, including a safer and more guided vault permission flow.
  • Explore native note search, read, and write actions for Obsidian content within the Codex client.
  • Develop a clear workflow for turning Codex outputs into Obsidian notes, reducing the need for custom glue code and local hacks.

Notes

The implementation details and technical requirements for the integration are not specified, and the issue lacks information about the current state of Codex and Obsidian APIs.

Recommendation

Apply workaround: While waiting for an official integration, users can continue to use custom MCP servers, CLI workarounds, or manual file manipulation to integrate Codex with Obsidian, although this may not be ideal for all users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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
#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Feature request: first-class Obsidian integration/plugin support in the Codex client [1 comments, 2 participants]