Guilds

A guild is a pre-built team you enlist into a workspace: agents with personalities, the assignments they run, and the tables, knowledge, skills, boards, and documents they work against, all configured to work together. Enlisting one skips the blank page. Instead of writing a personality, drafting assignments, and designing a table before anything useful happens, you answer a few setup questions and the team’s first assignment runs straight away.

Everything a guild adds is an ordinary copy in your workspace. Rename the agents, rewrite their instructions, change schedules, or delete what you don’t need; nothing ties the copy back to the catalog, and later catalog changes never alter it.

The catalog

The catalog has 9 guilds, each with two agents. Every guild includes one assignment that needs no integration at all, so a real work product arrives before you connect anything.

Guild	Agents	Runs the moment you enlist
Marketing Guild	Campaign Manager, Search Analyst	Website & Brand Snapshot
Sales Guild	Deal Desk, Competitive Analyst	Competitive Landscape Brief
Engineering Guild	Backlog Engineer, Incident Scribe	Repository Health Snapshot
Product Guild	Feedback Analyst, Sprint Steward	Competitive Feature Tracker
People Guild	Recruiting Screener, People Ops	Compensation Band Blueprint
Legal Guild	Contract Reviewer, Compliance Watch	Regulatory Change Monitor
Design Guild	Systems Auditor, Research Synthesist	Accessibility Monitor
Executive Guild	Chief of Staff, Market Analyst	Competitive Intelligence Digest
Investors Guild	Portfolio Analyst, Market Scout	Market & Sector Intelligence

Open Guilds from the Agents page to browse. Each guild’s page shows everything before you commit: The roster, its Assignments (marked Scheduled where they recur), the Integrations it recommends or can optionally use and what each one unlocks, the Setup questions it will ask, Try asking prompts for its agents, and its Seeded content. You can also reach the catalog from Browse guilds on an empty Agents page, from the link in the Create agent dialog, and from the first-run setup when you create an account.

Enlist a guild

1. Open the guild and choose Enlist. The enlist dialog walks through the rest.

2. Answer the setup questions. Most guilds ask for a few details, such as your company name, your domain, or who the content is for. The company name is filled in from your organization, and questions with a default can be left alone.

3. Review the integrations. The dialog lists the guild’s Recommended and Optional integrations and marks the ones already connected. Nothing here blocks: every assignment runs from day one, and one missing a recommended integration runs at reduced capability and says so in its output until the connection lands. Connect closes the dialog and opens Skills & integrations → Integrations, so it is often simpler to enlist first and connect afterward.

4. Review and enlist. The last step counts what will be added — agents, assignments, data tables, knowledge bases, skills, boards, documents — and says what starts right away. Choose Enlist.

When a whole guild is enlisted, its lead agent opens a kickoff session that introduces the team, says what is live and what is waiting on a connection, and suggests what to ask, while the guild’s first assignment runs immediately. The success screen lists what was created, names any assignment running at reduced capability and what it is waiting for, and offers Open kickoff session.

Guild agents are shared with the workspace, so they run on company accounts: the integrations they use are the ones a workspace admin connects in Skills & integrations → Integrations. Assignments arrive enabled, and scheduled ones run on their schedules from the start.

Enlisting has no permission model of its own. It creates each agent, assignment, and table the same way you would by hand, so anyone can browse the catalog, and an enlistment succeeds when you could have built the same things yourself.

Take only part of a guild

Enlist à la carte on a guild’s page lets you tick the agents, assignments, and seeded content you want and leave the rest. When you pick something that depends on an item you left out, such as an assignment that writes to a seeded table, you are asked whether to select that too; you can keep just your pick, at the cost of it working less well. Choose Enlist selected to continue. An assignment whose own agent you did not select gets an extra step in the dialog where you give it to one of your existing agents. À la carte picks skip the kickoff session; the first assignment still runs right away if you picked it.

Enlisting the same guild again

Once a guild is enlisted in the workspace, its button reads Enlisted. Choosing it still opens the dialog, which asks you to confirm with Enlist another copy so a second team is never added by accident.

Where enlisted things show their origin

The pages of enlisted agents, assignments, and boards carry a From guild name line under their title, linking back to the guild. Each guild agent’s personality also ends with a line naming its guild and its teammates, so an agent understands when you talk about “the guild” or ask it to hand something to a colleague.

Disband a guild

Disbanding removes what an enlistment added. Open Guilds, switch to the Enlisted tab, and find the enlistment. What it added lists every item it created; Disband opens a dialog with each item that still exists already selected. Untick anything you want to keep. Items you have edited since enlisting are marked Modified since enlisting, so you can spot the ones your team has invested in.

Each selected item is deleted through the same path as deleting it by hand, with the same rules. Session history is never removed as a side effect: an agent that still has sessions — the guild’s lead has at least its kickoff run — is blocked until you delete those sessions yourself. Some deletions finish later, and a hold on an item can block one too. The dialog links each request so you can follow it, and the enlistment stays active until every request completes. Once you have resolved a blocker, choose Start new attempt.

What disbanding keeps:

• Anything you untick. It stays in the workspace as an ordinary item.
• Anything you already deleted, which the dialog shows as No longer present.
• Everything the enlistment did not create. Only the items listed under What it added are candidates for removal, so your own agents, tables, and documents are never touched. That includes an existing agent you gave an à la carte assignment to: disbanding removes the assignment, not the agent.

Guilds over MCP

The workspace MCP server exposes the same catalog and lifecycle as a guilds tool group — list and read guilds, enlist, and disband — so an external client can set up a team programmatically. See MCP clients.