Marketplace for trusted AI agent skills

Skill Detail

Run agent CLI terminals inside Obsidian with Claude Sidebar

Use Claude Sidebar when an operator wants Claude Code, Codex, or another agent CLI available as terminal tabs inside an Obsidian vault with file and folder context.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Published
⭐ 443 GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-agent-cli-terminals-inside-obsidian-with-claude-sidebar Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source
At a glance
Tools required
Obsidian desktop, Python 3, an installed agent CLI such as Claude Code, Codex, Grok Build, OpenCode, Gemini, Kimi Code, GitHub Copilot, Cursor Agent, or Pi, and pywinpty on Windows when using native Windows terminal support
Install & setup
Install from the Obsidian Community Plugins listing for Claude Sidebar, then enable it in Obsidian. For manual installation, create .obsidian/plugins/claude-sidebar in the vault and download main.js, manifest.json, and styles.css from the latest GitHub release. On Windows, install Python 3 and run py -m pip install pywinpty for the interpreter used by the plugin.
Author
Derek Larson
Publisher
Individual
Last updated
Aug 20, 2026
Quick brief

Use Claude Sidebar when the operator keeps project notes or specs in Obsidian and wants agent CLI sessions to run next to that vault context. The workflow is concrete: install the Obsidian community plugin or release files, configure the CLI provider, open an agent tab from the ribbon or command palette, launch the agent in a selected folder, send a file path or selection into the terminal, resume the last conversation, and optionally switch providers for a one-off tab. Invoke this instead of using the agent product normally when the useful context is inside Obsidian and the operator wants terminal sessions, vault paths, selections, and project folders wired directly into the agent workflow. The scope boundary is embedded terminal operation for existing agent CLIs inside Obsidian; it is not a general Obsidian product card, not a knowledge-base automation recipe, and not a replacement for Claude Code, Codex, OpenCode, Gemini, or other supported backends.