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

# Release notes

> What changed in each Stampede release from v0.5.3 back to v0.3.0, and what to do when upgrading.

Each entry lists what changed for someone running Stampede and what the upgrade needs. The general procedure (verify, stop, back up, install, `service install`, `doctor`) is on [Upgrading](https://stampede.autonomousorganizations.ai/production/upgrading.md); a release that moves the store schema makes the backup mandatory, because the older binary refuses the migrated store.

## v0.5.3

Released 2026-11-14.

* A webhook route may no longer name a person whose policy is unrestricted (free, operator) or may run any program (maintainer). The webhook worker disables such a route at start and logs `webhook: route R disabled: person P has an unrestricted policy` (or `may run any program`); a disabled route answers 401 like an unknown one.
* The worker checks the route's person again before each run, and the run itself checks before any tool or MCP server starts. A person changed to a forbidden policy while the worker runs is not run; the delivery settles `failed`.
* `stampede doctor` shows a `FAIL` row for each refused route, and a `WARN` row for a served route whose person may start programs (reviewer, builder), naming what that person can reach.
* The webhook documentation now states correctly what a webhook run can read and write.

Upgrade: no schema step (stays 26) and no new configuration. Behaviour change: a route that names a free, operator or maintainer person stops being served. Before upgrading, check `stampede doctor` and `stampede webhook routes`, and give each such route a person made with `stampede person create NAME --policy research`. A delivery that a 0.5.2 worker queued for such a route settles `failed` and is never run. Rolling back is reinstalling the 0.5.2 binary and running `stampede service install`.

## v0.5.2

Released 2026-11-14.

* Signed webhooks. A new `webhook` worker listens on `127.0.0.1:8787` (configurable) and starts a run of a named person for each verified GitHub, GitLab, Linear or generic signed delivery.
* Verification per sender: GitHub `X-Hub-Signature-256`, GitLab `X-Gitlab-Token`, Linear `Linear-Signature` with a 60-second timestamp window, generic `X-Signature-256`. Replayed deliveries are dropped by delivery id and by body digest.
* Only the payload fields a route names reach the model, quoted as untrusted data after the route's template.
* Results go to the run record (`stampede webhook show RUN_ID`) or to a comment on the issue, pull request or merge request, posted by the worker with `gh` or `glab` and a token from the vault. Comments pass the outbound filter first.
* New commands: `stampede webhook list`, `webhook show RUN_ID`, `webhook routes`. New `doctor` rows for the worker, the bind address and each route.

Upgrade: store schema 25 to 26, one way; back up `~/.stampede` first. The `[webhook]` table is new and a 0.5.1 binary refuses a file that holds it, so add it after installing. Nothing starts until a route exists. Secrets and tokens go in the vault with `/add-secret`, never in `config.toml`. To roll back, run `stampede service uninstall webhook` with 0.5.2 still installed, then restore the backup.

## v0.5.1

Released 2026-11-13.

* `stampede skills install SOURCE` installs a skill from a Markdown file, an Agent Skills folder or a git URL. It shows the skill, runs a short smoke test with your model, and activates it on your confirmation. Only the Markdown is kept; nothing from the source runs.
* A skill can be user-only (invocation `user`): the model never sees or picks it, and only `/skill NAME` starts it. Agent Skills `disable-model-invocation: true` maps to this.
* `/skill NAME [text]` in the console loads one skill for the next turn. A scheduled task whose first line is `/skill NAME` does the same.
* `[persons.NAME] auto_load = [...]` pins up to two skills (16,384 bytes) into every model request of that person's runs. `doctor` warns about pins that do not load or that cost more than half of `turn_input_tokens`.

Upgrade: store schema 24 to 25, one way; back up first. `auto_load` is new and a 0.5.0 binary refuses it, so add it after installing and remove it before going back. `skills install` needs a working model profile. Skills installed earlier keep working and read as invocation `any`.

## v0.5.0

Released 2026-11-13.

* Task rooms. A person asked for work that needs two or more other persons opens a room with `room_open`, the members work from their mailboxes and post with `room_post`, and the requester gets one summary.
* A room grants no tool, path or program. Each member acts under its own policy narrowed by the opener's grant.
* `stampede room list` and `stampede room show ROOM_ID` print rooms, members and posts.
* New `[rooms]` section: `wake_limit` (64), `member_wake_limit` (16), `wake_wait_secs` (300).
* `run_command`'s default time limit is 60 seconds (was 30); the maximum stays 1,800.
* A person whose mail cannot start no longer blocks every later person's mailbox.
* Security: a dependency update fixes a UDP receive loop that could spin on macOS when sent an oversized datagram.

Upgrade: store schema 23 to 24, one way; back up first. `[rooms]` is new and a 0.4.9 binary refuses it. A run recorded by 0.4.9 is not resumed automatically. A run that relied on a command stopping at 30 seconds now waits up to 60 unless it sets `timeout_secs`.

## v0.4.9

Released 2026-11-13.

* Project instruction files. A run loads `AGENTS.md`, `CLAUDE.md` and `STAMPEDE.md` from the repository root down to its own directory, after `~/.stampede/instructions.md`, and shows them to the model as project instructions ranked below the operator's instructions and the person's policy. A file grants nothing.
* The console, the TUI and `stampede agent` load from the directory they start in; a gateway request from the gateway's `workdir`; a schedule fire or remote request from the run's workspace.
* Limits: 32,768 bytes per file, 65,536 in all; symlinks, devices and non-UTF-8 files are not read.
* Switches: `[tools] project_instructions = false` for the home, `[persons.NAME] project_instructions = false` for one person.

Upgrade: no schema step (stays 23). From the first run, the text of those files in a run's directory is sent to the model provider. To turn this off, stop the workers, install, add `project_instructions = false`, then `stampede service install`. Both keys are new and a 0.4.8 binary refuses them.

## v0.4.8

Released 2026-11-12.

* A command that reaches its time limit is stopped and returns a timed-out result to the model; the run continues instead of ending as interrupted.
* A person that handed work to another person and then answers in text now sends that answer to its requester. Gateway members no longer see "Finished without a reply." in that case.
* A sub-agent that declares only `read_paths` resolves relative paths where its parent does.
* A reply to a question the worker never recorded gets "This question has expired."
* After a restart, a gateway request whose work reached another person closes promptly instead of waiting out its age limit.
* Dependency updates clear two security advisories (bundled SQLite and root certificates).

Upgrade: no schema or configuration change. Rolling back is reinstalling the 0.4.7 binary.

## v0.4.7

Released 2026-11-12.

* A gateway request carries the chat's earlier requests and answers: the last six answered requests to the same person in the same chat within 24 hours, marked as untrusted context. A reply to an earlier answer carries that pair at any age.
* `/new` and `/new @person` in Telegram start a new conversation.
* Replies show their formatting in Telegram (bold, italic, code, links, lists).
* `run_command` and `start_command` accept quoted arguments (`git commit -m "Add keyword"`) and an optional `cwd`. Unquoted shell operators (`|`, `&&`, `;`, redirects) are refused; there is still no shell.
* New `[tools] turn_input_tokens` (default 500,000, range 100,000 to 5,000,000). A repository task wants about `turn_model_calls = 60` and `turn_input_tokens = 2000000`.

Upgrade: store schema 22 to 23, one way; back up first. `turn_input_tokens` is refused by 0.4.6. The first gateway request after the upgrade starts with no earlier pairs.

## v0.4.6

Released 2026-11-11.

* A free person runs any program on every home, including `full_access = false` homes. On such a home its chat-started runs can no longer save a model profile or MCP server.
* A person's sub-agent has its person's rights: the same programs, MCP tools and file roots. A builder's sub-agent can run a build such as `npm run build`. A person's sub-agents run one at a time.
* Interpreted programs such as `npm`, `npx` and Python tools run correctly again.
* `run_command` takes an optional `timeout_secs`, up to 1,800 seconds.
* A worker restart during a sub-agent's command no longer leaves the person serving no requests.

Upgrade: no schema change (stays 22). Behaviour changes for free persons and sub-agents as above.

## v0.4.5

Released 2026-11-11.

* Every person may start sub-agents, in every kind of run. A sub-agent decides each call through its parent person's policy.
* New presets: `writer`, `reviewer`, `coordinator` and `maintainer`, beside `research` and `builder`. `builder` gains `schedule_task`.
* `stampede person create NAME` without `--policy` makes a free person (every tool, any program the home allows) and says so.
* `person list`, `person show`, `runs show` and `doctor` name each person's preset, `free`, or `custom`.
* A gateway person's sub-agent no longer stops the gateway worker.

Upgrade: no schema change (stays 22). Stored persons keep their policies; none becomes free. A script that ran `person create NAME --allow-tool X` without `--policy` is now refused and needs `--policy research`. A 0.4.4 binary refuses a maintainer person's record.

## v0.4.4

Released 2026-11-11.

* `ask_user` takes up to four questions in one call, each with a short header and numbered options, and returns the answers as JSON.
* A run with nobody to ask is not offered `ask_user`.
* Gateway: the run working on a member's request can ask that member, who answers from chat by number or in their own words. A question waits at most 30 minutes.
* Questions and answers are sealed in the store and never shown by `stampede runs show`.

Upgrade: store schema 21 to 22, one way; back up first if you may go back.

## v0.4.3

Released 2026-11-11.

* Every run ends with one stop word: `completed`, `budget_exhausted`, `wall_clock`, `no_progress`, `cancelled`, `provider_failed`, `interrupted` or `failed`. `runs show` prints it as `stop: WORD`; `stampede agent` prints `[stopped: WORD]`.
* A run stopped by its call cap, a budget or its time limit ends with a handoff summary in three parts: Done, Not done, Next.
* A gateway member gets "Stopped: WORD." and the summary in one reply.

Upgrade: no schema change. Run `stampede service install` so the units are rewritten. A capped or failed run recorded by 0.4.2 shows `stop: unknown (recorded before 0.4.3)`.

## v0.4.2

Released 2026-11-10.

* One command gate per person: a bounded person runs exactly the programs in its list in every kind of run, on every home.
* The builder preset adds `gh`, `glab`, `node`, `npm` and `npx`.
* A refused program's error names the list and the command that extends it.
* An unattended run can rerun a test or build after a change in the same run.
* `doctor` shows one `mcp LABEL` row per MCP server.
* On Linux, quiet child processes (MCP servers, background commands) are no longer killed after about ten seconds.

Upgrade: no schema change. Run `stampede service install`, not a plain restart, so the units are rewritten. A builder whose list is exactly the earlier preset gains the new programs. A run recorded by 0.4.1 is not resumed. A git host login stored for the service user is readable by every builder person and anyone whose request reaches one.

## v0.4.1

Released 2026-11-10.

* A non-member's `/start` to the bot is recorded as a pending sender (no answer is sent).
* `stampede gateway pending`, `gateway pending clear [ID]` and `gateway member add ID PERSON [--purpose TEXT]` add members without editing the file by hand.
* The running gateway reloads the member and group lists after every poll and on `stampede service reload`. Removing a member or group revokes it in the running worker.
* `doctor` counts pending senders.

Upgrade: the store moves to schema 21 on first open; a 0.4.0 binary then refuses it. Confirm a pending sender's numeric id with the person before adding it.

## v0.4.0

Released 2026-11-08.

* Telegram groups: `[[gateway.telegram.group]]` lists groups by negative `chat_id`, each optionally limited to a `persons` list.
* In a group, members address persons as in a private chat, and every answer is a reply in the group. `/status`, `/cancel` and `/who` are scoped to the chat.
* Supported setup: privacy mode off and join groups on in BotFather, then remove and re-add the bot. Everyone in a listed group reads every answer.

Upgrade: no action beyond installing. A home with no group table behaves as 0.3.0.

## v0.3.0

Released 2026-11-07.

* The Telegram gateway: members of a small group reach the persons of one home from a bot in private chats, under each person's own policy.
* `[gateway.telegram]` configures the token variable, the work directory, requests per hour and one member table per person.
* Commands in chat: `@person request`, `/who`, `/status`, `/cancel ID`.
* The outbound filter keeps the bot token, every configured model key and every env-file value of 8 bytes or more out of sent messages.
* `doctor` gains a gateway row; `service install` installs the gateway worker only when it is configured.


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