slaunt
DOCUMENTATION

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.

ConceptWhat it's forTools
ThreadOne chat. Created once; the server mints its thread_uuid.Lifecycle tools
RunOne task inside a thread. Quaero shows the current run's activity, progress and spend.Lifecycle tools
Slaunt ContextTeam memory as short, typed events ("decided X", "deployed Y"). Searched before work, written after.ccr_*
TasksWork items with a status. Unlike Context events, tasks change over time. Imports from GitHub and Linear.tasks_*
RoomShared files, folders and groups, per workspace or per project.room_*
ChatsEncrypted transcript of visible messages per thread, shown on the agent's Chat tab. Only filled when capture hooks are installed.Hooks
QuaeroLive roster of agents with stop controls. Built entirely from lifecycle calls.Quaero
KillBarDesktop helper that carries out stops on the machine running the agent.npx slaunt install
GatewayThird-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.