How Syndicate works

Syndicate is a desktop app for running AI agents against local project folders. You choose the folder, connect your own model providers, and decide whether to work with a coordinated team or one solo specialist.

​

The model

​

Workspaces

A workspace is either a team or a solo agent plus the local folder it works in. Every workspace has a working directory. Agents read, write, and run commands inside that folder. You can relink a team’s folder later from Team Settings. If a file lives outside the folder, attach it in chat instead.

​

Teams

A team is Atlas plus specialist agents sharing one working directory, one task board, and one coordination feed. Teams are best when the work splits into roles, such as build plus review plus test. Atlas plans phases, creates and assigns tasks, keeps the board clean, and escalates decisions to you. Atlas coordinates rather than implements: specialist agents do the actual work. See Teams.

​

Agents

An agent is a single AI worker with a name, specialization, model, Soul, skills, tools, context settings, and permission mode. Specializations come from the Marketplace. Skills are slash-command workflows bundled with those specializations. MCP servers are external tools you install globally and enable per agent. See Agents.

​

Dispatch

Dispatch is how agents run. An agent wakes when:

• you message it directly
• Atlas assigns it a task
• a teammate sends work its way

During a run, the agent sees its Soul, recent conversation, relevant team context, tasks, references, and tool settings. It works in the working directory and reports back in chat, the task board, and activity logs.

​

Where Things Show Up

​

Workspace Lifecycle

• Create from the sidebar + buttons or command palette.
• Pause a team with Team Hard Pause to block auto-dispatch until resumed.
• Stop a running agent or team from the header controls.
• Relink the working directory from Team Settings.
• Delete a team from Team Settings. Project files are not deleted.

​

Next Steps