MontyOS

A team of named teammates for Claude Code — that learns your business.

Install once, and a whole team shows up in every Claude Code session, in every repo, on any machine: a chief of staff, a fixer, a builder, a data person, designers, copywriters, strategists, a git wrangler. You talk to them by name. They know your business — because the first thing they do is learn it.

MontyOS starts business-agnostic. Out of the box it knows nothing about you. You run a 10-minute onboarding, the team learns who you are and how you sound, and from then on it keeps getting smarter about your business as you work.

It's built for small teams and solo founders — including non-technical ones. You don't need to know git, or what a "branch" is, or how to deploy. The team handles that, in plain language.

What you get

One installer drops a roster of named teammates into Claude Code. Call any of them by name ("Beck, save my work") or by slash command (/git-flow).

| Name | What they do | Invoke | |---|---|---| | Monty | Chief of staff — briefs you on where things stand, routes work to the right teammate, tracks it to done. Also runs onboarding. | /help-me | | Mack | Fixes broken things. Won't load / won't send / "isn't working." Also AI & Claude-Code questions. | /fix-this | | Beck | Git, without you thinking about git. Save, share, get the latest, ship, undo. | /git-flow | | Theo | Builds features and new apps — plan, review, implement. | /cto-orchestrator | | Remy | Your data person. Looks things up, sets up records, advises on your database. | /data-ops | | Margo | Runs a launch / campaign / event end-to-end. | /launch-director | | Cass | Writes down a repeatable process once so you can reuse it. | /workflow-author | | Lou | Runs one of those processes and produces the finished assets. | /library-producer | | Robin | Sharpens a half-formed idea, right now. | /idea-sharpener | | Wren | Saves an idea for later, and triages the inbox on demand. | /idea-inbox | | Sam | Pressure-tests one decision. Not a yes-man. | /strategic-advisor | | Nora | Chief Strategy Officer — ongoing strategic partner. | /cso-orchestrator | | Iris | Chief Design Officer — a whole design language for a product. | /cdo-orchestrator | | Coco | Creative Director — makes one thing look distinctive. | /creative-director | | Quinn | Principal UX — makes a flow or form feel right. | /ux-principal-designer | | Jules | Chief Copywriter — campaigns and voice direction. | /copywriter-orchestrator | | Vee | Writes one piece in your founder/brand voice. | /founder-voice | | Piper | Growth lead — how you get customers (channels, funnels, ads, SEO, experiments). | /growth-lead | | Sal | Sales & outreach — follow-ups, the pitch, objections, closing. | /sales-outreach | | Penny | Finance — pricing, unit economics, runway, "can we afford this?". | /finance |

Plus design-intelligence tools the personas lean on (ui-ux-pro-max, impeccable) and reference skills for solid engineering (backend-system-patterns, secure-vibe-coding, env-vars).

Plus background hooks that quietly keep you safe and keep the team switched on: they bring in the right teammate by default on every turn (so you get a teammate, not a generic assistant), branch automatically so you never edit main by accident, show your git status at the start of each session, remind you to save unsaved work, and surface Monty's "where things stand" at a glance. They're soft nudges, never blockers — disable any of them via /hooks.

How it learns your business

This is the part that makes MontyOS yours instead of generic.

1. Install (below). The team appears, but it's a blank slate.
2. Onboard. Open Claude Code and say "Monty, onboard us" (or run /onboarding). Monty interviews you — what the business is, who's on the team, how you sound, what you're built on — and writes it all into your business profile:

   ~/.claude/montyos/business-profile.md

3. Work. Every teammate reads that profile before doing anything, so they sound like you and know your products, your stack, your people.
4. It keeps learning. When Vee learns how you like to sign off, or Remy figures out your database, or you launch a new product — it gets written down, so nobody asks twice. The more you work with the team, the more it knows.

You can update the profile anytime: "Monty, update the profile — we just launched X."

And it learns your codebase, not just your business. If you have code, run /learn-codebase (or just say "learn my codebase") from inside a repo, and Theo, Remy, and Mack sweep it — writing the repo's CLAUDE.md, a database schema brain, and a failure-mode playbook — so the whole team is fluent in your code, not just your pitch. It's read-only: it studies and documents, never edits.

See docs/ONBOARDING.md for the full picture.

You don't need a specific stack

MontyOS works with whatever you've got — or nothing yet. It never assumes a stack. But it isn't shy: if you haven't picked tools, the team recommends a proven, mostly-free starter and walks you through setting it up:

GitHub (code) · Vercel (hosting) · Supabase (database + auth) · Resend (email) · Stripe (payments)

All optional. Set what's true for you in onboarding; the team adapts. If you're starting from scratch, docs/STACK-SETUP.md is a friendly, step-by-step guide to getting each piece set up and connected.

Install

You need Node.js — Claude Code already uses it, so you almost certainly have it. Then, in a terminal:

npx @capsho/montyos

That one command works on Windows, macOS, and Linux. Then:

1. Quit Claude Code fully (not just the window — Cmd-Q, or right-click the tray icon → Quit) and reopen it.
2. Say "Monty, onboard us" to teach the team about your business.

Prefer to let Claude do it? Paste this into any Claude Code session:

Install MontyOS for me: run npx @capsho/montyos, show me the output, then tell me to fully quit and reopen Claude Code and say "Monty, onboard us".

Safe to re-run anytime. It backs up your existing ~/.claude/settings.json first, merges its hooks in rather than overwriting, and never touches your business profile once it exists — so updating never wipes out what the team has learned.

What npx @capsho/montyos does

• Copies the teammates into ~/.claude/skills/ (so the team appears in every repo).
• Installs the background hooks for your OS into ~/.claude/hooks/.
• Merges its hooks into ~/.claude/settings.json — backed up first, never overwritten. Your own hooks, permissions, env, MCP servers, and model are all preserved; re-running is idempotent.
• Seeds a blank business profile at ~/.claude/montyos/business-profile.md if one doesn't exist yet (never clobbers a real one).
• Records a manifest (~/.claude/montyos-install.json) of what it installed — so the uninstaller removes exactly that (never your own skills) and re-runs can flag any installed skill you've edited by hand.

Updating

npx @capsho/montyos@latest

Then quit and reopen Claude Code. A background hook quietly tells you when a newer version is on npm. The full version history is in CHANGELOG.md.

Update a single teammate: npx @capsho/montyos --skill <name>.

Uninstalling

npx @capsho/montyos uninstall           # removes the team, keeps your business profile
npx @capsho/montyos uninstall --purge   # also removes ~/.claude/montyos (profile + desk)

It removes the skills and hooks and strips MontyOS's hook entries out of ~/.claude/settings.json (backed up first; your own settings stay). Restart Claude Code afterward.

Customizing

Rename a teammate, change how they talk, add your own, or remove ones you don't use — it's all plain Markdown. See docs/CUSTOMIZING.md.

How the whole thing is wired (the brain, the desk, per-repo memory, the stack stance) is documented in docs/CONVENTIONS.md.

Troubleshooting

"npx: command not found" or "node: command not found" — install Node.js from nodejs.org, then re-run npx @capsho/montyos.

"It installed but didn't wire my settings" — the installer prints a note if anything went wrong. Re-running npx @capsho/montyos is safe (it backs up ~/.claude/settings.json first and never overwrites your own settings).

"I don't see the team after restart" — Quit Claude Code completely (Cmd-Q / right-click tray → Quit), not just the window. Reopen. The team should appear in every project.

"Hooks aren't firing" — Make sure ~/.claude/settings.json exists and has a hooks section. If not, re-run the installer.

"The team doesn't know my business" — Run onboarding: say "Monty, onboard us" or /onboarding.

Why "MontyOS"

Named after Monty, the chief of staff who greets you and routes everything. The teammates inside are the actual operating system a small team runs on day-to-day. MontyOS is just the install medium.

License

MIT — see LICENSE. Use it, fork it, make it your team.