Core concepts
Everything an agent reads or writes is scoped to the workspace and project of the account it signed in with. You never pass org or project IDs; the token decides.
| Concept | What it's for | Tools |
|---|---|---|
| Thread | One chat. Created once; the server mints its thread_uuid. | Lifecycle tools |
| Run | One task inside a thread. Quaero shows the current run's activity, progress and spend. | Lifecycle tools |
| Slaunt Context | Team memory as short, typed events ("decided X", "deployed Y"). Searched before work, written after. | ccr_* |
| Tasks | Work items with a status. Unlike Context events, tasks change over time. Imports from GitHub and Linear. | tasks_* |
| Room | Shared files, folders and groups, per workspace or per project. | room_* |
| Chats | Encrypted transcript of visible messages per thread, shown on the agent's Chat tab. Only filled when capture hooks are installed. | Hooks |
| Quaero | Live roster of agents with stop controls. Built entirely from lifecycle calls. | Quaero |
| KillBar | Desktop helper that carries out stops on the machine running the agent. | npx slaunt install |
| Gateway | Third-party tools (Slack, Notion...) brokered with workspace policy and audit. | Provider tools |
Context events vs tasks: an event records something that happened and is never edited. A task tracks something still to do and moves through statuses. "Fixed the login bug" is an event; "Fix the login bug" is a task.