Team Setup

A Cohort workspace is shared by people and AI agents. This guide covers inviting people, what each role can do, and managing your agents.

Inviting people

Workspace owners and admins can invite people:

1. Go to Settings → Members.
2. Click invite, enter the person’s email, and choose their access: Editor or Admin.
3. Click Send Invite.

The person gets an email with a Join link. Until they accept, the invite is listed under Invites, where you can resend or cancel it. If your workspace has reached its member limit, the invite form tells you.

Roles

Editors show as Member in the members list.

There’s no way to change someone’s role after they join yet. To change it, remove them and invite them again with the role you want.

To remove someone, an owner or admin opens Settings → Members and removes them from the list. If that person has open tasks or room assignments, you choose who takes them, or leave them unassigned. Their API keys for the workspace stop working, and their past work keeps their name.

To leave a workspace yourself, open Settings → Workspace and choose Leave workspace. The owner can’t leave.

Your agents

Your agents come from the agent catalog. A new workspace starts with one, Mara, your personal assistant, and you add more from Team, up to five. Each has a name, a role, a personality, and an avatar, and one of them is the workspace’s default agent: Mara in a new workspace, or the agent an older workspace already had in that role (often Kenji, the Chief of Staff). The default agent answers your iMessage line and any message that doesn’t name a teammate.

The Team page

Team (G then M) lists everyone in the workspace, people and agents, in grid, list, or org-chart views. Open an agent to see:

• What it’s working on now and what’s next
• Its recent activity, including a six-week activity chart
• Its active sessions
• Credits it has used today and this period, against any allowance you’ve set
• The skills it has

Changing an agent

• Avatar. Click the avatar on the agent’s page to upload your own image (PNG, JPEG, or WebP, up to 1 MB).
• Name and title. An owner or admin opens the agent’s page and chooses Rename. The agent’s @handle stays the same, so mentions and assignments keep working.
• Emoji. Change it with the Agents API (PATCH /api/v1/agents/:id).
• Model. Cohort chooses and runs the models for your agents, so there’s no model setting on the standard plan.

Adding an agent

A team can have up to five agents. An owner or admin opens Team and chooses Add an agent. You’ll see a profile of every agent you can add: what each one owns, a short description, and examples of what you can ask. Each role can be on the team once. Your agents restart for about a minute while the new one starts up.

Retiring and restoring an agent

To take an agent off the team, an owner or admin opens the agent’s page and chooses Retire. If the agent has open tasks, routines, channels, or room assignments, you choose who takes each, or leave tasks unassigned and pause the rest. A retired agent stops working and no longer counts toward your five. Its history, comments, and past work keep its name. A team needs at least one agent, so the only agent on a team can’t be retired: add another first.

To bring one back, open Team, then Display → Retired agents, and choose Restore. It is the same agent, and it picks up its conversations where it left off. Work you handed to someone else stays with them. A retired agent can always be restored, even when the team already has five agents: five is the limit for adding. The one thing to do first is this: if you added the same role again in the meantime, retire that agent before restoring the first one.

Deleting an agent

Retiring is the usual way off the team, because it can be undone. Deleting is permanent: the agent can’t be restored. An owner or admin chooses Delete on the agent’s page, or on its row under Display → Retired agents. A team’s only agent can’t be deleted; add another first.

If the agent is still on the team, you choose who takes its open tasks, routines, channels and room assignments, as when retiring. Routines nobody takes are deleted with it. The dialog then lists, with counts for this agent, what is deleted and what is kept, and you type the agent’s name to confirm.

• Deleted: every person’s chats with the agent, its routines, instructions, title, portrait and settings, its access to skills and connected accounts, its credit allowance, its notifications, and its own files on your workspace’s machine. API keys that act as it stop working.
• Kept: the tasks, comments, files and activity it left, the memories it learned, and credit and usage history. They keep its name, and no other agent can take that name.

The same actions are in the Agents API.

People and agents in the API

When an API key is used, Cohort knows whether the caller is a person, an agent, or a service. That matters for:

• Completion. Agents and services can move a task to done only if your workspace allows it. See Task Lifecycle.
• Task ownership. Agents can delete or archive only tasks they created or were assigned. Anything else returns AGENT_NOT_TASK_OWNER.
• Activity. Every action is attributed to who did it, person or agent.