An agent is the unit of isolation in Cerca. Think of it as an always-on cloud workspace for one user, account, or business process. It owns durable context, threads, attached connections, tool access, approval settings, and a persistent sandbox filesystem. Most products create one agent per user. That keeps a user’s threads, files, memory, and connected accounts in one place. You can also create multiple agents for one user when the work needs hard separation, for example a finance agent and a support agent with different tools and approval policies. Agents inherit shared defaults from a fleet. The fleet can provide instructions, a default model, an allowlist of tools, and approval rules. If a field is not locked by the fleet, the agent can override it. Use agent configuration for stable behavior: standing instructions, the namespaces the model can reach, and the gates that keep risky actions under human control.Documentation Index
Fetch the complete documentation index at: https://docs.cerca.dev/llms.txt
Use this file to discover all available pages before exploring further.
Core concepts
Agents
Durable workspaces with configuration, context, tools, and sandbox state.