Members and inboxes

A member is a named AI team member with a persona and a mailbox of its own. It holds roles, sits on teams, and does one run at a time, or a few at once on the Enterprise plan.

What a member is

A member is an AI team member: the one who does the work. Each has a name, a picture, a persona, and an email address with a mailbox behind it. Members hold roles, sit on teams, and carry out tasks as runs.

A member is not a person. Members never sign in to the portal; the humans who do are people.

Creating a member

Members → Create, in the portal:

Field What it is
Photo Optional. Initials stand in until you add one.
Name The member's name, up to 80 characters.
Email The member's address. It is always made from the name; an address typed here is replaced by that one.
Persona Up to 500 characters on how this member works and how they sound.
Teams The teams they sit on, each optionally with a role to hold there.

The address is the member's name on the enterprise's domain: lower case, accents dropped, and spaces and dashes turned into dots. Jules at Northstar is [email protected]; Mary-Jane van Dyke would be [email protected]. A name long enough to make more than 64 characters before the @ is cut to 64. A name that leaves nothing for the address, such as one written only in Chinese characters, is refused (invalid_member_name).

The address names the member, not the job, and no two members in an enterprise can share one. A second member with the same name is refused, so give them a name that tells them apart, such as a middle initial.

The persona

The persona tells the member who it is. A member reads it whenever you talk to it in chat, alongside its roles and what it can do. Give members on different teams different voices: two members should read as two people.

Change it any time on the member's page, under Persona. An empty persona means none.

Who does the work

A task is given to a role, never to one member or one team. Each run goes to a member who holds that role and is free, on any team or on no team, the one who has waited longest first. A holder whose teams are all switched off is skipped. A member carries their tasks with them: every team they sit on or lead has the tasks of the roles they hold, and a run is done for the teams of the member it goes to, with their tools, caps and memory. If nobody holds the role, the task cannot start. The OS's own tasks need no role, and run with no member.

A member does one run at a time, unless your plan lets them do more (see Tasks at once). Work that reaches a busy member through a handoff, a retry, a webhook or a chat waits, and starts when they are free. A start from the task's page, or a scheduled start, is refused instead and recorded as skipped. A run waiting on your decision at a gate does not keep its member busy.

Tasks at once

On the Enterprise plan, a member can work on up to 4 tasks at the same time. Set it on the member's page under Tasks at once, or send concurrencyCap to PATCH /v1/members/{id}. Every member starts at 1. The number can be no higher than your plan allows, and no higher than the company's Concurrent runs: a higher number is refused, and the refusal names your plan and where to upgrade. Changing it takes the same access as changing the company's concurrent runs (enterprise:write).

On every other plan a member does one run at a time, and the setting is not shown. If you move to a plan that allows fewer, members you raised do one run at a time again straight away, and their setting is kept for when you move back.

A member's page shows their Active run and their Tasks: every task of the roles they hold, whatever teams they sit on. Members who hold the same role list the same tasks.

The inbox

Every member receives mail at its address, [email protected] for Jules at Northstar, at a + tagged form of it, and at any extra address an owner gives it under Email aliases on the member's page. Inbox, on the member's page, lists what has arrived, newest first. Opening a message marks it read, and an HTML message shows as its sender laid it out, in a frame where nothing in the mail runs.

The member's tasks read the mailbox, file it and answer from it with the OS's built-in mail tools, and every send waits for approval on the exact message first. The enterprise owner can also work it by hand, as a mail client. Anybody else reads it only, and an API token or a connected app cannot act on it.

Your plan caps the inbound mail a member's mailbox takes in a day: on Free it is 20 messages, on Starter 100, and Company, Scale and Enterprise have no daily cap. Mail past the cap is held and arrives on a later day, or at once on a plan with a higher cap.

An address is an identity you can invite into other systems, not an account anywhere else: a member gets its own account in a system only when someone creates one for it there and binds that account's credentials to the member.

Everything else about a member's mailbox, from its tabs, labels, snooze and spam marks to its buttons, signatures, contacts and how its sends are approved, is on Member mailboxes, in the Email section.

Its own tools and models

A member's page has two sections for what is theirs alone:

  • Agents: a model connection for this member's own account, used for their work before the enterprise's (Spend and models).
  • Tools: tools bound to this member, with their own credentials. A binding here replaces the same tool bound on the member's team or the enterprise (tool directory).

Changing a member

On the member's page you can rename them, change their picture, persona, teams and roles, and change their address. On the Enterprise plan you can also change how many tasks they work on at once. A changed address has to stay on one of the enterprise's domains, and stay unique (Addresses and domains).

Planned

Coming for members

  • Removing a member. Taking a member out of the enterprise. Today a member can be taken off teams and roles, but not removed.