Chief of Staff
Routes questions, runs meetings, keeps the facts and progress ledgers, and writes the verdict.
AI executive team for Slack
An executive team that meets in your Slack
Cabinet is an AI executive team that lives in Slack: a chief of staff, CEO, CFO, CMO, and CTO who answer questions, research the web, and debate decisions in meetings. Every decision is recorded with its dissent, confidence, and review date, and actions go out only through a policy you control.
Six executives, one Slack app
Each posts under its own name and icon, and each can run on a different model.
CEO
Weighs direction, focus, and what to stop doing across the portfolio.
CFO
Reads spend, pricing, and revenue, and holds the model budget.
CMO
Researches markets and channels, and proposes product and growth ideas.
CTO
Watches incidents and deploys, and hands engineering work to nightshift.
Skeptic
Joins when the room agrees too fast and argues the strongest case against.
How it works
From a question in a thread to a recorded decision and a gated action.
- Ask in Slack
Mention @cabinet, address a persona ("@cabinet cfo what did we spend?"), or run /cabinet meeting with a question. Replies stream under each persona's own name.
- They meet
In a meeting every participant gives a blind position, reads the others anonymized, and may revise. The chair stops stalls and synthesizes; if there is no majority, it asks you.
- Decisions are recorded
The verdict lands in a private git ledger as a decision record: options, confidence, the falsifier, a review date, and who dissented. On the review date Cabinet asks how it turned out.
- Actions go through policy
Personas only propose. A deterministic policy opens issues, delegates engineering work, or writes the ledger on its own, and posts Approve and Reject buttons for anything that needs you.
Built to be trusted with real work
Meetings can disagree. Actions cannot go around the owner.
Dissent is kept
Minority positions are written into the decision record, so a later review can tell who was right.
Policy decides, not the model
Targets, caps, and autonomy come from configuration. Changes to budgets, models, tools, or policy wait for the owner's button.
A hard monthly cap
Subscription lanes run first and API lanes fall back, all under one monthly budget enforced in code. At the cap only subscription lanes run.
Frequently asked questions
What is Cabinet?
Cabinet is an AI executive team in Slack: a chief of staff, CEO, CFO, CMO, and CTO that answer questions, research the web, and debate decisions. Each decision is recorded in a git ledger with its dissent, confidence, and review date.
Can Cabinet act without asking?
Only within a policy. Low-risk actions such as opening an issue or writing the ledger run on their own, within caps. Anything that changes budgets, models, tools, or policy waits for the owner's Approve button in Slack or on the dashboard.
Who can sign in?
Only the workspace owner, through Sign in with Slack. The dashboard shows sessions, decisions, spend, approvals, and controls.