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

# Presets and permissions

> The policy presets a person can have, what each may read, write and run, and how to choose one.

A person's policy decides what it may do in an unattended run: an `@name` request, a request from another person, a schedule fire, a webhook delivery, a gateway request or work from a paired machine. Nobody approves those calls one by one. A call inside the policy runs, and a call outside it is refused and returned to the person as a tool result.

A preset is a named starting policy. You pick it with `--policy` on `stampede person create` or as the second argument of `stampede person policy`.

## Preset table

| Preset | Reads and searches | Writes files | Programs | Network | Other tools |
| - | - | - | - | - | - |
| `research` | yes | no | none | none built in | `send_message`, `todo_write`, `stampede_state`, sub-agents |
| `writer` | yes | yes | none | none built in | as `research` |
| `reviewer` | yes | no | its list (below) | through its programs, such as `git` and `npm` | as `research`, plus the command tools |
| `coordinator` | yes | no | none | none built in | as `research`, plus `schedule_task` and `ask_user` |
| `builder` | yes | yes | its list (below) | through its programs, such as `git`, `gh` and `npm` | as `research`, plus the command and job tools, `memory_propose`, `skill_propose`, `schedule_task` |
| `maintainer` | yes | yes | any program | through any program | the same tools as `builder` |
| `free` | yes | yes | any program | through any program and every configured MCP tool | every tool |

Every preset may start sub-agents. `operator` is accepted as the old name of `free` and is shown as `free`.

Stampede has no built-in web tool. A person reaches the network only through a program it may run or an MCP tool it may call. A bounded preset gets an MCP tool only when you add its exact name with `--allow-tool`.

### Tool lists

| Preset | Tools |
| - | - |
| `research` | `read_file`, `glob`, `grep`, `list_dir`, `read_artifact_range`, `memory_get`, `memory_search`, `skill_search`, `skill_load`, `send_message`, `todo_write`, `stampede_state`, `run_subagent`, `run_subagents` |
| `writer` | the `research` tools plus `write_file`, `edit`, `apply_patch` |
| `reviewer` | the `research` tools plus `run_command`, `start_command`, `command_output`, `kill_command` |
| `coordinator` | the `research` tools plus `schedule_task`, `ask_user` |
| `builder` | the `research` tools plus `write_file`, `edit`, `apply_patch`, `run_command`, `start_command`, `command_output`, `kill_command`, `inspect_lost_job`, `terminate_lost_job`, `memory_propose`, `skill_propose`, `schedule_task` |
| `maintainer` | the `builder` tools |
| `free` | every tool, under the home's normal tool policy |

A run that is offered `send_message` is also offered `room_open` and `room_post`, decided the same way. See [Mail and task rooms](https://stampede.autonomousorganizations.ai/teamwork/mail-and-task-rooms.md).

### Program lists

| Preset | Programs |
| - | - |
| `reviewer` | `cargo`, `cat`, `date`, `echo`, `git`, `go`, `head`, `make`, `node`, `npm`, `npx`, `pwd`, `pytest`, `python3`, `ruff`, `tail`, `wc` |
| `builder` | `cargo`, `cat`, `date`, `echo`, `gh`, `git`, `glab`, `head`, `node`, `npm`, `npx`, `pwd`, `tail`, `wc` |
| `maintainer` | any program |
| `free` | any program |

The other presets run no program.

## Adding to a preset

`--allow-tool NAME` adds one exact tool name (a built-in tool, or an MCP tool named `SERVER__TOOL`), and `--allow-command PROGRAM` adds one program. Both are repeatable and both need a preset:

```bash theme={null}
stampede person create docs --policy writer --allow-command make
stampede person policy notes research --allow-tool weather__forecast
```

A free person refuses any addition, and a `maintainer` refuses `--allow-command`. `person list`, `person show` and `stampede doctor` label a person whose list matches no preset as `custom`.

A bounded person runs exactly the programs in its list: the preset's programs plus its `--allow-command` grants. That one list applies in every run of the person, whatever the home's `full_access` setting says. A program outside it is refused, and the refusal names the list and the command that extends it.

## What free means

A person created without `--policy` is free. It may use every tool and run any program, in every kind of run, under the home's normal tool policy. Its file tools still follow the home's path settings: on a home with `full_access = false` they stay inside the configured `read_paths` and `write_paths`.

Two limits apply to free and `maintainer` persons:

* A `maintainer` cannot change Stampede's configuration or members through Stampede's own tools.
* On a home with `full_access = false`, a free person's run that a chat started (a gateway request, a mailbox or schedule run) is refused `save_model_profile` and `save_mcp_server` with "this home does not let a run change Stampede's configuration". Your own attended console turn keeps both, behind confirmation.

> [!WARNING]
>
> Both presets run commands with the host user's full rights. A shell or an interpreter can edit `~/.stampede`, the configuration and the member table, and read the env file that holds your keys. Give these presets only to persons you trust with everything that user can reach.

A webhook route refuses a person that is free or may run any program. See [Webhooks](https://stampede.autonomousorganizations.ai/start/webhooks.md).

## Commands and their limits

An allowlist entry is a grant of host authority. A program on the list can read or write any path the host user can reach through its arguments, and the build scripts, hooks and packages it starts run with the same rights. Granting an interpreter or a shell means granting any code. Only the file tools keep to the configured roots.

A command line is split on spaces. Single quotes, double quotes and backslashes keep spaces inside one argument (`git commit -m "two words"`). There is no shell, so pipes and redirections do not work.

A command stops after 60 seconds. A run can ask for longer with `timeout_secs` on `run_command`, from 1 up to 1800 seconds and never past the run's own time limit. A value outside that range is refused with "timeout\_secs must be from 1 to N seconds for this run". When a command reaches its limit, its process group is stopped, and the run gets a timed-out result with what the command printed and carries on. The command may have changed files before it stopped, and the result says so.

## Sub-agents

Every person may start sub-agents with `run_subagent` and `run_subagents`, and a sub-agent has its person's rights:

* the same program list (or any program for a `maintainer` or free person), run in the foreground with the same `timeout_secs` limit;
* the same MCP tools, on the same running servers;
* the same file roots. A sub-agent that names no `read_paths` or `write_paths` gets its parent's roots and workspace. A declared scope narrows the file tools and the directory commands start in, and never widens them.

A sub-agent decides each call through its parent person's policy, so it can do nothing its parent could not: a `research` person's sub-agent is refused `run_command`, as its parent is. It is not offered `start_command`, `command_output`, `kill_command`, `inspect_lost_job` or `terminate_lost_job`, because a background job would end with the sub-agent. A person's sub-agents run one at a time. See [Sub-agents](https://stampede.autonomousorganizations.ai/teamwork/sub-agents.md).

## Console-only tools

`schedule_task` in a preset takes effect at the console only, behind your confirmation. A gateway, mailbox or schedule run that calls it is refused.

`ask_user` in the `coordinator` list works as it does for every person: in an attended console or TUI it asks you; through the gateway it asks the member, only in the first run of that member's request; a run with nobody to ask gets `no_operator`.

## Choosing a preset

| The person should | Preset |
| - | - |
| Read, search, summarise, answer questions, send mail | `research` |
| Edit documents or code without running anything | `writer` |
| Run tests and linters and report, without editing | `reviewer` |
| Plan, delegate to other persons, schedule work from the console, ask questions | `coordinator` |
| Edit code, build, test, commit and open pull requests | `builder` |
| Do what `builder` does with programs outside its list | `maintainer`, or `builder` with `--allow-command` |
| Act with no limits as a trusted local assistant | `free` |

Start with the narrowest preset that does the job and add single programs or tools with `--allow-command` and `--allow-tool`. A gateway member's own requester person is always created `research`.

Changing a policy with `stampede person policy` applies to runs started afterwards. A run already started keeps the grant it began with.


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