Cofounder Docs
Agents Overview
Understand what an agent is in Cofounder, what it consists of, which agents are created by default, and how to add new ones.
What An Agent Is
Agents are the units that do work in Cofounder.
Each one is responsible for a particular kind of job. That might be engineering work, go-to-market work, SEO, security, or infrastructure. When you start a task, you are handing that work to an agent with the right scope for the job.
Agents are organized inside departments.
Cofounder is the exception. It is the top-level agent for the workspace, accessible from the side panel. It can help create or route tasks across the workspace instead of acting like a department-specific agent.
What An Agent Includes
Every agent has a few core parts:
- Instructions that define what the agent owns and how it should behave
- Model that defines the reasoning engine the agent uses
- Integrations that define which tools and systems it can use
- Skills that add reusable guidance for a specific kind of work
- Subagents that let it delegate narrower parts of a task to another helper agent
- Department that determines which lane of the company the agent belongs to
An engineering agent and a GTM agent should have different instructions, different tools, different skills, and live in different departments.
Default Agents
After onboarding, your workspace includes default agents for the main operating areas.
The default set includes:
- Cofounder
- Engineer
- Security Engineer
- Infra Agent
- GTM Agent
- SEO Agent
Default Agent Roles
- Cofounder is the top-level workspace agent in the side panel
- Engineer is for product and app work
- Security Engineer is for security-specific reviews or changes
- Infra Agent is for infrastructure, environments, and deployment-related work
- GTM Agent is for launches, messaging, campaigns, and other go-to-market work
- SEO Agent is for search and content visibility work
Cofounder sits above that layer as the workspace-level agent, while the others are agents for specific kinds of work.
Adding New Agents
You can add new agents when you need an agent that does not already exist in the workspace. Examples include support, operations, finance, recruiting, or a specific internal workflow.
New agents usually include:
- one clear job
- the right integrations for that job
- the few skills that actually help
- subagents only when the work truly needs delegation
Agents Vs. Skills Vs. Departments
- An agent is the worker
- A skill is reusable guidance attached to that worker
- A department is the operating area that groups agents and their work