AI OS Command Center

AI OS Command Center is a dashboard that shows you what your AI Operating System did while you were not looking.It reads your folder rather than any single tool, so every agent you run shows up in one place.

  • Every run your agents made, and what triggered it
  • What it cost, by day and by model
  • Which connectors are live, and which quietly expired
  • Everything your AI OS wrote, grouped by project
localhost:3030
AI OS

AI OS Command Center

Your local cockpit for Claude Code. Token burn, agent activity, connectors. All in one place.

Vaultmy-ai-os·PlanMax·Permissionauto·Live
Connectors21 connected
WorkspaceNotionKitSubstackXYouTubeVimeoWordPressStripeThriveCartHiggsfieldHeyGenElevenLabsHyperFramesGemini ImageNotebookLMPerplexityFirecrawlApifyVercelSupabase
Token burn·5h window·Live
0%
01.2M2.4M3.7M5M
0 / 5.0M
0 projected
Activity·
morning-brief·ok·12.3s

An AI OS Command Center answers 2 questions your folder cannot. What did my agents do, and what did it cost me.

Once routines run on a schedule, that work stops being visible. You find out something broke when the work depending on it breaks.

In this guide you will learn:

  • What each of the 14 screens shows you, and when to open it
  • How to build a working version yourself, free, with the exact steps
  • How to get the most out of it once you have it
  • Where your data lives, and what you may do with the software

Let's get started.

What is an AI OS Command Center?

The AI OS Command Center is a dashboard that runs on your own computer and reads your AI Operating System (AI OS) folder. It shows what is connected, what ran, what it cost and what is queued.

It reads the folder rather than any one tool, so it reports on every agent you use. It ships inside AI OS Pro.

Why an AI OS needs a dashboard

In this chapter you will see the problem it solves, and why that problem exists at all.

Plain text cannot tell you what happened to it

Your AI OS is markdown on purpose. That is what lets 10 different agents read the same folder.

But a folder will not show you that your calendar connector stopped authorizing 3 days ago. It will not show you that the morning brief has not run since Thursday.

The Command Center does not replace the folder. It reads the folder and puts a face on it.

It works with every agent you run

Claude Code, Claude Cowork, Codex, Cursor, Gemini CLI, Antigravity, OpenCode, OpenClaw and Hermes all read the same folder and write back into the same files.

The Command Center never talks to an agent and never asks for an API key. It reads the files they leave behind.

So switching agents changes nothing about this screen. Run 3 of them in a week and the activity feed shows all of it in one list.

What the AI OS Command Center shows you

In this chapter you will see all 14 screens, grouped by the question each one answers.

What is running

These 4 answer what your AI OS is doing right now.

  • Dashboard, the overview, opening on what changed since you last looked
  • Activity, every run in order, with what triggered it
  • Queue, what is waiting and what is blocked on you rather than the machine
  • Routines, your scheduled work and when each one last fired

What it costs

Usage charts your spend over time, by day and by model. Token burn is a live meter that sits on top of every screen.

The spend was already happening. What changes is that you can see which routine caused it.

What your agents know about you

These 5 let you read your own files the way your agents read them.

  • Context, your context files rendered, so you can check what actually loads
  • Memory, what has been added and when
  • Daily notes, one note per day, browsable
  • Open work, what is still open across your projects
  • Audience, who you are writing for

What it reaches, and what it made

These 4 cover what your AI OS is plugged into, and what came out of it.

  • Connectors, every tool your AI OS can reach, with live status on each
  • Skills, every skill installed and what each one does
  • Agents, the agents you defined, including the critics that block work before you see it
  • Outputs, everything your AI OS wrote, grouped by project

Who the AI OS Command Center is for

It is worth having once your AI OS does work you are not watching. That means routines on a schedule, several connectors, and spend you would rather understand.

If you are still writing your first context files, you do not need it yet. The next chapter is free and will carry you further than you expect.

How to build your own AI OS Command Center

In this chapter you will build a working version for free, and see exactly where it stops being enough.

What you need

You need an AI OS folder. If you do not have one, run npx @thenavidm/ai-os my-ai-os, then /onboard, which takes about 15 minutes.

You need an agent that can read files on your machine. You do not need a database, a host, an API key or an account.

Start with the audit you already have

Before building anything, run /ai-os-audit inside your folder. It ships with the free kit.

It scores your OS out of 100 across 6 parts, names the 3 fixes that move the score most, and saves the report so the number can climb.

That tells you whether the OS is built right. Run it weekly, and run /ai-os-grow monthly for what it could do but cannot yet.

Then build the daily read

The audit tells you how the OS is built. It does not tell you what happened yesterday.

Open your agent inside your AI OS folder and paste this in.

Read my AI OS folder and print me a command center as plain text.

1. Connectors: list every server in .mcp.json, and flag any that failed
   to load in this session.
2. Skills: list the skills under .claude/skills/ by name, and say which
   ones I have used in the last 14 days based on daily-notes/ and outputs/.
3. Open work: the top 5 items from inbox/open-work.md, most urgent first.
4. Outputs: what landed in outputs/ in the last 7 days, by project folder.
5. Memory: anything added to MEMORY.md in the last 7 days.
6. Decisions: anything added to decisions/log.md in the last 30 days.

Print it as one screen, under those 6 headings, with no preamble.
Where something is missing or empty, say so rather than filling it in.

Save it, so it is a tool and not a demo

Pasting a prompt once is a party trick. The value arrives when running it costs you nothing to think about.

Put that text in .claude/commands/status.md and typing /status runs it. Codex, Cursor and Gemini CLI each read a plain markdown file the same way.

What the free version cannot do

It has no history. It reads the folder as it is right now, so it cannot show spend over time or what changed since yesterday.

It cannot test a connector. An expired token looks identical to a working one in .mcp.json, and that is the failure that costs you a morning.

It costs tokens and takes about 30 seconds every time you look. A dashboard is instant and free to open.

It is not repeatable. The same prompt gives a different answer next week, so you cannot tell a real change from a rephrasing.

How to get the most out of it

Owning the screen is not the same as using it well. This is the rhythm that makes it pay.

Every morning, 30 seconds

Open the dashboard before you open your agent. You are looking for a routine that did not fire, a connector gone amber, and anything in the queue waiting on you.

If all 3 are clear, close it and start work.

Every week, 10 minutes

Open Usage and sort by spend. You are not cutting costs, you are finding the routine that costs more than it returns.

Then run /ai-os-audit and compare against last week. A falling score is the earliest warning that the OS is drifting.

Every month, 30 minutes

Open Outputs and read what your AI OS actually produced. It is the only screen that tells you whether the system earns its keep.

Then reread the context files that have not changed since setup. Those are usually the ones describing a business you no longer run.

Where your data lives

The Command Center reads your files, so it runs where your files are. You start it from your AI OS folder and it opens in your browser.

Nothing is uploaded. There is no account to create to see your own data, and nothing syncs in the background.

That is also the limitation. Close the laptop and the dashboard is not running, because the folder it reads is not there either.

For more than 1 person, it points at a shared Postgres database and switches on real accounts. That is a config change, not a different product.

How to get the AI OS Command Center

In this chapter you will see how to try it, how to get it, and what the licence allows.

Use the demo before you install anything

The demo at demo.aios.guide is not a screenshot tour. It is the same application, fully working, on an example vault.

Every screen loads and every filter works. The data is example routines and example spend, never yours.

How access works

It ships inside AI OS Pro, in the command-center folder, next to the skills and the routines. AI OS Max includes it too.

Access runs through your GitHub account rather than a download link. The repository is private and your account is added when you buy.

The free AI OS Starter Kit does not include it. The chapter above is what the free tier gets, and it is a real answer rather than a teaser.

What you can do with it

You may use it for your own business, on any number of your own machines. You may read, edit and extend every file in it.

You may not redistribute it, publish it, resell it, or share it outside your business.

The free version above is yours to do anything with. It is a prompt, and what it prints belongs to you.

FAQs about the AI OS Command Center

The questions people send before they install it.

An AI OS Command Center is a dashboard that runs on your own computer and reads your AI OS folder, so you can see what is connected, what ran, what it cost and what is queued. It replaces opening 6 files to work out what your agents did overnight.

Yes, it is included. It ships inside the AI OS Pro folder as command-center, and AI OS Max includes it too. There is nothing separate to buy and nothing separate to install.

It works with all of them. It reads your AI OS folder rather than any single tool, so Claude Code, Claude Cowork, Codex, Cursor, Gemini CLI, Antigravity, OpenCode, OpenClaw and Hermes all show up in the same activity feed.

No, it does not. The free AI OS Starter Kit gives you the folder, the structure and the skills, and the Command Center is the Pro side of that. This page shows you how to build a free version that genuinely works.

Your data does not go anywhere. The Command Center reads your folder on your computer and renders it in your browser, so there is no upload, no sync and no copy on a server.

No, you do not. You start it from your AI OS folder and it opens in your browser like any other site. If you got through the AI OS install, you can run this.

Yes, and you can use it rather than just look at it. The demo at demo.aios.guide is the full application running on example data.

No, it does not. It runs on your own machine, so there is no hosting bill, and the spend it reports is what your agents were already costing you.

Yes. By default it runs for 1 person on 1 machine with no sign-in. Pointing it at a shared Postgres database and switching on accounts turns it into something a team can open.

You can use it for your own business on any number of your own machines. You cannot redistribute it, resell it, or share it outside your business.

Was this page helpful?