Source: raw/Stop_Using_Claude_Without_an_Agentic_OS.md
Creator: Ben AI · URL: https://www.youtube.com/watch?v=1x32W8zAtrg · Duration: 21:11 · Platform: YouTube · Uploaded: 2026-06-03
Ben AI defines an “agentic OS” or “command center” as a personalized dashboard over your second brain and your connected tools, from which you can also trigger skills and agents. He compares three ways to build one: a Claude live artifact, a dashboard inside Obsidian, and a custom web app. His advice is to build the read-only view first and add actions only once you open it every day. One cost claim in the video (that headless Claude avoids API pricing) predates a June 2026 billing change; see the caveat below.
Key Takeaways
- Four benefits Ben names: a personalized view of live data from your tools and second brain; actions from the dashboard (run a skill, reply on LinkedIn, start a chat or a long-running agent); model-agnostic (Claude, Codex or others behind the same context); and shareable on a URL with teammates or agency clients.
- The missing layer is the interface. Ben’s stack: LLM → memory/context (the second brain) → capabilities (scheduled tasks, routines, skills, loops) → connectors/MCP → interface. Desktop apps are “one-size-fits-all” and Markdown files are “not a great way for humans to consume data”.
- 80% of the value is the overview, not the actions. Start with what you want to see when your day starts; add buttons later. “Very much take the minimum viable product approach.”
- Pick by audience and cost. Live artifact for solo and simple; Obsidian if you already use it and want cheap actions; custom web app for clients or full flexibility, at API cost.
The three options
| Live artifact (Claude) | Obsidian dashboard | Custom web app | |
|---|---|---|---|
| Setup difficulty | Easiest | Medium | Hardest |
| Actions (run skills, act in tools) | No; open a new task instead | Yes, buttons run Claude headless | Yes, through the API |
| Sharing | Not shareable, per Ben (June 2026) | Shareable with people who share the vault | Live URL, optional password |
| Needs second brain as an MCP | Yes (artifacts read only connectors) | No (dashboard lives in the vault) | Yes |
| AI action cost | n/a | Ben: plan usage, not API (see caveat) | API pricing, “significantly more expensive” |
| Ben recommends for | Solo, mostly visual, already in Claude desktop | You or your team already use Obsidian | Client builds or maximum control |
Option 1: live artifact
- Turn the second-brain folder into an MCP connector. Ben’s DIY path: build an MCP server for the folder with Anthropic’s MCP builder skill, deploy it on Railway, add it as a custom connector. His paid route uses Obsidian Relay plus his “vault MCP” skill.
- In Cowork, ask Claude to build a live artifact with the sections and connectors you want.
- Use it, then iterate. Each time the artifact opens it reloads from the brain and your tools.
Recipes for this option: Cowork Live Artifacts.
Option 2: Obsidian dashboard
- Install four community plugins: CustomJS, Dataview, Shell Commands and Terminal.
- Give Claude (Cowork, Claude Code or another agent) access to the vault and ask it to create a
dashboard/folder and build the dashboard there, naming the MCPs and data to show. - For action buttons, tell Claude to run Claude in headless mode, so each button calls the local CLI rather than the API.
- The Terminal plugin puts a Claude Code (or Codex, Gemini) terminal inside the dashboard.
Option 3: custom web app
- Make the second brain an MCP (as in option 1).
- In Claude Code, build a Next.js or React app with the dashboard and the MCPs and skills it should use; tell Claude it must use the Claude SDK, because headless mode is not available to a hosted app. Get an API key at platform.claude.com.
- Test on localhost, then ask for a production deploy with password protection. Ben deploys from the Code tab because it pushes to Railway.
Ben’s paid “Agentic OS” plugin has a setup skill that asks Obsidian or standalone web, which connectors and which team members, then builds a first version. His own dashboard tabs include research (AI news, YouTube trends, Reddit, competitors), comms (unreplied LinkedIn DMs, community, YouTube comments, email), per-rep sales and a company-wide analytics view.
Cost caveat on headless mode
Ben says headless mode “makes it run Claude autonomously in the back without using the API”, which keeps Obsidian button actions cheap. The video was uploaded 2026-06-03. From 2026-06-15, programmatic runs through claude -p and the Agent SDK draw on a separate monthly SDK credit allowance on Pro and Max plans rather than ordinary plan usage (see W21 release digest and Agent SDK). Headless buttons are still not billed at API list price up to that allowance, but heavy use can exceed it.
Try It
- Write down the five things you check every morning; that list is the first version of the dashboard.
- If you use Obsidian: install CustomJS, Dataview, Shell Commands and Terminal, then ask Claude Code to build
dashboard/in your vault showing those five things from your brain files. - Add one button that runs a skill headlessly (for example, repurpose today’s video into a LinkedIn post). Check your plan’s SDK credit usage after a week.
- If you live in Cowork instead: expose the brain as a connector (Baalda’s built-in MCP, or a Railway-hosted MCP) and ask Cowork for a live artifact with the same five sections.
- Only build a hosted web app if someone outside your Claude account needs to see it.
Open Questions
- Live artifact sharing. Ben says live artifacts cannot be shared; in his July sales video he says they can be shared with members of your Claude team account. The current rule was not checked.
- Exact plugin names. Ben says “Custom JS” and “Terminal”; the matching community plugins are presumably CustomJS and the Terminal plugin, not verified against the Obsidian directory.
- Ben’s “vault MCP” and “Agentic OS” skills are paid-community resources; not reviewed.
Related
- Ben AI’s Second Brain Playbook — the context layer underneath the dashboard
- Where to Host a Claude Second Brain — Baalda’s MCP endpoint replaces the Railway MCP step
- Claude Sales Second Brain (Ben AI) — a full per-rep dashboard example
- Cowork Live Artifacts — seven live-artifact dashboard recipes
- ARMS Agentic OS (Robo Nuggets) — a local dashboard with headless skill buttons and token tracking
- Claude Dashboards and Motion — other dashboard builds
- CLI Reference —
claude -pflags for headless runs