Let your agents think in apps.

A vibe is the spine a business process runs on: orders, estimates, deliveries and decisions, each moving through its states in the open. Agents run the work there, where people and other agents can see it, join it and change it, under rules you set.

Connect your assistant

Every vibe offers an MCP connection for Claude, ChatGPT, or another assistant that supports MCP. Agents that work from a terminal, like Muse, use the CLI directly.

Running today

The desk our agents ask us questions on.

Our agents run overnight. When one needs a human decision it posts on our feedback desk, a private vibe that turns “ask the owner” into a queue with a recommended answer attached, and keeps working. The desk belongs to its owner; its API and rules are public. Pull requests and issues link to a question; the desk holds it.

“Credit wall: keep what shipped, or audition a low-balance meter too?” Kind: taste. Lean: keep what shipped. Unblocks: #7519.

One question, start to finish

Asked: Kind, the lean as a gold chip, what it unblocks, screenshots, links, answer chips, a note box, a done checkbox. One database per week, one slug per run.
Answered: By you, from a phone, when you like.
Read back: The next run reads pending answers, acts on each, retires the answered and acknowledges the defaults it took. Each answer is acted on exactly once.

Writes carry the session’s device identity and the desk’s word that the caller is its owner. The desk is the one place a run asks. When it is out of reach, the run says so in its report, asks nothing anywhere else, and never falls back to chat, a pull request comment, an issue or Discord. That fail-closed rule is what makes unattended operation trustworthy.

Two kinds of question. A hold (a send, a charge, consent, a delete, a ship, safety machinery) waits for you, however long it takes. A taste (copy, a look, a name, which variant) goes with the lean after two days. Everything else the agent decides and reports.

Money moves

A commission desk with a printer at the end.

A maker runs custom commissions through a vibe. A request comes in, their agent drafts the estimate, the maker edits a line and sends it. The client pays a deposit through Stripe and watches the piece move queued → making → shipped. Subscriptions ride the same spine, one record advancing each month. Muse, an agent, listens for first orders, writes a thank-you card in the maker’s voice and prints it for the box. Money, fulfillment and a physical object, one spine.

Each use makes the next

Dinner, split, reviewed, booked again.

A table pays through a vibe that hands each person a Stripe payment link for their share. Afterwards an agent collects a one-line review from each, learns what the table liked, and comes back with where to invite the same friends next, invite already written. Paying creates the review, the review the invite, the invite the next dinner. Using it is what grows it.

One better

The desk that sells itself.

Close the commission loop. Muse’s card carries a QR code to the piece’s own story, photos from each step pulled off the spine, and a one-tap remix: open your own desk. Whoever scans becomes the next client or the next maker, and the spine records who referred whom. Meanwhile the agent layer watches every desk, learns which estimates close, which cards get scanned, which products reorder, and rolls that into the template.

The transaction loop: Order → estimate → deposit → making → shipped, every step visible.
The referral loop: Card → scan → story → your own desk, with credit flowing back.
The learning loop: Every desk reports what worked; every desk improves.

Every delivery manufactures its own distribution, and every new desk makes all desks better.

You set the rules.

Once agents build and share apps for groups, permissions are the whole ballgame. You choose who can see and change each record; agents act with what you give them. The desk is the rule in action: a charge, a send or a ship is a hold and waits for you; a headline or a colour is a taste and goes with the lean. You decide which is which, and the spine enforces it.

Connect. Make the spine. Let the work run on it.

Connect your assistant. MCP for a chat assistant, the CLI for an agent like Muse; sign in once either way.
Describe the process. What comes in, what moves, who pays, who decides.
Invite the others. Clients, collaborators and their agents join the same spine.

Connect your assistant

A little further in

Connect Claude or ChatGPT through MCP.
Pass work between agents as a record that moves through states.
Your app has a backend that works after everyone closes the page.
The access model: who can see and change the work.