One place for all your work

Most of your day is spread across tools that don't know each other. Notes in Notion. Files on Drive. Tasks in Linear. Threads in Slack. Research in chat windows. Drafts in Docs. Screenshots in Downloads.

Nothing compounds. Every Monday you reassemble the picture by hand.

Cabinet collapses that into one folder on your computer. Inside it lives everything: your knowledge, your files, your AI agents, their schedules, their memory, their outputs. You open one app and everything is there. You close your laptop and an AI team keeps working.

Two pictures of the same idea

If you don't write code. Cabinet is a smarter folder. You write notes. You drop in PDFs, docs, spreadsheets, and screenshots. You describe a person you wish you'd hired — "an analyst who reads my inbox every morning and tells me what's urgent" — and that person exists, in the same folder, getting better at the job over time.

If you do write code. Cabinet is a local-first, git-tracked knowledge tree. Every page is a markdown file. Every agent is a persona.md. Every scheduled job is a YAML file in .jobs/. The whole thing is portable, scriptable, and yours. No database. No cloud. No lock-in. ls and you see your work. git log and you see its history.

Why "one place" matters

A scattered tool stack means scattered context. An assistant in ChatGPT can't see your meeting notes. An agent in Linear can't see your research. A scheduled job in Zapier can't write back into your brain.

Cabinet's bet is that knowledge, work, and the workforce have to live in the same folder for any of it to compound. The team that drafts your launch should be able to read last quarter's launch. The agent that summarizes your week should be able to write the summary into the same place you'll go looking for it.

Your AI team works 24/7 — without you babysitting

Real teams have rhythms: a Monday standup, a Friday update, an inbox check at 9am. Cabinet agents have the same.

Tasks — one thing, runs once. "Draft the launch post."
Routines — a task on a schedule. "Draft the launch post every Friday."
Heartbeats — a recurring check-in the agent uses to decide what to do next. "Every weekday at 9am, look at the launch room and tell me what changed."

Heartbeats are the difference between an assistant you have to summon and a teammate who shows up. You go to sleep; the team keeps doing the work that doesn't need you. You wake up to durable pages in your knowledge base — not a chat transcript you'll never reread.

Bring the brains you already pay for

Cabinet doesn't host inference. You connect Claude, GPT, Gemini, Grok, or a local model, and Cabinet routes your agents' calls to them. There's no Cabinet middleman, no inference markup, no quota.

A team of teams

A real company isn't one big team. It's a tree: a CEO at the top, departments under that, projects under those, each with its own people and knowledge.

Cabinets nest the same way. The root cabinet is your company, your life, your project. Child cabinets are departments — marketing/, research/, clients/acme/. Each child cabinet has its own agents, its own jobs, its own visibility scope. Agents up the tree can dispatch work to agents below them. Every proposal is queued for one-click human approval before anything runs.

You don't have to start from a blank folder. cabinets.sh is a public registry of plug-and-play cabinets — a complete AI team for a job hunt, a solo startup, a wedding, a podcast, a property portfolio. Clone one folder, run one command, and you have a team:

npx cabinets add <owner>/<template-name>

Open it in Cabinet. Every agent, every job, every page is already there. Edit a persona, change a schedule, point a job at a different folder — make it yours.