Building an Agentic OS Command Center with Obsidian and Claude Code

Chase walks through a custom Obsidian workspace that serves as the front end for his entire "Agentic OS." The setup combines an integrated terminal running Claude Code with dashboards, one-click automations, and research feeds -- all inside a single note-taking app. It is a practical example of how Obsidian's flexibility can turn a markdown editor into a full operations hub for AI-assisted workflows.

The Dashboard Layout

The command center opens with a top-level view labeled "AGENTIC OS" and four navigation tabs: Overview, Audience, Content, and Research. Across the top row, large metric cards display platform stats: 125,000 YouTube subscribers, 9,766,258 TikTok views, 195,000 TikTok followers, and 124,700 Instagram followers. Below the metrics sits a token burn tracker showing Claude Code usage (8.7K tokens, 246 messages, 26 sessions) alongside quick-action buttons: "Plan Today," "Plan Tomorrow," "Morning Brief," "Inbox Brief," and others for content cascading, YT pipelining, weekly review, daily cleanup, and a pull summary. A daily notes section at the bottom provides space for ongoing task context.

Integrated Terminal

One of the standout features is the embedded terminal panel running Claude Code directly inside Obsidian. The frame shows a live Claude Code v1.141 session with Opus 4.7 connected to a project vault. You can see actual terminal output -- hook configurations, plugin settings, identity federation details -- sitting right below the dashboard tabs. This means Chase never leaves Obsidian to run agentic workflows. He gets the full power of a CLI session alongside visual dashboards in one window.

Custom Skills and Automations

The button row beneath the metrics gives single-click access to predefined automations. These appear to be Claude Code custom skills wired into the Obsidian interface. "Plan Today" and "Morning Brief" likely trigger prompt-based routines. "Content Cascading" and "YT Pipelining" suggest automated content repurposing workflows. The setup removes the friction of remembering commands or navigating to separate tools.

Audience and Research Tabs

Switching to the Audience tab provides a deeper view of content performance data. The Research tab is where things get more interesting: it surfaces trending topics and content opportunities pulled from Twitter, YouTube, and other sources. The frame showing the research view includes a markdown-formatted daily briefing with sections covering AI space developments, new Claude Code features, and content strategy angles. Beneath that, output items reference scripts that generate weekly recaps and trend analysis automatically.

File Structure and Calendar

The left sidebar exposes Obsidian's standard file tree -- daily notes organized by date, folders for dashboards, projects, and other vault sections. Chase also mentions embedding his calendar on the left side, giving him scheduling context alongside project files. The file tree visible in the frames shows a well-organized vault with nested folders for different operational areas.

Key Takeaways

• Obsidian's plugin ecosystem and markdown-based structure make it a viable front end for AI agent workflows, especially when paired with an embedded terminal.
• Placing Claude Code inside Obsidian means you get CLI power and visual dashboards in one workspace, eliminating context switches between terminal and browser.
• One-click automation buttons wired to Claude Code skills reduce the overhead of running recurring AI tasks like daily planning, content pipelining, and research briefings.
• Platform metrics displayed at the top of the dashboard give immediate visibility into audience growth without opening separate analytics tools.
• The research tab pattern -- automatically aggregating trending topics and content opportunities -- is a useful template for anyone producing regular content in the AI space.