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

# Agent runtime

FluffBuzz runs a single embedded agent runtime.

## Workspace (required)

FluffBuzz uses a single agent workspace directory (`agents.defaults.workspace`) as the agent’s **only** working directory (`cwd`) for tools and context.

Recommended: use `fluffbuzz setup` to create `~/.fluffbuzz/fluffbuzz.json` if missing and initialize the workspace files.

Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)

If `agents.defaults.sandbox` is enabled, non-main sessions can override this with
per-session workspaces under `agents.defaults.sandbox.workspaceRoot` (see
[Gateway configuration](/gateway/configuration)).

## Bootstrap files (injected)

Inside `agents.defaults.workspace`, FluffBuzz expects these user-editable files:

* `AGENTS.md` — operating instructions + “memory”
* `SOUL.md` — persona, boundaries, tone
* `TOOLS.md` — user-maintained tool notes (e.g. `imsg`, `sag`, conventions)
* `BOOTSTRAP.md` — one-time first-run ritual (deleted after completion)
* `IDENTITY.md` — agent name/vibe/emoji
* `USER.md` — user profile + preferred address

On the first turn of a new session, FluffBuzz injects the contents of these files directly into the agent context.

Blank files are skipped. Large files are trimmed and truncated with a marker so prompts stay lean (read the file for full content).

If a file is missing, FluffBuzz injects a single “missing file” marker line (and `fluffbuzz setup` will create a safe default template).

`BOOTSTRAP.md` is only created for a **brand new workspace** (no other bootstrap files present). If you delete it after completing the ritual, it should not be recreated on later restarts.

To disable bootstrap file creation entirely (for pre-seeded workspaces), set:

```json5 theme={"theme":{"light":"min-light","dark":"min-dark"}}
{ agent: { skipBootstrap: true } }
```

## Built-in tools

Core tools (read/exec/edit/write and related system tools) are always available,
subject to tool policy. `apply_patch` is optional and gated by
`tools.exec.applyPatch`. `TOOLS.md` does **not** control which tools exist; it’s
guidance for how *you* want them used.

## Skills

FluffBuzz loads skills from these locations (highest precedence first):

* Workspace: `<workspace>/skills`
* Project agent skills: `<workspace>/.agents/skills`
* Personal agent skills: `~/.agents/skills`
* Managed/local: `~/.fluffbuzz/skills`
* Bundled (shipped with the install)
* Extra skill folders: `skills.load.extraDirs`

Skills can be gated by config/env (see `skills` in [Gateway configuration](/gateway/configuration)).

## Runtime boundaries

The embedded agent runtime is built on the Pi agent core (models, tools, and
prompt pipeline). Session management, discovery, tool wiring, and channel
delivery are FluffBuzz-owned layers on top of that core.

## Sessions

Session transcripts are stored as JSONL at:

* `~/.fluffbuzz/agents/<agentId>/sessions/<SessionId>.jsonl`

The session ID is stable and chosen by FluffBuzz.
Legacy session folders from other tools are not read.

## Steering while streaming

When queue mode is `steer`, inbound messages are injected into the current run.
Queued steering is delivered **after the current assistant turn finishes
executing its tool calls**, before the next LLM call. Steering no longer skips
remaining tool calls from the current assistant message; it injects the queued
message at the next model boundary instead.

When queue mode is `followup` or `collect`, inbound messages are held until the
current turn ends, then a new agent turn starts with the queued payloads. See
[Queue](/concepts/queue) for mode + debounce/cap behavior.

Block streaming sends completed assistant blocks as soon as they finish; it is
**off by default** (`agents.defaults.blockStreamingDefault: "off"`).
Tune the boundary via `agents.defaults.blockStreamingBreak` (`text_end` vs `message_end`; defaults to text\_end).
Control soft block chunking with `agents.defaults.blockStreamingChunk` (defaults to
800–1200 chars; prefers paragraph breaks, then newlines; sentences last).
Coalesce streamed chunks with `agents.defaults.blockStreamingCoalesce` to reduce
single-line spam (idle-based merging before send). Non-Telegram channels require
explicit `*.blockStreaming: true` to enable block replies.
Verbose tool summaries are emitted at tool start (no debounce); Control UI
streams tool output via agent events when available.
More details: [Streaming + chunking](/concepts/streaming).

## Model refs

Model refs in config (for example `agents.defaults.model` and `agents.defaults.models`) are parsed by splitting on the **first** `/`.

* Use `provider/model` when configuring models.
* If the model ID itself contains `/` (OpenRouter-style), include the provider prefix (example: `openrouter/moonshotai/kimi-k2`).
* If you omit the provider, FluffBuzz tries an alias first, then a unique
  configured-provider match for that exact model id, and only then falls back
  to the configured default provider. If that provider no longer exposes the
  configured default model, FluffBuzz falls back to the first configured
  provider/model instead of surfacing a stale removed-provider default.

## Configuration (minimal)

At minimum, set:

* `agents.defaults.workspace`
* `channels.whatsapp.allowFrom` (strongly recommended)

***

*Next: [Group Chats](/channels/group-messages)* 🐾

## Related

* [Agent workspace](/concepts/agent-workspace)
* [Multi-agent routing](/concepts/multi-agent)
* [Session management](/concepts/session)