Creating and Configuring Agents

An agent is an AI identity: a personality, skills, tools, and guardrails. Your personal agent — pinned at the top of the sidebar — is created with your account and is the default place to chat and delegate. Workspace agents are the ones you create for specific jobs.

The identity part matters more than it first appears. A one-off chat starts from zero every time; an agent accumulates. Its personality shapes every conversation, its memory carries what it learned last week into next week’s work, and its assignments give it a standing job rather than a stream of ad-hoc requests. Over time an agent stops feeling like a chat window and starts feeling like a colleague with a beat: the one who watches competitors, the one who runs the Monday pipeline report, the one who triages inbound tickets.

Creating an agent

Choose New Agent, give it a Name, and optionally a Personality. That’s the whole form — everything else is configured on the agent’s page, and both can be refined later.

Names deserve a moment of thought, since they are how the agent appears across sessions and the Inbox, and how you @-mention it in a conversation. Short, role-shaped names wear well:

• Scout — watches the competitive landscape and maintains a tracker table.
• Pipeline — compiles the weekly sales report every Monday.
• Triage — fields support tickets delivered by a webhook as they arrive.

The personality is the agent’s standing character: how it writes, what it cares about, how it approaches work. A useful one reads like a briefing you’d give a new hire rather than configuration. For example:

You are Scout, a competitive-intelligence analyst. You are skeptical of vendor announcements until you can confirm them from a second source, and you always link the source. You write in short, factual sentences and lead with what changed since last time. When you are uncertain, say so plainly instead of hedging. Prefer a table over prose for anything with more than three items.

Start with your personal agent

You don’t need a roster on day one. Chat and delegate through your personal agent first; when you notice a job recurring — the same report, the same research, the same triage — that’s the moment to create a dedicated workspace agent for it, or to turn the conversation itself into an assignment with Make recurring.

The agent page

The left side of an agent’s page is its feed: a composer and the agent’s sessions. The right side is configuration.

Personality sits in the header, always in view: a preview of how this agent thinks, communicates, and approaches tasks, applied to every conversation. Click it to edit — the editor includes AI refinement, and an agent allowed to adjust its own personality will also refine it as it learns. Whether it may do that is a self-improvement guardrail, so you decide which agents earn that latitude.

The configuration cards below cover the rest:

• Assignments — recurring tasks this agent runs on a schedule. See Assignments.
• Abilities — the skills, integrations, and private credentials this agent uses. See Skills and Integrations.
• Memory — knowledge the agent saves across conversations. See Memory and storage.
• Storage — the agent’s durable working storage.
• Guardrails — limits on what this agent can reach or change. See Guardrails.
• Messaging — on your personal agent only: link Slack so you can chat from there. See the Slack guide.

Together the cards answer the questions you would ask about any coworker: what is this agent responsible for (Assignments), what can it do (Abilities), what has it learned and what is it working on (Memory and Storage), and what is it not allowed to do (Guardrails).

A status line under the name keeps you oriented — whether the agent is running or idle, its current session, and when its next scheduled run is due. The pause control stops all automated triggers while still allowing manual runs — useful while you rewrite an assignment’s instructions and don’t want the old version firing on schedule mid-edit.

Sharing an agent

Workspace agents start private to you, which makes them a safe place to iterate: tune the personality, run a few sessions, adjust the guardrails, all before anyone else depends on the results. The Share button opens a dialog where you choose who can use the agent and what they can do — give everyone in the workspace a tier (view, use, or edit) or add specific people, each at their own tier. Granting the whole workspace use while keeping edit to one or two owners is a common shape: the team gets the agent, and its personality, assignments, and guardrails stay coherent.

Star the agents you use most to keep them at hand.

Patterns that work

• One agent per job — an agent with a single clear beat (competitors, pipeline, tickets) develops sharper memory and a more useful personality than a generalist asked to do everything.
• Personal agent as front door — delegate everything there first, and spin out a workspace agent when a duty becomes recurring.
• Shared team agent — one well-tuned agent shared at the use tier, with edit access kept to its owners.