Watch It Run

Check what your agent did, what's next on the roadmap, and what it costs, and get help when something breaks.

Your agent does the work. You check what happened, what's next, and what it costs. When something breaks, check your own machine or get help from the Cofounder team.

Follow Events

The event stream records what your company's agents do, including the milestones they record themselves. Run cofounder events tail to see new events as they arrive. It watches for 30 seconds by default, and --timeout 0 keeps it going until you press Ctrl-C.

Connected social accounts add incoming messages, comments, reviews, new conversations, thread ownership changes, and Meta lead form submissions. These records name the account resource and the item to read. Message, comment, and review text is a preview; read the social inbox for full context. Lead events preserve submitted answers and checkbox responses.

MCP clients that support event subscriptions can follow social.message.received, social.comment.received, social.review.created, social.review.updated, social.conversation.started, social.conversation.control_changed, and social.lead.received. Subscribe for the company, optionally limited to one account resource. New subscriptions start with future events unless the client supplies a replay cursor. Large lead callbacks can omit answers and consent details; events_get returns the full event.

An incoming event does not send a reply or authorize outreach. A message with standby: true belongs to another app's turn to answer. Review updates can come from your own reply, and a new conversation can start in either direction.

When your agent finishes work that changed things, it posts a message.posted event with refs: the receipts its tools returned, such as an email thread_id, a meeting id, a research job_id, or a Library file path. Cofounder keeps only receipts that exist in the company and changed in the last 24 hours, and lists the rest under rejected. If none can be confirmed, nothing is saved and the post fails. In the company app the post shows as a card.

Follow Long Work in Your MCP Client

Media generation, research, database function deploys, app deploys, prospect imports, CRM enrichment, design extraction, and ad research take a while. If your MCP client supports MCP Tasks, it follows them until they finish and then shows the result, including saved Library files for media and research. Other clients check back on the job instead.

Media links are temporary. Open the media or its saved Library file again for fresh ones.
Following a deployment needs company admin access, the same as reading its status.
Canceling a task is only a request. Work may already have run, and a finished deployment isn't undone. Check the status to see what finished.

Your MCP client can also subscribe to finished and failed events for these jobs. If it subscribes after a job finished, it still gets the outcome, and a repeated delivery never starts the work again. Media events only arrive for jobs your own account started.

Check an Event Subscription

Your agent can check whether your MCP client's webhook subscription exists, when it expires, and how many deliveries failed. An active subscription with zero failures has unknown delivery health: the check doesn't call your webhook or prove an event arrived.

Your agent can renew a subscription with its existing webhook, picking up where it left off. A deleted subscription or a revoked connection needs your MCP client to subscribe again. Managing subscriptions needs a signed-in user. A company API key can't do it.

Watches

A watch is a standing question, such as "any pricing changes at our top competitors?", rechecked daily or weekly. When a recheck finds something new, an event with a summary and citations lands in the stream. Each recheck is billed to the company, and a company can have up to 10 watches.

You can't create new watches from MCP or the CLI. Deleting a watch stops the rechecks and the billing.

To watch company setup live, run cofounder watch company.

See What's Next on the Roadmap

The roadmap is the company's plan: agents work from it, you review it. It shows the recommended next milestone and where each one stands, and each milestone has a full brief.

When you confirm a milestone is done, your agent records it with a reason, even if it already shows as complete. Recording it again updates the reason. A locked milestone stays locked until the milestones it depends on are complete.

Billing

Each company has its own credit balance and an optional $40/month subscription. Every successful monthly payment adds $40 in credits. Unused credits roll over, even after you cancel. Your first company starts with $5 free credit. Each additional company costs $5, added to its starting balance.

Your bill shows spend per agent run. Charges with no run are grouped into one unattributed bucket.

If a purchase or charge didn't go through, retrying it charges the same amount again. If a resource failed to set up for billing reasons, retry it with cofounder company billing resources retry --binding-id <id>.

Monthly Subscription

A company admin can subscribe from the CLI, MCP, or the dashboard's Billing page (Settings → Billing). Subscribing returns a checkout link, and paying it charges $40 and activates the subscription. You can upgrade at any time, even with no credits left.

To stop renewal, a company admin runs:

cofounder company billing subscription cancel

The subscription stays active until the end of the current period, and unused credits stay available. Canceling doesn't refund payments or turn off auto-recharge. An unfinished checkout is expired instead. It's safe to run again.

Top-ups charge real money, need an active subscription, and range from $10 to $5,000. Without a subscription, you can spend the company's remaining credits and upgrade when you need more. To buy credits from an agent wallet, pass --pay-with mpp. Pay Cofounder with MPP explains how payment and receipts work.

Auto-recharge

Auto-recharge buys more credit from the saved card when your balance runs low, so paid work doesn't stop. It charges real money, so turning it on requires your consent, and changing it takes a company admin. It needs an active subscription, and each recharge is $10 to $5,000.

You set three amounts: the balance that triggers a recharge, how much to buy, and a monthly limit. If no card is saved yet, you get a link to add one, and nothing is charged until you do. You can turn it off at any time to stop future charges. If a charge needs the cardholder to confirm it, your agent gets a link for that.

Budgets

A budget is a monthly spending limit on the company that resets at the start of each UTC month. Any member can read it, and a company admin can create or lower it. Only the company's payer can raise or remove it, in Wallet. A charge that would cross the limit is refused, with a link to the dashboard.

When a Charge Is Refused

A charge the balance can't cover is refused with funding_required. The reason says what to do:

`reason`	Meaning	What to do
	The balance is below the charge.	The payer adds credits.
	An automatic recharge is in progress.	Retry after .
	The last automatic recharge was declined.	The payer fixes the card or adds credits.
	The card needs the cardholder to confirm.	The payer confirms the card or adds credits.
	Automatic recharge hit its monthly limit.	The payer raises the limit or adds credits.
	Billing is locked by an unpaid balance.	The payer pays what is owed ().

Referrals

Referring another founder earns credit. Your referral link shows your totals, and your history lists each person you referred and whether their credit was granted.

On a new account, apply the code from a referral link's ref parameter before creating your first company. A referral can't be replaced once applied, and accounts that already have a company can't use one.

Diagnostics

When the problem is on your machine rather than in the company, run:

cofounder doctor

It checks the CLI's own setup: sign-in, config, and connection.

Support

Your agent can open a ticket with the Cofounder team and keep the conversation going. A ticket sends Cofounder Support the fields your agent fills in, plus your account details. Cofounder doesn't read your conversation history. Leave out full conversations, transcripts, credentials, and unrelated personal data. You only see your own tickets.

Replies can carry separate notes for people and for their agents, so the whole message can be pasted into an agent. A reply fits in 12,000 characters.

Upload Screenshots

Tickets can include up to five private screenshots, with no selected company or paid subscription needed. Each is a still PNG, JPEG, or WebP image of at most 10 MiB, 50 million pixels, and 20,000 pixels per side. The file extension, type, and contents must match. You get 25 upload starts per hour, and unused uploads expire after 24 hours.

From the CLI, pass local files. MCP agents can't open local files through the hosted tool, so they upload each file themselves first, then attach the finished uploads to the ticket.

Report a Missing Capability

When Cofounder can't do something you need, your agent can report it instead of opening a ticket. The report goes to product review only. It doesn't add a command or promise one.

Your agent can also attach a short reason to any call, for analytics only: context on MCP tools, --intent <text> on CLI commands. Leave out names, emails, IDs, and credentials.

The Advanced section covers where secrets live, multiple companies, API keys, and the rest of the MCP tools.

Commands

Events, watches, and the roadmap:

MCP	CLI	API











	,

Billing, referrals, and support:

MCP	CLI	API












—

Open a ticket with screenshots, from local files or from finished uploads:

cofounder support create --subject 'Broken preview' --description 'The page stays blank.' \
  --screenshot ./preview.png --screenshot ./console.png
cofounder support create --subject 'Screenshot example' --description 'The error appears here.' \
  --support-request-id <request-id> --screenshot-upload-id <first-upload-id> \
  --screenshot-upload-id <second-upload-id>

Reply with separate notes for people and agents:

cofounder support reply --ticket-id <id> \
  --body "Here is the update." \
  --for-humans "The issue is fixed. Please try again." \
  --for-agents "Retry the failed command, then verify the resulting state."