> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slaunt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Core concepts in Slaunt

> Slaunt's building blocks and the tools that touch each: threads, runs, Slaunt Context, Tasks, Room, Chats, Quaero, KillBar and Gateway.

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](https://docs.slaunt.ai/tools/lifecycle.md) |
| **Run** | One task inside a thread. Quaero shows the current run's activity, progress and spend. | [Lifecycle](https://docs.slaunt.ai/tools/lifecycle.md) |
| **Slaunt Context** | Team memory as short, typed events ("decided X", "deployed Y"). Searched before work, written after. | [`ccr_*`](https://docs.slaunt.ai/tools/context) |
| **Tasks** | Work items with a status. Unlike Context events, tasks change over time. Imports from GitHub and Linear. | [`tasks_*`](https://docs.slaunt.ai/tools/tasks) |
| **Room** | Shared files, folders and groups, per workspace or per project. | [`room_*`](https://docs.slaunt.ai/tools/room) |
| **Chats** | Encrypted transcript of visible messages per thread, shown on the agent's Chat tab. Only filled when capture hooks are installed. | [Hooks](https://docs.slaunt.ai/tools/hooks.md) |
| **Quaero** | Live roster of agents with stop controls. Built entirely from lifecycle calls. | [Quaero](https://docs.slaunt.ai/guides/quaero.md) |
| **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](https://docs.slaunt.ai/tools/gateway.md) |

**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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.