@markusylisiurunen/tau 0.3.77 → 0.3.78

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

@@ -64,12 +64,10 @@ Within the project, the effective default persona is `gpt-6.1-sol-coder:high`.
 A few fields intentionally use other rules:
 
 - `apiKeys` merges by provider id. A more-specific key replaces only the same provider's value.
-- `autoCompact` merges by field on top of shipped defaults.
 - `modelSystemNotices` merges by normalized `<provider>/<model>` key.
 - `flySprites.apis` merges by API id. A more-specific API replaces the complete API entry with that id.
 - `agentContextFiles` is additive across levels, resolves each entry at its owning level, and removes duplicate resolved paths while preserving order.
-- `diffTool` and `builtInDiffTool` select the complete object from the most-specific level that defines them.
-- `subagents.defaultLaunchModels` selects the most-specific list.
+- `subagents.launchModels` selects the most-specific list.
 - `clientTools` is defined only at global scope. `enabledClientTools` at the most-specific project level is an exact selection from those definitions.
 - `history` is accepted only at global scope.
 
@@ -89,22 +87,18 @@ Relative path bases belong to the level that declares the value:
 
 - Global `agentContextFiles` entries resolve from home.
 - Project `agentContextFiles` entries resolve from the directory containing `.tau`.
-- A relative `diffTool.command` containing a slash resolves from the same level root.
 - A global `clientTools[].command` containing a slash resolves from home.
-- A bare command such as `review-ui` is left bare and resolves through the owning process's `PATH`.
+- A bare command such as `git` is left bare and resolves through the owning process's `PATH`.
 
 For example, in `/home/ada/work/ledger/.tau/config.json`:
 
 ```json
 {
-  "agentContextFiles": ["docs/AI_GUIDE.md"],
-  "diffTool": {
-    "command": "./tools/review-ui"
-  }
+  "agentContextFiles": ["docs/AI_GUIDE.md"]
 }
 ```
 
-Tau resolves the paths as `/home/ada/work/ledger/docs/AI_GUIDE.md` and `/home/ada/work/ledger/tools/review-ui`. In an attached session, `diffTool` used by the TUI comes from the client-local load, so this resolved command is a client path.
+Tau resolves the path as `/home/ada/work/ledger/docs/AI_GUIDE.md`.
 
 Other strings that happen to contain paths are not automatically rebased unless their field contract says so. In particular, hosted execution-environment `home` values are passed as configured.
 
@@ -158,7 +152,6 @@ Never verify a secret by printing the full config or environment into a shared t
 Tau loads startup configuration and content before opening the TUI. Restart the local TUI or `tau attach` to apply client-owned changes such as:
 
 - `defaultTheme`
-- `diffTool` and `builtInDiffTool`
 - `clientTools` and `enabledClientTools`
 - client environment variables
 

package/dist/core/static/tau_docs/ownership-and-scope.md

@@ -57,7 +57,7 @@ A Fly Sprite can place the execution environment on another target while the hos
 | Session snapshots | Host home | Local defaults live under the host's Tau config directory. Do not edit session files. |
 | Local transcript history and remote history outbox | Host home | History follows the host, not an attached TUI or execution target. |
 | Terminal theme and `/theme` | TUI client | An attached client selects from Tau’s built-in themes. Themes are not session state. |
-| `/diff` process | TUI client | `diffTool.command` must exist on the client machine. Repository capture still runs through the session execution environment. |
+| `/diff` process | TUI client | Tau’s built-in browser tool runs on the client machine. Repository capture still runs through the session execution environment. |
 | Configured command client tools | Owning client | Commands and their environment are client-local; their execution-environment facade reaches the session target explicitly. |
 | `/listen` and `/speak` capture or playback | TUI client | Required programs, devices, and media credentials belong on the client machine. |
 | Host execution-environment targets | Host startup | Fly Sprite API definitions must be available to the host before it accepts sessions using them. |
@@ -84,7 +84,7 @@ tau attach --new --cwd /srv/ledger ws://devbox.example:8787
 
 The path `/srv/ledger` is interpreted by the host and its local execution environment. Project personas and `.tau/config.json` are read from `/srv/ledger` and its ancestors on `devbox.example`. The laptop's current directory does not influence that session runtime.
 
-The laptop still loads its own theme, `diffTool`, and command client tools before attaching. If `/diff` launches `review-ui`, that executable must exist on the laptop. Git snapshot commands for the review run through the session and therefore see `/srv/ledger` on the execution environment.
+The laptop still loads its own theme and command client tools before attaching. `/diff` launches Tau’s built-in browser tool on the laptop. Git snapshot commands for the review run through the session and therefore see `/srv/ledger` on the execution environment.
 
 If the selected persona needs a provider credential, the host on `devbox.example` makes the model call. Export the provider environment variable for `tau serve` there, or make the appropriate runtime configuration available to that host. Setting it only in the laptop shell does not authenticate the remote host.
 

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

@@ -1,12 +1,12 @@
 # Personas
 
-A persona is Tau's complete model-facing working profile. It chooses a provider and model, supplies the base system prompt, sets reasoning and service behavior, and selects tools, skills, and subagents. Changing persona changes how future turns run without creating a new session.
+A persona is Tau's complete model-facing working profile. It chooses a provider and model, supplies the base system prompt, sets reasoning and service behavior, and selects tools and skills. Changing persona changes how future turns run without creating a new session.
 
 Tau ships generated built-in personas and discovers custom persona Markdown from the execution environment. The effective list is version-specific and scope-specific, so inspect the current catalog rather than relying on a memorized list of names.
 
 ## Built-in and effective personas
 
-Built-in personas are generated from Tau's current model catalog. Most model families have separate chat and coder variants; some families expose only the variants Tau supports. Built-ins carry Tau-maintained prompts, defaults, tool selections, skills, and the built-in `default` subagent.
+Built-in personas are generated from Tau's current model catalog. Most model families have separate chat and coder variants; some families expose only the variants Tau supports. Built-ins carry Tau-maintained prompts, defaults, tool selections, skills, and subagent supervision tools.
 
 The Opus 5.5 chat and coder personas are available only when `anthropic/claude-opus-5-5` is present in the effective model catalog. The Sonnet 5.5 variants (`sonnet-5.5-chat` and `sonnet-5.5-coder`) likewise require `anthropic/claude-sonnet-5-5`.
 
@@ -16,7 +16,7 @@ All built-in personas default to medium reasoning. The startup default is `sonne
 
 After a remote catalog refresh, `/reload` adopts the updated catalog for an existing session.
 
-Set `disableBuiltinPersonas: true` in `config.json` to omit built-ins from the effective catalog. Custom personas can also replace a built-in by using the same ID. A shipped built-in is therefore not necessarily available in a particular session.
+Built-in personas are always included in the catalog. Custom personas can replace a built-in by using the same ID.
 
 Use one of these to inspect the current effective list:
 
@@ -67,14 +67,6 @@ tools:
   - view_image
   - web
   - history
-subagents:
-  default: false
-  verifier:
-    description: Verify release state independently. Trigger: balanced.
-    systemPrompt: Verify the requested release state and report concrete blockers.
-    tools:
-      - bash
-      - history
 ---
 
 Work as a release engineer. Inspect repository policy before changing release state.
@@ -104,9 +96,8 @@ The frontmatter must be a YAML object between valid delimiters. Unknown fields a
 | `allowedReasoningLevels` | Array of reasoning efforts offered by the TUI selector. |
 | `skills` | `"*"`, a list of discovered skill names, or `[]`. |
 | `tools` | Explicit list of persona-controlled tools. |
-| `subagents` | Map of enabled subagent definitions. |
 
-If a standalone custom persona omits `skills`, Tau selects all discovered skills with `"*"`. If it omits `subagents`, Tau enables the built-in `default` subagent. Tool defaults then include the ordinary host tools plus subagent supervision tools. See [skills](skills.md) and [subagents](subagents.md) for those contracts.
+If a standalone custom persona omits `skills`, Tau selects all discovered skills with `"*"`. If it omits `tools`, Tau enables the ordinary host tools plus subagent supervision tools. An explicit `tools` list without `spawn_agent` prevents subagent launches. See [skills](skills.md) and [subagents](subagents.md) for those contracts.
 
 The persona-controlled tool names are:
 
@@ -135,10 +126,8 @@ Important boundaries are:
 
 - `extends` resolves shipped built-ins, not another custom persona.
 - Lookup of the built-in ID is case-insensitive.
-- It remains available as an inheritance base even when `disableBuiltinPersonas` hides built-ins from the effective catalog.
 - A non-empty Markdown body replaces the inherited base prompt.
 - Explicit `skills` or `tools` replaces the inherited selection.
-- Explicit `subagents` builds a new subagent map rather than merging custom entries into the inherited map. Unless that map contains `default: false`, Tau adds the built-in `default` subagent.
 - `reasoning` and `serviceTier` override their individual inherited settings; omitted settings remain inherited.
 
 Extending a built-in is useful when Tau's maintained behavior is the desired base. A standalone body is more stable when the persona must not change as Tau updates its built-in prompts.
@@ -187,7 +176,7 @@ Run `/reload` while the TUI session is idle after editing personas, `models.json
 
 If the current persona ID still exists, Tau applies its newly loaded definition. This can reset runtime settings such as reasoning or service tier to the definition's values. If the ID disappeared, Tau selects the first effective persona. Existing session messages remain; changing a persona does not rewrite prior model-facing history.
 
-A reload does not alter a turn already in progress, and the TUI refuses the operation while one is running. Existing live subagent threads retain the runtime with which they were created; newly spawned subagents use the reloaded persona definition. See [subagents](subagents.md).
+A reload does not alter a turn already in progress, and the TUI refuses the operation while one is running. Existing live subagent threads retain the runtime with which they were created; newly spawned subagents inherit the reloaded persona. See [subagents](subagents.md).
 
 ## Validation and common mistakes
 
@@ -200,8 +189,6 @@ An invalid persona is skipped and reported as a configuration warning. Other val
 - an `extends` target that is not a shipped built-in;
 - an invalid reasoning effort or service tier;
 - `skills` that is neither `"*"` nor a string list, or contains a blank entry;
-- an unknown persona tool;
-- an invalid subagent name, missing custom `systemPrompt`, unsupported subagent tool, or invalid launch model; and
-- attempting to override the built-in `default` subagent instead of using `default: false`.
+- an unknown persona tool.
 
 `/reload` surfaces warning paths directly in the transcript. For a new local TUI session, `tau --debug --persona <id>` shows the selected model, settings, skills, subagents, tools, and complete effective prompt. If a remote edit appears to have no effect, confirm the session execution environment and `cwd` before changing another copy of the file. [Troubleshooting](troubleshooting.md) covers that check in more detail.

package/dist/core/static/tau_docs/prompts-and-project-context.md

@@ -149,7 +149,7 @@ The alternate directory controls:
 - target applicable `AGENTS.md` and `agentContextFiles`,
 - target-discovered skills filtered by the parent persona.
 
-The parent session remains the source of truth for the selected persona, subagent definition, model catalog, model settings, and tool policy. Tau filters skills discovered at the alternate directory through the parent persona's skill selection. It does not replace the source persona with a persona found in the target directory. See [subagents](subagents.md) for the full launch contract.
+The parent session remains the source of truth for the selected persona, model catalog, model settings, and tool policy. Tau filters skills discovered at the alternate directory through the parent persona's skill selection. It does not replace the source persona with a persona found in the target directory. See [subagents](subagents.md) for the full launch contract.
 
 ## Leading hidden system blocks
 

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

@@ -150,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’s theme selection 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
 
@@ -161,7 +161,7 @@ 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`. |
+| 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. |

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

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,11 +215,11 @@ 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 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.
 

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