Skip to content
Billing Early Access

Quickstart

Cate runs many Claude agents at once: pair with one, delegate to another, review with a third. Connect Jira, Linear, or GitHub and every agent’s work is tracked alongside yours.

What you’ll need

Section titled “What you’ll need”
  • Claude Code installed — this quickstart uses your existing Claude Code login and default model
  • Node.js >= 18

Download Cate, launch it, and activate your license.

Start with an example

Section titled “Start with an example”

On the new project screen (File → New Project), click Start from a template and choose Cate Quickstart: a one-page ShopCart app with nerdy products and three unfinished features:

  1. The quantity stepper doesn’t update the item count or totals
  2. The “Remove from cart” button doesn’t do anything
  3. There’s no way to select a shipping option

Let’s fix all three.

Pair

Section titled “Pair”

Pair is for working with an agent in real time. You steer; it codes.

Open New Task (Cmd/Ctrl+N). Pair is selected by default. Paste the following and press Enter:

The quantity stepper is disabled. Enable it and wire it to the
store so + and − update the item subtotal and cart total.

This launches a Claude Code session in an isolated Git worktree: its own branch and working directory.

Run the app

Section titled “Run the app”

While the agent works, click the green arrow beside Run the site at the top right. The site launches in a terminal subtab running inside the agent’s Git worktree, so you’re seeing the agent’s actual code. Nuxt prints the local URL when it starts — look for Local: http://localhost:3000/ in that tab (the port may differ if 3000 is busy). Open the URL to confirm the stepper is broken.

Click back on the agent’s conversation in the sidebar to watch it fix the issue. Ask questions, redirect, or edit alongside it at any point.

When the agent finishes, the app hot reloads. The + and − buttons should now update the item count and totals. Confirm it looks right.

Create a PR

Section titled “Create a PR”

Click Create PR. The PR view shows every changed file. Give it a name, then decide: let the agent write the description and issue text, or do it yourself. Agents write thorough PRs and tracker tickets.

Once written, Cate shows whether the PR is mergeable. If CI is failing or approvals are required, you’ll see it. When everything’s green, click Merge PR, then End Session. Cate moves the issue to Done, stops the server, and cleans up the Git worktree. Or assign a teammate and Cate moves it into their queue.

Plan Mode

Section titled “Plan Mode”

Plan Mode is for handing off a task entirely. Describe the work, approve the spec, and step back while agents build and review.

Click New Task (Cmd/Ctrl+N) and use Shift+Tab to enter plan mode, just like Claude Code. Paste this:

Write a spec to wire the "Remove from cart" button.
It should use an existing store method to remove the
item from the cart and update totals.

The agent drafts a spec. Read through it and confirm it describes the change correctly. When satisfied, tell it to create the issue. It’s fine to say “start immediately.”

Watch the pipeline

Section titled “Watch the pipeline”

A code agent picks up the issue automatically, usually within a minute. Click Board to see the work queue and watch the issue move through the pipeline. Click the agent’s tab to watch it edit code.

If an agent needs permission, you’ll see an alert in the tab list, activity feed, or as an OS notification.

Wait for the code agent to finish. The issue moves to AI Review automatically.

The automatic review

Section titled “The automatic review”

A review agent picks up the PR and runs a two-phase check:

  1. Does the change satisfy the spec?
  2. Is the code quality acceptable?

Guardrails let you add your own gates: linting, tests, security scans.

When the review agent signs off, the issue appears in your Ready for Review queue. Wait for that before continuing.

Review

Section titled “Review”

Review sessions are for delegated PRs in your queue. The agent’s done the implementation. Review is where you bring your judgment: read the diff, try the feature, make any adjustments, and decide what ships or goes to a teammate.

The remove-button fix is now in your queue. Click into the issue to start a review session. Cate loads the PR and summarizes the changes.

Click the green arrow to run the site again and try the fix. The “Remove from cart” button should now remove the item and update the totals.

The shipping section still shows static text. Fold it into this PR — tell the agent:

The shipping section shows static text. Replace it with a dropdown
for Standard, Express, and Overnight that updates the cart total.

Click Update PR. The agent revises the code and updates the PR description. When satisfied, click Merge PR and Cate moves the issue to Done.

That’s it. Pair, delegate, review — from concept to PR.

Next steps

Section titled “Next steps”

Keep experimenting with ShopCart:

  • Connect an issue tracker to drive agents from Jira, Linear, or GitHub.
  • Set up guardrails so agents enforce your quality bar before PRs reach you.

Bring your own project:

  • Open File → New Window and point Cate at any local Git repo, or start a new project and Cate creates one for you.

Go deeper: