Oh My Claudian banner
lee259 lee259

Oh My Claudian

Development community

Description

Bring Claude Code, Codex, Cursor, Grok, OpenCode, Oh My Pi, and Pi into your Obsidian vault — a Claudian fork.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Oh My Claudian

![Preview](assets/Preview.png)

Oh My Claudian is an Obsidian plugin that embeds coding agents in your vault. Agents can read, write, search, run commands, and carry out multi-step workflows in the vault working directory.

[Install from Obsidian Community Plugins](https://community.obsidian.md/plugins/oh-my-claudian) · [View on GitHub](https://github.com/lee259/oh-my-claudian)

This repository is based on [YishenTu/claudian](https://github.com/YishenTu/claudian) and adds Oh My Pi (OMP) and Cursor support through ACP.

Why Oh My Claudian?

Oh My Claudian gives you one Obsidian chat workspace for seven coding-agent providers while keeping each provider's native strengths visible:

  • Switch between Claude, Codex, Cursor, Grok, OMP, OpenCode, and Pi without changing your vault workflow.
  • Use provider-aware model discovery, readiness checks, permissions, planning, MCP, image attachments, and session recovery where supported.
  • Start safely with approval-oriented defaults, then opt into more powerful modes when you need them.
  • Run Oh My Claudian alongside the original Claudian plugin without sharing its Obsidian view type or composer styling.

Product Direction

Oh My Claudian is a local-first, multi-provider Obsidian workspace. It combines a shared chat experience with provider-native capabilities, so you can choose the right agent without giving up the safety and context of your vault.

Our priorities are:

  • Provider-neutral orchestration with provider-native behavior — shared conversation, tab, recovery, and readiness flows live behind core contracts; permissions, history, models, planning, MCP, and runtime protocols remain provider-specific where they need to be.
  • Obsidian-native knowledge work — dual-pane navigation, vault file context, attachments, inline editing, Mermaid rendering, and conversation history should work together as one workspace.
  • Safe and recoverable local execution — external file boundaries, approval-awa