@markusylisiurunen/tau 0.3.76 → 0.3.78

package/dist/core/static/tau_docs/remote-sessions.md

@@ -91,7 +91,7 @@ Remote `--new` supplies the conventional creation attribute `source: "tui"`. It
 
 ## Select an execution environment
 
-A session can use a local host directory, an already-provisioned Cloudflare Sandbox, or an already-provisioned Fly Sprite. In all cases, the execution cwd is an absolute path inside that environment.
+A session can use a local host directory or an already-provisioned Fly Sprite. In all cases, the execution cwd is an absolute path inside that environment.
 
 ### Host-local directory
 
@@ -103,22 +103,6 @@ tau attach --new --cwd /srv/workspaces/tau ws://host.example:8787
 
 The host process executes agent-visible filesystem and command operations on its own machine. Tau does not clone, pull, or provision a repository.
 
-### Cloudflare Sandbox
-
-The host must already have a named bridge in `cloudflareSandbox.bridges`, and the sandbox must already exist:
-
-```sh
-tau attach \
-  --new \
-  --execution-kind cloudflare-sandbox \
-  --cloudflare-bridge production \
-  --cloudflare-sandbox sandbox-42 \
-  --cwd /workspace/tau \
-  wss://tau.example.com
-```
-
-`--cloudflare-bridge` identifies host configuration. `--cloudflare-sandbox` identifies an existing sandbox reachable through that bridge. Tau does not create the sandbox or copy a repository into it.
-
 ### Fly Sprite
 
 The host must already have a named API target in `flySprites.apis`, and the Sprite must already exist:
@@ -166,7 +150,7 @@ An attached session spans three logical machines even when two happen to share o
 - command execution, platform, PATH, and runtime dependencies
 - automatic-compaction archives and other target-side temporary files
 
-This is why changing a host theme does not affect a remote TUI, why `!git status` runs against the execution environment, and why a custom diff application opens on the attaching machine. [Ownership and scope](ownership-and-scope.md) applies the same model across Tau.
+This is why changing a host’s theme selection does not affect a remote TUI, why `!git status` runs against the execution environment, and why the built-in diff review tool opens on the attaching machine. [Ownership and scope](ownership-and-scope.md) applies the same model across Tau.
 
 ## Reload or restart the correct process
 
@@ -177,8 +161,8 @@ Different changes have different owners:
 | Project config, model overlays, personas, prompts, skills, or AGENTS.md in the execution environment | Wait for idle, then run `/reload`. |
 | Effective model `apiKeys` in execution-environment or session configuration | Wait for idle, then run `/reload`; new sessions also resolve the current values. |
 | Managed Codex auth changed with `tau auth` | No host restart; auth storage is read again on later credential resolutions. |
-| Attaching themes, diff launcher, speech config, or configured client tools | Restart `tau attach`. |
-| Host process environment variables, history target, WebSocket listener, Cloudflare bridge, Fly API target, or host startup flags | Restart `tau serve`. |
+| Attaching themes, speech config, or configured client tools | Restart `tau attach`. |
+| Host process environment variables, history target, WebSocket listener, Fly API target, or host startup flags | Restart `tau serve`. |
 | Host Tau package, built-in tools, protocol, session recovery code, or built-in documentation | Upgrade and restart the host. |
 | TUI package, keybindings, rendering, local speech, or client-tool implementation | Upgrade and restart the attaching client. |
 
@@ -215,9 +199,9 @@ Avoid downgrading a host that has already written sessions with a newer storage
 The host lists only stored sessions whose execution-environment kind it can currently restore. Confirm that:
 
 - the connection uses the same host user and home directory as the original process
-- the Cloudflare bridge id or Fly API id still exists in host configuration
+- the Fly API id still exists in host configuration
 - host credentials are available to the restarted process
-- the target sandbox, Sprite, or local directory still exists
+- the target Sprite or local directory still exists
 - the session was created on this host rather than another machine with a different store
 
 Do not edit the session JSON to change environment identity. Restore the owning configuration or target instead.

package/dist/core/static/tau_docs/security.md

@@ -26,7 +26,7 @@ The execution environment supplies more than source files. Tau can load project
 
 A repository checkout is therefore part of Tau's trust boundary. Before using it with meaningful credentials or write access, inspect relevant `.tau/`, `.agents/`, and `AGENTS.md` content, including nearer nested levels. Pay particular attention to:
 
-- persona system prompts, tool lists, subagent definitions, and model launch allowlists;
+- persona system prompts, tool lists, and model launch allowlists;
 - skill instructions and any scripts they direct the agent to run;
 - model overlays that replace endpoints, headers, capabilities, or token limits;
 - project configuration that supplies API keys, Nook targets, model notices, or hosted-environment definitions;
@@ -100,7 +100,7 @@ Before enabling one:
 
 A project `enabledClientTools` list is permission to select an already trusted global definition. Unknown selected names are ignored, so verify effective advertisement after changes. Start an untrusted project with `--no-client-tools` until its selection has been reviewed.
 
-The TUI's diff launcher is also a client-local process. A custom `diffTool.command` and its configured environment should be treated as trusted code.
+The TUI's built-in diff review tool is also a client-local process.
 
 ## Use code mode as a capability boundary
 

package/dist/core/static/tau_docs/session-protocol-methods.md

@@ -63,12 +63,6 @@ Creates a session in one explicitly selected execution environment.
 params: {
   executionEnvironment:
     | { kind: "local"; cwd: string; env?: Record<string, string> }
-    | {
-        kind: "cloudflare-sandbox";
-        bridgeId: string;
-        sandboxId: string;
-        cwd: string;
-      }
     | {
         kind: "fly-sprite";
         apiId: string;
@@ -83,7 +77,7 @@ params: {
 result: { sessionId: string }
 ```
 
-`cwd` must be absolute inside the selected execution environment. Cloudflare sandboxes and Fly Sprites must already exist and be reachable through a host-configured resolver. Tau does not provision a target or repository.
+`cwd` must be absolute inside the selected execution environment. Fly Sprites must already exist and be reachable through a host-configured resolver. Tau does not provision a target or repository.
 
 `attributes` is required, including when empty. It accepts at most 32 immutable pairs; keys are 1 to 64 characters and values at most 1,024 characters. Tau stores the supplied strings without inferring missing provenance. Conventional attributes and their use are covered in [sessions](sessions.md) and [history](history.md).
 

package/dist/core/static/tau_docs/session-protocol.md

@@ -108,6 +108,8 @@ Observation controls delivery, not session ownership. `session.unobserve` stops
 | `tools`, `operations`, `agents` | Mutable semantic state referenced by timeline items or client views. |
 | `facets` | Versioned client-facing metadata. Unknown facet kinds and versions should be ignored. |
 
+`bootstrap.prompt.subagentSystemPrompt` is present when subagent launches are enabled. Each catalog persona has a `subagentLaunchModels` allowlist. Subagent records have task titles and IDs, not worker-type names.
+
 Render active transcript order from `timeline.items`, not by sorting or filtering `messages`. A timeline item either contains a notice or references a message, tool, or operation in the corresponding snapshot collection. Some model-visible messages intentionally have no timeline item.
 
 The timeline has an `epoch`, a per-epoch sequence high-water mark, and ordered items. Successful compaction replaces the active recoverable timeline and advances the epoch. Rewind stays in the same epoch, removes later items, and preserves the sequence high-water mark so sequence numbers are not reused.

package/dist/core/static/tau_docs/sessions.md

@@ -36,7 +36,7 @@ Only one logical turn runs at a time. Input sent during active work has two usef
 - A queued message waits for the session to become idle, then starts an independent turn.
 - Steering joins the active logical turn at a safe continuation boundary.
 
-In the TUI, Enter queues and Ctrl+Enter steers while work is active. When idle, either starts a normal turn. Pending messages are visible to every observer of the same live hosted session. Alt+Up cancels queued messages and steering that has not been applied and restores the text to the editor.
+In the TUI, Enter steers and Ctrl+Enter queues while work is active. When idle, either starts a normal turn. Pending messages are visible to every observer of the same live hosted session. Alt+Up cancels queued messages and steering that has not been applied and restores the text to the editor.
 
 A turn captures its model, persona, reasoning, system prompt, tools, retry policy, and compaction policy when it starts. Tool subturns and steering continuations keep that captured specification even if reasoning or host configuration changes meanwhile. A queued turn captures the then-current specification when it later starts.
 
@@ -107,7 +107,7 @@ Compaction replaces older model-visible conversation context with a synthetic su
 
 ### Automatic compaction
 
-Automatic compaction runs before a model subturn when fresh provider usage plus newly added estimated context exceeds the configured threshold. The threshold is the model context window minus `autoCompact.reserveTokens`. Tau keeps a recent tail bounded by `autoCompact.keepRecentTokens`, summarizes older context, and can compact more than once during a long logical turn.
+Automatic compaction runs before a model subturn when fresh provider usage plus newly added estimated context exceeds the fixed threshold. The threshold is the model context window minus 16,384 tokens. Tau keeps a recent tail with a target budget of 20,000 tokens, capped by that threshold, summarizes older context, and can compact more than once during a long logical turn.
 
 The summary model may copy important original user messages verbatim into the summary. Recent retained messages stay available to the model, although unusually large textual tool and recovery results may be truncated in retained context. Tau records the compaction as a new active context segment.
 
@@ -119,18 +119,6 @@ The continuation also requires the archive guide to be present in model context
 
 These archives are temporary recovery aids, not backups. Archive failure does not block compaction, and execution-environment cleanup may remove them.
 
-Configure the policy in [configuration](configuration.md):
-
-```json
-{
-  "autoCompact": {
-    "enabled": true,
-    "reserveTokens": 16384,
-    "keepRecentTokens": 20000
-  }
-}
-```
-
 ### Intermediate system instructions
 
 Tau supports plain-text system instructions in conversation history separately from the persona/base prompt. These records are hidden in the TUI, persisted for recovery, recorded as system entries in searchable transcript history, and sent to the model in conversation order. The initial persona/base prompt is not recorded in transcript history. Providers that cannot represent intermediate system messages may fold their instructions into the leading prompt through the model adapter.

package/dist/core/static/tau_docs/skills.md

@@ -79,7 +79,7 @@ The frontmatter contract is:
 | `metadata` | Optional map whose keys and values are strings. |
 | `allowed-tools` | Optional non-empty string. It is accepted for skills-format compatibility but currently ignored by Tau. |
 
-Unknown frontmatter fields are discarded. `allowed-tools` does not enable, disable, or restrict any tool. Tool availability comes from the active persona and, for a subagent, its subagent definition. See [tools](tools.md) and [subagents](subagents.md).
+Unknown frontmatter fields are discarded. `allowed-tools` does not enable, disable, or restrict any tool. Tool availability comes from the active persona; subagents inherit its eligible tools. See [tools](tools.md) and [subagents](subagents.md).
 
 Keep the description useful without copying the full workflow into it. Tau initially exposes the name, description, and `SKILL.md` path. The agent opens the file after activation, then reads only the referenced resources needed for the task.
 
@@ -133,28 +133,6 @@ Skill references compose. If `release-check` instructs the agent to use `@@skill
 
 After activation, the agent reads `SKILL.md` from the path in the discovered index. It should load only relevant files from `references/` or `assets/`, and prefer provided scripts when they implement the required workflow. Skills are treated as read-only unless the user explicitly asks to edit them.
 
-## Installing starter skills
-
-Tau ships starter prompts and skills that can be copied into a project:
-
-```bash
-tau install
-```
-
-By default this installs all starter prompts and skills under the current directory's `.tau/`. To install one skill:
-
-```bash
-tau install --skill code-review
-```
-
-To install under `~/.config/tau/` instead:
-
-```bash
-tau install --global --skill commit
-```
-
-Existing skill directories are skipped. `--force` replaces the entire same-named target directory, including files that are not present in the starter copy, so use it only when replacement is intended. `--prompt` and `--skill` are mutually exclusive. See [prompts and project context](prompts-and-project-context.md) for the prompt side of `tau install`.
-
 ## Applying changes and checking discovery
 
 A running TUI session keeps its current content catalog and prompt context until it reloads. Run:

package/dist/core/static/tau_docs/speech-generation.md

@@ -152,7 +152,7 @@ The output parent directory must exist. Neither the requested WAV nor `<output>.
 
 Stdout on success is one JSON object with absolute `output`, `artifacts`, and the number of `batches`. The manifest contains the script text; keep artifacts private for sensitive scripts.
 
-Failures exit nonzero and report the retained directory. Requests are not automatically retried because a failed request may already have incurred a charge.
+Failures exit nonzero and identify invalid script fields, chunks, or turns before generation, or the failed batch and processing stage afterward. Existing output or artifact paths require a fresh `--output` path; preserve recovery artifacts. Errors after output preparation report the retained directory, which may be incomplete. If final publication fails, copy the completed `assembled.wav` to a fresh path instead of generating again. Requests are not automatically retried because a failed request may already have incurred a charge; another generation request may incur another charge.
 
 To recover after a later batch fails, inspect the manifest's `completed` flags and chunk mapping. Generate only the unfinished chunks to a fresh output path, then assemble the completed PCM files from both runs in script order. Request stitching does not carry over between invocations.
 

package/dist/core/static/tau_docs/subagents.md

@@ -1,87 +1,24 @@
 # Subagents
 
-Subagents are host-supervised background agent threads created by the main agent. They are useful when work can proceed independently, needs a separate context, or benefits from a deliberately narrower tool set. A subagent is not a second session and does not have its own persona file. Its definition belongs to the active persona.
+Subagents are host-supervised background agent threads created by the main agent. They are useful when work can proceed independently or needs a separate context. A subagent is not a second session and does not have its own persona file.
 
-The persona decides which subagent names exist. The host enforces launch models, tools, working directory, concurrency, follow-up state, interruption, and cleanup.
+## Background workers
 
-## The built-in `default` subagent
+Subagents are general-purpose background workers with no named types. Multiple instances can run concurrently, each with its own task and conversation.
 
-Tau provides one built-in subagent named `default`. It is a general-purpose background worker and has explicit trigger sensitivity. Built-in personas enable it, and a standalone custom persona also enables it when `subagents` is omitted.
+The worker inherits the active main persona's model-facing behavior through Tau's maintained wrapper. Its instructions and description are not configuration surfaces. Supply task-specific instructions in the launch prompt, including any relevant skill guidance.
 
-The `default` subagent inherits the active main persona's model-facing behavior through Tau's maintained wrapper. Its wrapper and built-in prompt are implementation-owned and are not configuration surfaces. It cannot be overridden in persona frontmatter.
-
-Disable it explicitly when a persona should expose only named custom workers or no subagents:
-
-```yaml
-subagents:
-  default: false
-```
-
-If `subagents` is omitted by a persona that extends a built-in, Tau inherits the base persona's entire subagent map. If a persona supplies a `subagents` map, Tau builds a new map from it and adds `default` unless the map says `default: false`.
-
-## Defining custom subagents
-
-Custom definitions live under `subagents` in a [persona](personas.md):
-
-```yaml
-subagents:
-  default: false
-  dependency-auditor:
-    description: Audit dependency changes and report concrete risks. Trigger: explicit.
-    systemPrompt: >-
-      Inspect the requested dependency change. Verify lockfile and release implications,
-      then return prioritized findings with paths.
-    tools:
-      - bash
-      - history
-    launchModels:
-      - anthropic/claude-haiku-4-5:low
-      - openai/gpt-6.1-sol:high
-```
-
-A custom subagent name must:
-
-- contain 1 to 64 characters;
-- use lowercase letters and digits;
-- use single dashes between segments; and
-- begin and end with a letter or digit.
-
-`dependency-auditor` and `review2` are valid. `DependencyAuditor`, `dependency_auditor`, and `-review` are not.
-
-Each custom definition accepts:
-
-| Field | Contract |
-| --- | --- |
-| `systemPrompt` | Required non-empty string containing the subagent's base instructions. |
-| `description` | Optional non-empty catalog description. Include trigger sensitivity here when needed. |
-| `tools` | Optional list of eligible subagent tools. Omission inherits eligible tools from the main persona. |
-| `launchModels` | Optional allowlist of exact model overrides accepted by `spawn_agent`. |
-
-Unknown fields are discarded. In particular, `provider`, `model`, `reasoning`, and `serviceTier` inside a subagent definition do not configure its runtime. Use `launchModels` for approved launch-time model changes.
-
-A custom entry cannot be `false`; only `default: false` has disable semantics. Every custom entry requires `systemPrompt`.
+Availability follows the main persona's tool list. Built-in personas and standalone custom personas that omit `tools` enable the five supervision tools. A custom persona can prevent launches by providing an explicit `tools` list without `spawn_agent`; omit all five supervision tools when no subagent interaction is wanted. There is no separate subagent enable or disable setting. See [personas](personas.md).
 
 ## Trigger sensitivity
 
-Trigger sensitivity is expressed in the `description`, not in a separate field:
-
-- **eager**: use proactively whenever the capability would help;
-- **balanced**: use when the request clearly matches, which is the default when no trigger is stated;
-- **explicit**: use only when an active instruction names the subagent.
-
-Use a clear phrase such as `Trigger: explicit.`. An exact user reference looks like:
-
-```text
-@@agent:dependency-auditor
-```
-
-An exact reference in the user request, an active `AGENTS.md` instruction, or the instructions of an already-active skill explicitly activates that subagent. A subagent reference tells the main agent which capability to use; it does not itself create a thread. The main agent still calls `spawn_agent`.
+The main agent launches subagents only when the user or active instructions explicitly request delegation. Ask for a subagent in ordinary language; no named agent tag is needed. A request does not itself create a thread: the main agent still calls `spawn_agent`.
 
-Trigger sensitivity is agent-facing policy. The host enforces whether the named subagent exists, but it does not infer whether a prompt semantically satisfied `eager`, `balanced`, or `explicit`.
+This is agent-facing policy. The host validates launches but does not infer whether a prompt semantically authorized delegation.
 
 ## Tool inheritance and restriction
 
-The persona-configurable subagent tool subset contains only:
+The eligible inherited tools are:
 
 - `bash`
 - `write`
@@ -89,14 +26,13 @@ The persona-configurable subagent tool subset contains only:
 - `view_image`
 - `web`
 - `history`
+- `nook`, when Nook is configured
 
-Tau then adds intrinsic `tau_docs` to every subagent registry, independently of this subset. Neither a persona nor a subagent `tools` list can disable it. Apart from `tau_docs`, subagents do not receive Nook, goal controls, subagent supervision tools, client tools, or TUI-local tools.
+Tau then adds intrinsic `tau_docs` to every subagent registry, independently of this subset. A persona’s `tools` list cannot disable it. Apart from `tau_docs`, subagents do not receive goal controls, subagent supervision tools, client tools, or TUI-local tools.
 
-When `tools` is omitted, Tau filters the main persona's tool list to the eligible names above. For example, a main persona with `bash`, `edit`, `history`, and `spawn_agent` gives an omitted subagent list of `bash`, `edit`, and `history`.
+The worker inherits the intersection of the main persona's tools and those seven eligible names. For example, a main persona with `bash`, `edit`, `history`, and `spawn_agent` gives the child `bash`, `edit`, and `history`, plus intrinsic `tau_docs`. There is no separate child tool allowlist.
 
-An explicit `tools` list replaces inheritance. It may select any of the six eligible subagent tools, even if that name is absent from the main persona's own list. Use `tools: []` for a worker with no persona-configurable tools; it still receives `tau_docs`. Names are normalized to lowercase, duplicate entries are removed, and an unknown name rejects the containing persona.
-
-The main persona must itself expose the subagent supervision tools for the model to operate subagents. Defining a subagent while omitting `spawn_agent` from an explicit persona `tools` list leaves the definition present but not launchable by the main agent. See [tools](tools.md) for the broader availability contract.
+Subagents cannot launch other subagents: supervision tools are never included in a child's registry. See [tools](tools.md) for the broader availability contract.
 
 ## Models and settings
 
@@ -110,18 +46,18 @@ A launch override must use exact form:
 
 The provider is normalized to lowercase. The model ID remains exact and case-sensitive. Effort is one of `none`, `minimal`, `low`, `medium`, `high`, `xhigh`, or `max`.
 
-`launchModels` is an allowlist, not a default selection. The main agent should normally omit the `model` argument to `spawn_agent`; when omitted, the subagent inherits the active persona model and reasoning. When supplied, the normalized value must exactly match an entry in the selected subagent's allowlist. The override changes provider, model, and reasoning. Other inherited settings remain.
+The configured launch-model list is an allowlist, not a default selection. The main agent should normally omit the `model` argument to `spawn_agent`; when omitted, the subagent inherits the active persona model and reasoning. When supplied, the normalized value must exactly match an entry in the configured allowlist. The override changes provider, model, and reasoning. Other inherited settings remain.
 
-Model IDs may be unbundled when their provider is known, following the synthesis rules in [models](models.md). Invalid provider, model, effort, or format rejects the persona during content loading. Duplicate normalized entries are removed.
+Model IDs may be unbundled when their provider is known, following the synthesis rules in [models](models.md). Invalid provider, model, effort, or format rejects the configuration field. Duplicate normalized entries are removed.
 
-### Allowing overrides for `default`
+### Allowing model overrides
 
-The built-in `default` definition cannot be edited in persona frontmatter. Configure its launch allowlist through `subagents.defaultLaunchModels` in `config.json`:
+Configure the built-in worker’s launch allowlist through `subagents.launchModels` in `config.json`:
 
 ```json
 {
   "subagents": {
-    "defaultLaunchModels": [
+    "launchModels": [
       "anthropic/claude-haiku-4-5:low",
       "openai/gpt-6.1-sol:high"
     ]
@@ -129,7 +65,7 @@ The built-in `default` definition cannot be edited in persona frontmatter. Confi
 }
 ```
 
-This list is layered configuration. The nearest defined `defaultLaunchModels` array replaces the broader array rather than appending to it. Tau applies the effective list to every persona that currently enables `default`; it does not add `default` to a persona that disabled it.
+This list is layered configuration. The nearest defined `launchModels` array replaces the broader array rather than appending to it. Tau applies the effective list to every persona that exposes `spawn_agent`.
 
 ## Working-directory context
 
@@ -137,7 +73,7 @@ This list is layered configuration. The nearest defined `defaultLaunchModels` ar
 
 When the resolved path differs from the parent `cwd`, Tau rebuilds prompt context from that target directory. It discovers the target platform and repository metadata, reads applicable `AGENTS.md` and configured context files, discovers target skills, and filters those skills through the parent persona's skill selection.
 
-The target directory does **not** select a different persona, subagent definition, model catalog, runtime configuration, credential source, or tool policy for the child. Those remain under parent-session authority. Target configuration is consulted only where needed to rebuild target prompt context, such as target `agentContextFiles` and skill discovery.
+The target directory does **not** select a different persona, model catalog, runtime configuration, credential source, or tool policy for the child. Those remain under parent-session authority. Target configuration is consulted only where needed to rebuild target prompt context, such as target `agentContextFiles` and skill discovery.
 
 This distinction matters in monorepos and hosted environments. `workingDirectory` is an execution-environment path. The host and attached client must not reinterpret it against their own filesystems.
 
@@ -145,11 +81,11 @@ A launch is blocked if Tau cannot build target context, the directory is invalid
 
 ## Lifecycle and supervision tools
 
-Subagent threads are addressed by host-generated IDs. Names identify configurations; IDs identify live thread records.
+Subagent threads are addressed by host-generated IDs. IDs identify individual live thread records.
 
 ### Spawn
 
-`spawn_agent` validates the configured name, optional launch model, title, prompt, and working directory. The prompt is the child's only initial user input, so it should be self-contained. A successful call returns immediately with the new ID while the child continues in the background.
+`spawn_agent` accepts a title, prompt, optional launch model, and optional working directory. The prompt is the child's only initial user input, so it should be self-contained. A successful call returns immediately with the new ID while the child continues in the background.
 
 At most eight subagent runs may be active concurrently within one main session. Completed or interrupted idle threads do not consume active capacity.
 
@@ -165,7 +101,7 @@ The host also publishes bounded live subagent activity to observing clients. Tha
 
 `send_input_to_agent` starts another run on an existing idle thread. The thread retains its conversation state, model, settings, tools, and working directory. It must finish or be interrupted before another input is accepted.
 
-Starting a follow-up replaces the previously retained response in the thread's latest-run state. Read any needed result before sending the next input. Follow-ups do not reread a changed persona definition or adopt a newly reloaded launch model.
+Starting a follow-up replaces the previously retained response in the thread's latest-run state. Read any needed result before sending the next input. Follow-ups do not reread a changed persona definition or adopt a newly reloaded launch allowlist.
 
 ### Interrupt
 
@@ -185,19 +121,10 @@ Plan durable work accordingly. Important conclusions should be returned to the m
 
 ## Reloading and validation
 
-Persona and global launch-policy changes take effect after `/reload` in an idle TUI session or in a newly created session. Reload updates which subagent definitions new `spawn_agent` calls see. It does not kill, rename, or reconfigure already spawned threads, and follow-ups continue on their captured runtime.
-
-An invalid subagent definition rejects its containing persona. Common content warnings include:
+Persona tool selections and launch-policy changes take effect after `/reload` in an idle TUI session or in a newly created session. Reload updates new launches without reconfiguring already spawned threads. Follow-ups continue on their captured runtime.
 
-- a name outside the lowercase-dash contract or longer than 64 characters;
-- `subagents` that is not an object;
-- `default` set to anything other than `false`;
-- a custom entry set to `false` or missing `systemPrompt`;
-- blank descriptions, prompts, or list entries;
-- unknown subagent tools;
-- `launchModels` or `defaultLaunchModels` that is not a string array; and
-- an unknown provider or model, invalid effort, or malformed `<provider>/<model>:<effort>` value.
+`subagents.launchModels` must be a string array of valid `<provider>/<model>:<effort>` values. Unknown providers, invalid efforts, and malformed entries produce configuration diagnostics.
 
-At execution time, launches can still be blocked by an unenabled name, a model outside the allowlist, exhausted concurrency, invalid arguments, missing prompt composition, or target-context failure. Follow-up, wait, and interrupt calls reject unknown IDs; follow-up also rejects a thread that is still running.
+At execution time, launches can be blocked by invalid arguments, a model outside the allowlist, exhausted concurrency, missing prompt composition, or target-context failure. Follow-up, wait, and interrupt calls reject unknown IDs; follow-up also rejects a thread that is still running.
 
-Use `tau --debug --persona <id>` before starting a local TUI to inspect effective subagent names, inherited model and settings, and tool lists. It does not reveal managed prompt bodies for built-in subagents. In a running session, `/reload` reports exact file warnings and `list_agents` verifies live runtime choices.
+Use `tau --debug --persona <id>` before starting a local TUI to inspect effective tool availability, inherited model and settings, and the child tool list. In a running session, `/reload` reports file warnings and `list_agents` shows live thread state.

package/dist/core/static/tau_docs/telegram.md

@@ -56,7 +56,6 @@ Unknown object fields are stripped, so a misspelled field can have no effect wit
 | `projects` | Yes | Object keyed by project ID. Bots select from these definitions. |
 | `workspaceRoot` | No | Base for managed workspaces; defaults to `.tau/telegram-workspaces` beside the Telegram config file. |
 | `maxSessions` | No | Positive integer cap on active sessions across the whole runner. |
-| `systemMessage` | No | Non-empty model-facing instruction prepended to every Telegram turn. |
 
 A relative top-level `workspaceRoot` resolves from the Telegram config file's directory. Tau persists runner session records at `<workspaceRoot>-sessions.json` and per-chat preferences at `<workspaceRoot>-project-preferences.json`. These are runner-owned state files, not operator editing surfaces. Session snapshots remain in the normal host store under the runner user's Tau home.
 
@@ -74,8 +73,8 @@ Each `bots.<id>` object supports:
 | `allowedChatIds` | No | Integer chat IDs allowed to interact with the bot; also opts groups in. |
 | `defaultProjectId` | No | Initial project preference, and must be allowed for this bot. |
 | `systemMessage` | No | Additional instruction for turns from this bot. |
-| `pollIntervalMs` | No | Positive polling retry interval, default 1,000 ms. |
-| `requestTimeoutSeconds` | No | Positive Telegram long-poll timeout, default 30 seconds. |
+
+The runner retries failed polling after 1,000 ms and uses a 30-second Telegram long-poll timeout.
 
 An absent or empty `allowedUserIds` means no user restriction. An absent or empty `allowedChatIds` allows DMs but allows no groups. When `allowedChatIds` is non-empty, it restricts DMs to listed chat IDs and enables only listed groups. Group IDs are usually negative integers.
 
@@ -95,7 +94,7 @@ platform_api
 release2026
 ```
 
-Every project can have an optional non-empty `description`. Repository and persistent-directory projects can select `persona` as `<id>` or `<id>:<reasoning>`, and can set `noAgentContextFiles` to disable `AGENTS.md` injection for that session. Composite projects require their own persona and do not support `noAgentContextFiles`.
+Every project can have an optional non-empty `description`. Repository and persistent-directory projects can select `persona` as `<id>` or `<id>:<reasoning>`. Composite projects require their own persona. Sessions load applicable `AGENTS.md` instructions.
 
 Each project must define exactly one workspace source: `repo`, `directory`, or `projectIds`.
 
@@ -110,9 +109,7 @@ A repository project clones one GitHub repository into a session-specific manage
       "repo": "acme/ledger",
       "ref": "main",
       "workingDirectory": "packages/api",
-      "workspaceRoot": "/var/lib/tau/ledger-workspaces",
-      "persona": "gpt-6.1-sol-coder",
-      "noAgentContextFiles": false
+      "persona": "gpt-6.1-sol-coder"
     }
   }
 }
@@ -120,7 +117,7 @@ A repository project clones one GitHub repository into a session-specific manage
 
 `repo` must use GitHub `owner/repo` syntax. Arbitrary Git URLs are not accepted. The runner needs `gh` and `git` on its login-shell `PATH`, and `gh` must already be authenticated for the repository.
 
-A relative project `workspaceRoot` resolves from the Telegram config file's directory and replaces the top-level root for that project's managed workspaces. A session workspace is:
+All managed projects use the top-level `workspaceRoot`. A session workspace is:
 
 ```text
 <effective-workspace-root>/<project-id>/<telegram-session-id>
@@ -179,7 +176,7 @@ A composite project creates a root containing multiple repositories:
       "persona": "gpt-6.1-sol-coder:high",
       "instructions": "Keep shared contracts synchronized.",
       "subagents": {
-        "defaultLaunchModels": ["openai/gpt-6.1-sol:high"]
+        "launchModels": ["openai/gpt-6.1-sol:high"]
       }
     }
   }
@@ -190,11 +187,11 @@ A composite project creates a root containing multiple repositories:
 
 Members live at `<composite-root>/<member-project-id>` and use each repository's cache, ref, and working directory. The root is the session `cwd`. At creation, Tau writes a root `AGENTS.md` listing the members and optional `instructions`, plus root `.tau/config.json` containing `subagents` or `{}`. These are workspace files, not synchronized mirrors of Telegram configuration, and are not regenerated when a preserved session reconnects.
 
-`subagents.defaultLaunchModels` sets the built-in `default` launch override allowlist. Runtime config resolves and enforces entries. See [subagents](subagents.md) for model syntax and custom policy.
+`subagents.launchModels` sets the subagent launch override allowlist. Runtime config resolves and enforces entries. See [subagents](subagents.md) for model syntax and inheritance.
 
 The composite owns the parent persona, subagents, model catalog, config, settings, and tools. Child `.tau/config.json` files are not merged. A subagent in a member directory rebuilds only target context: environment and repository metadata, applicable `AGENTS.md` and `agentContextFiles`, and skills filtered by the parent persona.
 
-Composite preparation is all-or-nothing. If one member cannot be prepared, Tau removes the generated composite workspace. The composite's optional `workspaceRoot` controls the generated root; member repository caches continue to use each member's configured root or the top-level default.
+Composite preparation is all-or-nothing. If one member cannot be prepared, Tau removes the generated composite workspace. Composite workspaces and member repository caches use the top-level `workspaceRoot`.
 
 ## Managed workspace lifecycle
 
@@ -218,13 +215,13 @@ New and reconstructed workspaces run their hooks; preserved workspaces and persi
 
 After preparation, Tau creates an ordinary local session at the workspace `cwd`. Runtime discovery reads normal `~/.config/tau` and ancestor `.tau` content visible from that path: models, personas, prompts, skills, project context, host tools, and other session settings work as they do in the TUI.
 
-A project `persona` overrides the normal default for that session. `noAgentContextFiles: true` suppresses `AGENTS.md` injection for repository or persistent-directory sessions. Composite root context is generated deliberately and uses its required persona.
+A project `persona` overrides the normal default for that session. Sessions include applicable `AGENTS.md` instructions. Composite root context is generated deliberately and uses its required persona.
 
 Every Telegram turn starts with hidden `<system>` guidance identifying Telegram as the source and reply destination. It favors direct simple answers and brief acknowledgements or meaningful progress updates for tool-driven or multi-step work, since users cannot see tool activity.
 
-Top-level and per-bot `systemMessage` values share a second hidden block after the default, in that order. Audio transcripts receive another warning that they may contain noise or errors. Unlike project context, hidden guidance is persisted with user turns and can appear in history, so never put credentials in configured messages.
+A per-bot `systemMessage` appears in a second hidden block after the default. Audio transcripts receive another warning that they may contain noise or errors. Unlike project context, hidden guidance is persisted with user turns and can appear in history, so never put credentials in configured messages.
 
-The runner's speech-to-text provider is loaded from normal Tau config at runner startup, based on the runner process's startup `cwd`. Restart the runner after changing that provider or its environment.
+The runner's speech credentials and `speech.voiceId` are loaded at startup from its environment and normal Tau config, based on the runner process's startup `cwd`. Restart the runner after changing those settings.
 
 ## Chat commands
 
@@ -280,14 +277,9 @@ Uploads only queue files; captions are metadata. The next text or voice transcri
 
 Files use native temporary directories in the execution environment; OS cleanup can invalidate their paths. Pending queues and group context clear on shutdown. File contents and metadata are untrusted.
 
-OpenAI is the default. Select Gemini with `speechToText.provider`. Runner credentials are:
-
-- Gemini: `GEMINI_API_KEY`, then `apiKeys.google`
-- OpenAI: `OPENAI_API_KEY`, then `apiKeys.openai`
-
-Gemini extracts spelling hints with Gemini 3.8 Flash and transcribes uploaded audio verbatim with `gemini-3.5-transcribe`, using English (`en-US`) and Finnish (`fi-FI`) hints. It attempts remote file deletion afterward. OpenAI normalizes downloaded audio with runner-side `ffmpeg` and uploads it to `gpt-transcribe`. Missing keys prevent transcription, not file delivery. See [credentials](credentials.md).
+Voice transcription uses Gemini with `GEMINI_API_KEY`, then `apiKeys.google`. Optional hints use GPT-6 Luna (reasoning disabled) and OpenAI credentials. Gemini transcribes audio verbatim with `gemini-3.5-transcribe`, using English (`en-US`) and Finnish (`fi-FI`) hints. It attempts remote file deletion. File delivery needs no Google key. See [credentials](credentials.md).
 
-`/tts_on` uses `gemini-3.8-flash`, `gemini-3.1-flash-tts-preview`, Despina, the Google key, and runner `ffmpeg` with Opus. Source and rewritten text each allow 10,000 Unicode characters; audio allows 32 MiB. Rewrite and job timeouts are one and five minutes. Jobs are ephemeral. Failure sends `voice response failed. please try again.` without affecting text; details stay in logs.
+`/tts_on` rewrites text with `gpt-6-luna` (reasoning disabled) and generates speech with Eleven v4 Turbo. It requires both OpenAI and ElevenLabs credentials and runner `ffmpeg` with Opus. Voice notes use brisk delivery and 1.15× speed. See [`speech` configuration](config-reference.md#speech) for default and custom voice selection. Source and rewritten text each allow 10,000 Unicode characters; audio allows 32 MiB. Rewrite and job timeouts are one and five minutes. Jobs are ephemeral. Failure sends `voice response failed. please try again.` without affecting text; details stay in logs.
 
 ## Command client tools
 
@@ -338,7 +330,7 @@ Do not verify bot tokens, provider keys, Access secrets, transcript contents, or
 
 **A persistent-directory session fails recovery.** Restore the configured directory and its original path, or return the project config to the snapshot's durable `cwd`. Tau does not migrate an existing session to a new persistent directory.
 
-**Audio reports a missing key.** Set the credential for the configured speech provider in the runner process and restart it. A workspace-only environment change does not update the runner's startup speech configuration.
+**Audio reports a missing key.** Set the credential for the Gemini in the runner process and restart it. A workspace-only environment change does not update the runner's startup speech configuration.
 
 **A message sent during active work changes direction.** Telegram uses steering, not ordinary queueing, while a turn is running. Wait for completion before sending an independent next task, or use `/interrupt` to stop the current run first.
 

package/dist/core/static/tau_docs/tools.md

@@ -47,7 +47,7 @@ list_agents
 interrupt_agent
 ```
 
-When a custom persona extends another persona and omits `tools`, it inherits the base persona's list. A non-extending custom persona that omits `tools` enables `bash`, `write`, `edit`, `view_image`, `web`, `nook`, and `history`. If that persona has any enabled subagents, Tau also enables the five subagent-management tools. Built-in personas enable the same base and subagent tool sets.
+When a custom persona extends another persona and omits `tools`, it inherits the base persona's list. A non-extending custom persona that omits `tools` enables `bash`, `write`, `edit`, `view_image`, `web`, `nook`, and `history`. It also enables the five subagent-management tools. Built-in personas enable the same base and subagent tool sets.
 
 An empty list disables every persona-controlled host tool:
 
@@ -131,7 +131,7 @@ Neither tool provides a general read operation. Use a scoped non-interactive Bas
 
 `view_image` reads an image from the execution environment and returns it to a multimodal model. Tau's built-in instruction limits use to cases where the user explicitly asks to view or analyze an image.
 
-The supported formats are JPEG, PNG, and WebP. Source reads are capped at 50 MiB. Images larger than 2,000 pixels in either dimension or 2.5 MiB of model payload are resized or re-encoded while preserving aspect ratio. If Tau cannot reduce a valid image below the model payload limit, the call fails. Relative paths resolve from the execution-environment working directory.
+The supported formats are JPEG, PNG, and WebP. Source reads are capped at 50 MiB. Images with both dimensions at most 4,096 pixels and a model payload at most 3.5 MiB are returned unchanged. Images exceeding the dimension limit are resized to fit within 4,096 pixels while preserving aspect ratio, without upscaling. Tau tries lossless encoding before lossy compression and reduces dimensions further only if needed to meet the payload limit. Transparency is preserved. If Tau cannot reduce a valid image below the model payload limit, the call fails. Relative paths resolve from the execution-environment working directory.
 
 ## Command-line tools
 
@@ -175,7 +175,7 @@ The effective history query may be machine-local or backed by a configured remot
 
 ### Nook
 
-`nook` manages the configured Nook static mini-app platform. It is available only to a main-session persona that lists `nook` and only when Nook is configured. Subagents cannot receive it.
+`nook` manages the configured Nook static mini-app platform. It is available when the main persona lists `nook` and Nook is configured. Subagents inherit it under the same conditions.
 
 The tool is intended for explicit requests to inspect or manage Nook, publish a static artifact or mini-app, or work with Nook KV. Once the built-in documentation is visible, app-authoring work requires a second separate documentation-only call that prints the Nook authoring skill. The agent reads that guide before creating or modifying app files. Nook setup and platform behavior are covered in [Nook](nook.md).
 
@@ -184,12 +184,12 @@ The tool is intended for explicit requests to inspect or manage Nook, publish a
 A subagent can receive only:
 
 ```text
-bash  write  edit  view_image  web  history
+bash  write  edit  view_image  web  history  nook
 ```
 
-A subagent definition may list an exact subset. If it omits `tools`, Tau inherits the intersection of the main persona's tools and those six eligible names. Duplicate names are normalized. `tau_docs` is then added intrinsically regardless of the subset.
+Tau inherits the intersection of the main persona’s tools and those seven eligible names. `tau_docs` is then added intrinsically. There is no separate child tool selection. Nook is bound only when configured, just as for the parent.
 
-Subagents do not receive Nook, goal tools, subagent-management tools, or client-provided tools. Their Bash and file tools are scoped to the subagent working directory, including an alternate directory selected at launch. See [subagents](subagents.md) for configuration and working-directory context rebuilding.
+Subagents do not receive goal tools, subagent-management tools, or client-provided tools. Their Bash and file tools are scoped to the subagent working directory, including an alternate directory selected at launch. See [subagents](subagents.md) for configuration and working-directory context rebuilding.
 
 ## Client-owned tools