# Kairo Crew

> Named agents with their own job, goals, memory and computer.

Source: https://docs.coline.app/kairo/crew

Crew members are agents you name and give a job. Each one has a profile, a DM with you, its own goals and memory, and a cloud computer. They read along in conversations like a teammate and keep working when you're away.

## Personal and team crew

|                            | Just for me                                         | For the team                                          |
| -------------------------- | --------------------------------------------------- | ----------------------------------------------------- |
| Works for                  | You, on your goals, your computer and your accounts | The workspace, with a job anyone can ask about        |
| Who can see and message it | Only you                                            | Anyone in the workspace, in channels, threads and DMs |
| Computer                   | Your computer                                       | Its own computer, with team logins an admin added     |
| Who can add one            | Anyone                                              | Workspace admins, or roles they allow                 |

## Add a crew member

From **Crew** in the Kairo sidebar, choose **Add to your crew**. Start from a built-in crew member or from scratch:

* **Name** and **avatar**. The name can't be Kairo or match another crew member.
* **Instructions:** what it does and where its limits are, such as "Triage new posts in #support. Tag the right team, draft a first reply, and ask before emailing anyone." It reads these on every run.
* **Voice** (optional): how it talks, such as "Dry and brief. Says when it's unsure."
* **Tools:** which tool groups it can use. Search, reading and memory are always on.
* **Model**, **owner** and **monthly budget**. The owner can edit the crew member and is accountable for its work.

Nothing is created until you press **Add to crew**. A new crew member says hello in your DM and asks one question about the job.

## Working with a crew member

* **DM it** like a person. Ask for something once and it does it; it doesn't ask you to confirm.
* **Mention it** in a channel or thread to add it there. It reads along and answers when it's addressed, including replies to its own questions.
* **Hand off from Kairo:** ask Kairo for ongoing work ("keep an eye on #general and tell me if anyone mentions pricing") and it starts a goal for the right crew member, right in the chat.
* Things a crew member creates or mentions (emails, docs, tasks, events, repositories, Change Requests) show as cards under its message.

Its profile has tabs for **Goals**, **Activity**, **Computer**, **Memory** and **About**.

## Goals

A goal is work a crew member owns until it's done.

* **Goals** have a "done when" condition, a plan the crew member writes and keeps current, helpers it starts (such as a Code session), and outputs.
* **Tracking** goals watch for something and tell you when it happens ("only when the price drops below $400").
* Set an end date, or none. Mark a goal done or cancel it any time; completed actions aren't undone.
* **Team goals** post in a channel and run on the crew member's own computer. Approvals still come to you.

Personal goals are private to the person who set them up.

## Needs you

When a crew member can't continue without you (a question, a decision, a service that isn't connected, or a step only you can do), it raises a **Needs you** item instead of guessing. These show in its DM and under **Waiting on you** on [Home](/home).

## Always on

Turn on **Always on** and a crew member checks in on its own: every 30 minutes, or every 2 hours while you're quiet. It only messages you when it finds something worth your time, and says where it noticed it. It pauses after 14 days without you opening Coline.

**Daily digest** writes one short entry a day in a private doc: what changed and what's next.

## Routines

Routines are standing work on a schedule or when something happens, such as "post a summary in #team every Friday at 4 PM". See [routines](/kairo/routines).

## What it may do without asking

In **Kairo → Customize → Crew**, set what your crew may do without asking, for each kind of action:

| Action                              |   |
| ----------------------------------- | - |
| Read and look things up             |   |
| Change things in Coline             |   |
| Send email and messages             |   |
| Delete things                       |   |
| Share or post outside the workspace |   |
| Buy something                       |   |
| Sign in to websites, submit forms   |   |
| Run commands on the computer        |   |

For each, choose **Do it without asking**, **Ask me first** (it shows the exact action and waits), or **Hand it to me** (it never does it, and asks you to do that step). Approvals you give can be once, for one goal, until a date, or always.

**Stop everything** stops running work, pauses every goal and schedule, turns off Always on, and puts your computer to sleep.

## Computers

Crew members do browser, terminal and desktop work on a cloud computer. Watch it live in the **Computer** tab and take over at any time. Website sessions stay signed in until the site expires them; connected-account tokens are never on the computer. You can reset or recover a computer from its saved disk. Computer time uses [Code credits](/plans#credits).

## Integrations

Crew members can use services you connect, such as a mailbox or calendar, in **Settings → Integrations** or from their profile. Team connections are opt-in for each crew member. Integrations are in beta.

## Budgets

Crew work draws Kairo credits from the workspace's shared bank. Each crew member has a monthly budget, 30% of the workspace's credits by default, which the owner or an admin can change. The **About** tab shows what it's used this month.