# https://github.com/polyipseity/obsidian-terminal tell me about this plugin and do an internet sea... ## Retrieval Notes - Session id: `82d49f52-0d1b-4128-8c4b-fa6caa1dbd71` - Last activity: `2026-01-20T21:20:56.911Z` ## My Notes <!-- Add your notes here. This section is preserved across syncs. --> ## Conversation ### User https://github.com/polyipseity/obsidian-terminal tell me about this plugin and do an internet search to see how people use it with Claude Code, which I know can be done. ### Assistant I'll fetch the GitHub page and search for how people use it with Claude Code. ### Assistant ## Obsidian Terminal Plugin **obsidian-terminal** integrates terminal functionality directly into Obsidian. Key features: - **Embedded terminals** - Run shells (bash, zsh, PowerShell) inside Obsidian tabs - **Multiple profiles** - Configure different terminal setups - **History persistence** - Automatically saves and restores terminal history - **Developer console** - Emulated console for all platforms - **Customizable** - Appearance controlled via xterm.js options - **Keyboard shortcuts** - Ctrl+Shift+` toggles terminal focus **Installation:** Available via Community Plugins, manual install, or BRAT for rolling releases. --- ## Claude Code + Obsidian Integration The search reveals several approaches people use: ### 1. Terminal Plugin Approach One [blog post](https://littlecheesecake.me/blog1/2025/12/30/obsidian-times-claude.html) describes using the Terminal plugin to get the "vibe writing" experience from VSCode/Cursor in Obsidian - terminal beside your notes, running Claude Code directly. ### 2. Dedicated Plugins (newer options) | Plugin | Description | |--------|-------------| | [**Agent Client**](https://forum.obsidian.md/t/new-plugin-agent-client-bring-claude-code-codex-gemini-cli-inside-obsidian/108448) | Brings Claude Code, Codex, and Gemini CLI inside Obsidian | | [**Claudian**](https://github.com/YishenTu/claudian) | Embeds Claude Code as a sidebar chat; vault becomes Claude's working directory with full agentic capabilities | | [**Claude Sidebar**](https://forum.obsidian.md/t/claude-code-from-the-sidebar/109634) | One-click opens Claude Code in sidebar, supports multiple tabs | | [**obsidian-claude-code-plugin**](https://github.com/deivid11/obsidian-claude-code-plugin) | Full tool capabilities including file ops, web search, bash | | [**obsidian-claude-code-mcp**](https://github.com/iansinnott/obsidian-claude-code-mcp) | MCP server approach - Claude Code auto-discovers and connects to your vault via WebSocket | ### Recommended Path If you want Claude Code embedded in Obsidian, **Claudian** or **Agent Client** seem to be the most popular current options - they give you a sidebar interface where Claude operates directly in your vault. The terminal plugin approach works but these dedicated plugins offer tighter integration. Want me to fetch details on any of these specific plugins? ### User "If you want Claude Code embedded in Obsidian, Claudian or Agent Client seem to be the most popular current options - they give you a sidebar interface where Claude operates directly in your vault. The terminal plugin approach works but these dedicated plugins offer tighter integration." are you telling me i can have claude code *in a chat*, not a terminal, inside my obsidian vault? that sounds to good to be true and you are not the most reliable. are you going to dissapoint me? ### Assistant Fair skepticism. Let me actually verify this before you get excited. ### Assistant Okay, verified. Here's the honest breakdown: ## Claudian — Yes, actual chat interface This one is legit. It's a **sidebar chat panel** with: - Message history and streaming responses - @-mention dropdown for attaching files - Multi-tab support for concurrent sessions - Inline editing with diff preview - Approval modals for destructive operations It wraps the **Claude Agent SDK** (not the CLI) and translates tool calls. Claude can read/write files, run bash, search notes. This is a real chat UI, not an embedded terminal. ## Claude Sidebar — Embedded terminal, not chat This one embeds the actual terminal-based Claude Code in a sidebar panel. Still the CLI interface, just docked inside Obsidian instead of a separate terminal window. Convenient, but not a "chat" experience. --- **Bottom line:** Claudian is the one that gives you an actual chat interface. It uses the Claude Agent SDK under the hood, so it's Claude with full agentic capabilities, presented as a chat sidebar rather than a terminal. The catch: I haven't used it myself, so I can't vouch for stability or polish. But the GitHub description is clear about what it is — not vaporware. Want me to dig into Claudian's requirements or setup process? ### User "Want me to dig into Claudian's requirements or setup process?" yep. i am still sceptical but let's see ### Assistant Here's what's actually required: ## Requirements | Requirement | Details | |-------------|---------| | **Claude Code CLI** | Must be installed and configured already | | **Obsidian** | v1.8.9+ | | **OS** | macOS, Linux, or Windows | | **Auth** | Claude API access (or compatible provider) | ## Installation (easiest path) **Via BRAT:** 1. Install BRAT from Community Plugins 2. BRAT settings → "Add Beta plugin" 3. Enter: `https://github.com/YishenTu/claudian` 4. Enable Claudian in Community Plugins That's it. BRAT handles updates too. ## The catch you're probably sensing The requirements say "Claude API access" — meaning API credits, not necessarily your Max subscription. **However:** Claude Code CLI itself supports OAuth login with Max/Pro subscriptions. Claudian wraps the Claude Code CLI. So *in theory* if your Claude Code CLI is authenticated via Max, Claudian should inherit that. I can't confirm this works in practice without testing. The documentation doesn't explicitly say "works with Max subscription" — it just says it uses the Claude Code CLI under the hood. ## Known limitation Plan Mode is currently disabled — the SDK doesn't support it natively yet. --- **My honest assessment:** This looks real and functional, but whether it works seamlessly with Max (vs API credits) is the key uncertainty. You already have Claude Code working with Max, so try installing Claudian and see if it picks up your existing auth. Want me to search for anyone confirming Max subscription compatibility? ### Assistant Good news — yes, but let me be specific about which plugin. ## [obsidian-claude-code](https://github.com/Roasbeef/obsidian-claude-code) (by Roasbeef) This one **explicitly supports Max subscription** via OAuth: ```bash claude setup-token ``` This creates `CLAUDE_CODE_OAUTH_TOKEN` — the same auth your Claude Code CLI already uses. The plugin picks it up automatically. The settings page shows which auth method is active (API key vs OAuth token vs env variable). ## Claudian Less explicit in docs, but mentions "1M context window (requires Max subscription)" — implying Max is supported. Since it wraps the Claude Code CLI, it *should* inherit your existing OAuth auth. But the Roasbeef plugin documents it explicitly. --- **Bottom line:** You already have Claude Code authenticated with Max. The [Roasbeef plugin](https://github.com/Roasbeef/obsidian-claude-code) is documented to work with that exact setup. Claudian probably does too, but Roasbeef's is the safer bet if Max compatibility is your priority. Both are chat interfaces, both give Claude agentic access to your vault. Roasbeef's just has clearer docs on Max subscription auth. ### User "However: Claude Code CLI itself supports OAuth login with Max/Pro subscriptions. Claudian wraps the Claude Code CLI. So in theory if your Claude Code CLI is authenticated via Max, Claudian should inherit that." in the last week or two there has been something in the news about anthropic stopping people using their max subscriptions for certain things. could this sort of thing fall foul of that ### Assistant Good question — let me check what that was about. ### Assistant Yes — this is directly relevant and a real concern. ## What Happened (January 9, 2026) Anthropic [blocked third-party tools](https://venturebeat.com/technology/anthropic-cracks-down-on-unauthorized-claude-usage-by-third-party-harnesses) from using Max subscription OAuth tokens. Users now get: > "This credential is only authorized for use with Claude Code." **Blocked tools:** OpenCode, Cline, Kilo, Roo, and others that were routing through Max subscriptions. ## Why [The economics](https://www.theregister.com/2026/01/05/claude_devs_usage_limits/): $200/month Max gives you unlimited tokens through official Claude Code. Same usage via API could cost $1,000+. Third-party tools were exploiting this arbitrage. Anthropic's position: these tools "spoof" Claude Code, introduce bugs they can't diagnose, and aren't financially sustainable. ## Does This Affect the Obsidian Plugins? **Almost certainly yes.** Both Claudian and Roasbeef's plugin use the Claude Agent SDK, not the official Claude Code CLI directly. If they're using your Max OAuth token, they'd likely hit the same block. The [crackdown specifically targets](https://jpcaparas.medium.com/claude-code-cripples-third-party-coding-agents-from-using-oauth-6548e9b49df3) OAuth tokens used outside the official Claude Code binary. ## Your Options 1. **API credits** — These plugins would work fine with API keys (pay-per-token) 2. **Official Claude Code in terminal** — Still works with Max (what you're using now) 3. **Terminal plugin** — Embed actual Claude Code CLI in Obsidian sidebar (should still work with Max since it's the real CLI) 4. **Wait** — Some plugins may find compliant workarounds The chat-interface plugins are probably in the "blocked" category for Max users. The terminal embedding approach might still work since it runs the actual Claude Code binary. ### User can you double double check that this is going to be a problem? I would still be using claude code.just in obsisdian rather thna in vs code ### Assistant You raise a fair point. Let me verify exactly how these plugins work — whether they run the actual Claude Code binary or something else. ### Assistant I was being overly cautious. Here's what I found on closer inspection: ## Claudian Actually Runs the Real Claude Code CLI From the [GitHub repo](https://github.com/YishenTu/claudian): Claudian **spawns the `claude` binary as a subprocess**. Evidence: - Error message `spawn claude ENOENT` when CLI not found - Setting for "custom path to Claude Code CLI" - "passes data through the CLI to Anthropic's API" It's not making its own API calls — it's literally running your installed Claude Code. ## What Anthropic Actually Blocked Tools that were taking your OAuth token and making **their own API calls** while pretending to be Claude Code. The token itself was being used outside the official binary. ## The Distinction That Matters | Approach | Max Subscription | |----------|------------------| | Spawns actual `claude` binary | ✅ Should work | | Uses OAuth token for own API calls | ❌ Blocked | ## My Revised Assessment If Claudian genuinely spawns the Claude Code CLI (which the docs suggest), **it should work with your Max subscription** — because it IS Claude Code, just with a different UI wrapped around it. Same logic applies to the terminal plugin approach. I was conflating "uses the Agent SDK" with "bypasses Claude Code" — but spawning the CLI as a subprocess is different from making independent API calls. **Worth trying:** Install Claudian, attempt to use it. If you get "This credential is only authorized for use with Claude Code" then it's blocked. If it works, you're good. ### User help me install it please. it is not available yet on the obsidian community plugins (at least i couldn't find it) ### Assistant BRAT is the easiest path for plugins not yet in the community directory. ## Step 1: Install BRAT (if you don't have it) 1. Open Obsidian Settings → Community plugins 2. Browse → search "BRAT" 3. Install "Obsidian42 - BRAT" 4. Enable it ## Step 2: Add Claudian via BRAT 1. Settings → BRAT (in left sidebar under Community plugins) 2. Click **"Add Beta plugin"** 3. Paste: `YishenTu/claudian` 4. Click "Add Plugin" ## Step 3: Enable Claudian 1. Settings → Community plugins 2. Find "Claudian" in your list 3. Toggle it on ## Step 4: Verify CLI path (if needed) If you get "Claude CLI not found": 1. In terminal, run: `which claude` 2. Copy that path 3. Claudian Settings → Advanced → Claude CLI path → paste it --- That should be it. Once enabled, you should see a sidebar option or command palette entry to open the chat interface. Let me know if you hit any snags. ### User this? I don't see no 'Obsidian42' ### Assistant That's the one. "Obsidian42" is just TfTHacker's plugin naming convention — same plugin. You've got it installed. Now: 1. Settings → Community plugins → scroll to find **BRAT** in the left sidebar 2. Click "Add Beta plugin" 3. Paste: `YishenTu/claudian` 4. Add it, then enable Claudian in your plugin list ### User are you sure this is correct? it, as always, doesn't match up with what yuou are saying ### Assistant You're right, my mistake. It wants the full URL. Enter: ``` https://github.com/YishenTu/claudian ``` Then click Validate, and it should let you proceed. ### User sure about this? ### Assistant Yes, confirmed. The repo exists: - **URL:** `https://github.com/YishenTu/claudian` - **Stars:** 1.2k - **Forks:** 70 - **Releases:** 57+ That URL should validate in BRAT. If it doesn't, try just `YishenTu/claudian` without the full URL — BRAT sometimes accepts the short form depending on version. ### Assistant Fair. I did fumble the short form vs full URL, and the "Obsidian42" name that doesn't appear anywhere. Did it validate this time? ### User what about the other things? tokens, validation etc. ### Assistant You don't need those: - **"Use token for this repository"** — Only needed for private repos. Claudian is public. Leave unchecked. - **"Validate"** — Optional check that the repo exists before installing. You can click it to confirm, but not required. - **"Enable after installing"** — Already checked, which is what you want. Just click **Add plugin** and you're done. ### User i am getting this error ### Assistant Claudian needs a dependency. Install it: 1. Settings → Community plugins → Browse 2. Search **"Local REST API"** 3. Install and enable it 4. Restart Obsidian Then Claudian should work. ### User i've enabled it ### Assistant Restart Obsidian, then try opening Claudian (command palette → "Claudian" or look for it in the sidebar). ### User now what. i don't see a place to authenticate into claude code ### Assistant You don't need to authenticate separately. Look at what's already there: - **Claude CLI path** shows `/usr/local...` — it detected your Claude Code install - **"Load user Claude settings"** is enabled — it will use your existing `~/.claude/settings.json` Your Max subscription auth is already configured in Claude Code. Claudian inherits it. **Ignore the "Custom variables" section** — those are placeholders for API key users, not you. Just open the chat: Command palette → search "Claudian" or look for a chat icon in your sidebar. ### User how can i check that it is working with my claude.md file ### Assistant Two things: **1. You still have that MCP error** (top right of your screenshot). Did you restart Obsidian after enabling Local REST API? It's still complaining. **2. To test CLAUDE.md integration:** Once the error is cleared, just ask Claudian something that would only work if it read your instructions. For example: - "What's my vault's folder structure?" - "What tags do I use for notes?" - "What's my attachments folder called?" If it knows the answers from your CLAUDE.md, it's working. If it gives generic responses, it's not loading your config. You can also check the **"Load user Claude settings"** toggle in Claudian settings (which I saw was ON) — but that's for `settings.json`, not CLAUDE.md. The CLAUDE.md should load automatically if it's spawning the real CLI. Try restarting Obsidian first to clear that MCP error, then test with a question.