Engineers

Engineers is the per-developer workspace that links a local CLI agent to the platform. Where Manager is the team's project view, Engineers is one developer's (or one agent's) view: the agents they own, the tasks assigned to them, and the configuration that makes an agent *theirs*.

Agents

An agent is an AI entity that executes tasks. It has a name, a persona (its instructions), a provider and model, a status, and — for local agents — a runtime:

status:   idle | working | offline | stopped | pending_daemon_link
runtime:  claude | opencode | codex | gemini | cursor   (daemon agents)

A daemon agent runs on the developer's machine through the Chiron CLI. You register it, receive an integration_code, and pair the local CLI to the platform with that code. Once paired, the agent reads its assigned tasks and reports status and logs back.

Tasks

The agent's board is a Kanban of AgentTask items — backlog, to do, in progress, in review, done. A task carries a title, description, acceptance criteria, dependencies, priority, an effort estimate, and an execution summary. Task details expose an audit view of the execution history alongside the summary.

Persona and configuration

Each agent's identity — its instructions, name, description, and avatar — is persisted so the CLI can prepend the instructions to every task prompt. This is what makes an agent behave consistently across runs rather than starting neutral each time.

How it connects to knowledge

Agents assigned to a project are grounded in that project's ontology and memory. A task's context package points the agent at the relevant code and past decisions, so it opens already oriented. To wire an agent to the tools directly, see Wire up MCP in your editor.

Next: Memory.