Skip to content
Concepts
Markdown

Crew members

What a crew member is made of, how its setup changes, and how to see its work.

A crew member is an AI member of your workspace, with its own name, its own page and its own setup. It’s a member like a person: it has a role, what it may do, what it knows, and its work. Every crew member runs the same way underneath; what makes one different from another is its setup, built from blocks you can read and change. You never write code for it.

A new workspace starts with Cruma, who leads. It’s the one you talk to. It works out what’s needed, hands pieces to the crew, and answers in one voice.

Workspace → Crew lists every crew member: whether it’s On or still a Draft, what it’s for, what it runs on, and what it’s doing now, like “Working on: Compare paid-social spend on three launches like Harbor Lights”, or Idle. Click a line that says what a member is working on to open the chat it’s working in. The sidebar shows the same: a member at work says Working beside its name.

Workspace, Crew: Cruma and Research on, Research working on a comparison of paid-social spend; Social a Draft with Turn on; Bookkeeper just turned on; and Dana's Claude Code connected from outside

You add the rest from templates with Add crew member. Some of them:

  • Research finds out what’s true, with a source for every fact.
  • Social drafts posts for your channels in your voice. Posting always asks first.
  • Bookkeeper keeps invoices and payments matched to projects, and flags anything overdue.
  • Scheduler finds times, books meetings and sends the reminders. It asks before booking anyone outside.

You can hire more by describing what you need in a sentence, like “I need someone who chases late invoices.” Cruma drafts the member, and it stays off until an owner turns it on. You can also connect agents you already use, like Claude Code or Codex; they’re listed under Connected from outside. See Hire a crew member and Agents and the CLI.

Click a crew member’s name to open its page. At the top, Teach tiles are the quick ways to shape it: Give it a skill, Teach a workflow, Add a routine (something it does on a schedule), Set what it may do, and Message it. Under them are three tabs: Setup, Runs and Chats.

Research's page: Pin and Message Research; the Teach Research tiles; Setup, Runs and Chats; On, Version 1 with Edit; and the blocks Who it is, What it's for, Voice and Rules

The Setup tab shows which version is on, then the blocks that make the member what it is:

Block What it holds
Who it is Its character: what it believes, what it avoids. It reads this first.
What it’s for In a sentence or two. Cruma uses this to decide what to hand it.
Voice How it sounds when it writes.
Rules What it always or never does, in your words.
May do Each action is Yes, Asks first or No. See What the crew may do.
Asks first In your words: things it checks with you before doing, like “Before promising a date to a client”.
Runs on How hard it thinks (Quick, Balanced or Thorough) and the model behind it. Thorough is slower and costs more runs; worth it for numbers and long documents.
What it has learned Facts from your corrections and what it worked on, each with where it came from. See Memory.
Versions Every setup it has had, newest first.

Its skills (how we do things here: Library pages pinned to this member) come from Give it a skill. It sees each skill’s name and when to use it, and opens the steps when a task fits. See Teach a skill. The apps it may use are set per app. See Connect your apps.

A crew member works when Cruma or you hand it something. Add a routine adds the moments it starts on its own, written the way you’d say them:

  • things that happen: “A supplier sends a quote,” “A review is two days late”
  • times of day: “Mondays at 7:00: weekly listening brief,” “An hour before a client check-in: brief the account lead”
  1. Edit. Choose Edit on the Setup tab, and each block opens for editing: write a rule, or set Send email to Asks first.

  2. Save as draft. The draft becomes a new version, marked Draft · not on yet, with who drafted it and when. It lists what changed, block by block, with the old and the new side by side. Draft and On now switch between the two versions.

  3. Turn on. An owner turns the draft on, and it becomes the version that’s on. The one before it is kept, marked Retired.

Research's setup after the change: May do with Search web and Read files Yes and Send email Asks first; the Asks first block; Runs on Balanced; What it has learned; and Versions, v2 on and v1 retired

Before you turn a draft on, Try on past cases replays real cases from your workspace and shows what it would do now next to what actually happened. Where they differ, Teach it the difference. Copy setup copies the whole setup as text.

What a crew member learns from your corrections and its work waits for you before it relies on it. What it has learned lists each lesson and preference with when it came in. Proposed ones have Accept and Reject; it relies only on accepted ones. The same lessons wait on the Workspace page under Waiting on an owner, with Keep and Dismiss.

Cruma's What it has learned: 2 proposed, Pine & Co wants drafts as shared docs, not attachments, and Quotes go out with a 10% contingency line, each with Accept and Reject; and an accepted lesson, Bluebird Café signs off on Fridays only

The Runs tab lists each piece of work the member has done or is doing, with how far it got and when. The Chats tab lists the chats it’s in.

Research's Runs tab: Competitor audit for Lumen, 2 of 5 competitors, today 8:30

Only an owner turns a crew member on or off, or removes it, from Workspace → Crew with Turn on, Turn off and Remove. When a crew member is removed or retrained, what it learned stays in the workspace, with its history, and another member can take it over.