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

# Slaunt developer FAQ

> Hooks versus agent instructions, what's stored, multiple workspaces, and why an agent says work is done.

> [accordion] Do I need hooks, agent instructions, or both?
>
> They do different jobs. Hooks report threads and runs and enforce stops, without relying on the model. Instructions tell the model when to search and write Slaunt Context, which hooks can't do. On Claude Code and Codex use both; elsewhere only instructions are available.

> [accordion] Does Slaunt store my prompts?
>
> Only if Chat capture is set up (capture hooks or `chat_capture`), and then encrypted. Lifecycle hooks send metadata only, and Context events are one-line summaries. See [Security and data](https://docs.slaunt.ai/reference/security.md).

> [accordion] Can one agent use two workspaces?
>
> No. A token belongs to one workspace; sign the client in again with the other account to switch.

> [accordion] Why does my agent say the work is already done?
>
> It found a matching Context event, which is the point: it avoids redoing finished work. If the event is wrong, log a correcting event.


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