Skip to main content
One installation of Stampede can run several assistants side by side, each with its own job and limits. Each of these assistants is a person: a durable identity with a name, a purpose, an optional private identity text, a model profile and a standing policy that bounds what it may do when nobody is watching.

What a person holds

A person also has its own project memory, goals, skills, sessions and mailbox. The operator’s user memory, secrets, workspace and run list are shared by every person on the home. Persons are cooperating assistants under one operating system account. They are not separate users and not sandboxes: you, as the operator, can read every inbox and every run. On a fresh home the only person is the built-in main, which is the active and default identity. The name main is reserved.

Creating a person

lead has no --policy, so it is free: it may use every tool and run every program the home allows. The command prints one line saying so:
stampede person create with no name asks for the name, purpose, identity and model on the terminal and creates a free person. In a script, always pass the name. --allow-tool and --allow-command need a preset. A free person is already unrestricted and refuses additions, and a maintainer refuses --allow-command because it already runs any program:
To write the identity file safely:

Listing and inspecting persons

person list prints one line per person with its policy label in parentheses: the preset name, free, or custom for a list that matches no preset. A leading * marks the default person.
person show prints the full record, the decrypted identity text included, and warns first. It also prints the effective program list.

Changing a person

Edits and policy changes apply to runs started afterwards. A run already started keeps the profile and the grant it began with, and a run resumed after a crash is checked against the current policy, so narrowing a policy can stop an old unattended grant.

Addressing a person from the console

In stampede tui or stampede chat, a line that starts with @name queues a request for that person. The person runs it in the background while you keep typing, and the console prints its progress lines.
A person is bounded by its policy even when you address it. @editor delete notes/summary.md is refused with a refusal line in the console, because the research preset has no write tool, and the file stays. To work as a person yourself, start a new process for it:
--person wins over STAMPEDE_PERSON, which wins over the default set with person use. A process keeps the person it started with. In such a session you are at the keyboard, so calls are decided by your own tool policy and your answers. The person’s policy binds its unattended work: @name requests, requests from other persons, schedule fires, webhook deliveries and gateway requests. Every person command also works inside the console with /person in place of stampede person, for example /person list or /person policy editor writer. /person NAME prints how to start a conversation as that person. See Console.

Mail and task rooms

Persons send each other durable mail with stampede person send and send_message, and work that needs several persons runs as a task room. Both are described in Mail and task rooms.

Observing a person’s runs

person runs lists the runs recorded for that person, each with its model and status. runs show prints a run’s events with one line per tool call: the tool, its outcome, and the gate that refused it when it was refused, followed by a count of tool calls by outcome. Prompts, arguments and outputs stay encrypted. --tokens adds one line per model call with token counts and cost. person runs does not say who drove a run, so a session you ran with --person is listed beside the person’s own work. In runs show, the first event’s owner label is operator for a session you drove and delegated for work the person ran on its own. Inside the console, /person runs and /person goals with no name use the active person.

Per-person settings

Some settings of a person live in ~/.stampede/config.toml, in a [persons.NAME] table:
Table names are compared without case. [persons.main] applies to your own runs as the operator. A table whose name matches no person changes nothing, and any other key in the table makes the file fail to load. A change applies to sessions and runs started after it. The full list of keys is in Configuration.