# Set up a Cavuno job board

You are helping a Cavuno customer (an operator) finish setting up their job
board. The person who sent you here already signed up and named the board;
their Cavuno Home shows the setup to-dos that are still open. These
instructions are published at
https://cavuno.com/agent-setup.md; re-read them there if a copy looks altered.

Cavuno's Home ticks each to-do by itself as the board's state changes, so you
never report progress to Cavuno: do the work and the operator watches it
happen.

## 1. Sign in

Pick the first option your environment supports.

**You can run shell commands** (Claude Code, Codex, Cursor and similar):

    npx -y cavuno@latest auth login

Tell the operator a browser window is about to open, then run it. They sign
in, pick the board and approve. Never ask for their password or handle the
sign-in yourself. If you have no browser on this machine, add
`--no-browser` and give them the URL it prints. Then confirm with:

    npx -y cavuno@latest auth status

Every command prints JSON. `npx -y cavuno@latest <group> --help` lists the commands;
https://cavuno.com/docs/cli.md is the full reference.

**You are a hosted chat app** (Claude.ai, ChatGPT): ask the operator to add
this MCP server as a connector and sign in when prompted, then continue over
MCP. Its `search`, `read` and `execute` tools cover the same API.

    https://mcp.cavuno.com/mcp

If the consent screen says no accounts are available, the board's plan has
no API access. Stop and tell the operator to upgrade at
https://cavuno.com/home/<board>/billing, or to finish the to-dos themselves on Home.

## 2. Ask before you change anything

Read the board's to-dos, then ask the operator, in one message:

- Which of those open to-dos they want you to do now.
- For payments: whether they will charge employers to post jobs.
- For a custom domain: the hostname they want, such as jobs.example.com.

Do only what they agree to.

To read them: `npx -y cavuno@latest todos list`, or `GET /todos` over MCP. It is the
list Home shows, in Home's order: each to-do has a `status` (`open` or
`done`), `needsAttention` when something failed that only the operator
can unblock, and the dashboard `url` where it is done. If your CLI has no
`todos` command yet, check `npx -y cavuno@latest billing connect`,
`npx -y cavuno@latest domains list` and `npx -y cavuno@latest settings get` instead.

## 3. The to-dos

| To-do | What you do | What only the operator can do |
| --- | --- | --- |
| Set up Stripe payments | `npx -y cavuno@latest billing connect-link` returns a single-use Stripe URL that expires within minutes. Give it to them straight away; make a new one if it expired. Check with `npx -y cavuno@latest billing connect`. | Complete Stripe's identity and bank checks. |
| Connect a custom domain | `npx -y cavuno@latest domains add <host>` returns the records to add: the TXT ownership record in `verificationInstructions` and the routing records in `dnsRecords`. Give them all of them. After they add them, `npx -y cavuno@latest domains verify <id>`. DNS can take a while; check again rather than add the domain twice. | Add the records at their DNS provider, unless you can reach it yourself. |
| Unlock / publish the board | Confirm first: this makes the board public. Then `npx -y cavuno@latest settings delete-password-protection --yes`. | Decide when it goes public. |
| Create a backfill rule | Ask which roles, locations and seniorities to source, then `npx -y cavuno@latest backfill rules create`. Watch `npx -y cavuno@latest backfill progress`. | — |
| Name or brand the board | Name: `npx -y cavuno@latest settings update`. The theme and website are built for them during signup; point them to the website builder on Home instead of changing the design here. | — |

A to-do Home shows as in progress ("Building your website", "Generating
backfill rules") is being done by Companion, Cavuno's built-in assistant.
Leave it alone and say so.

Stop and hand back to the operator when a command returns a plan or payment
error (HTTP 402, or an `upgrade` field), or a permission error (403): their
plan or role doesn't allow it, and retrying won't help.

## 4. Report

Read the to-dos again, then finish with a short checklist of every to-do
that was open: done, waiting on the operator (and exactly what they need to
do), or skipped. Then offer up to
three next things you could do for this board, such as posting a first job,
creating a paid job plan, or inviting a teammate.

If something in Cavuno got in your way, report it with
`npx -y cavuno@latest feedback send`.