The workshop
The workshop is the group's agents working in the background. Members ask for work on its board. Agents on members' computers do it, each with its owner's approval, and propose the results as pull requests to the library or a paper. The hub only coordinates: it never runs an agent or a build.
The board
Workshop, beside the forum, library and papers, shows:
- the requests, waiting, running or finished;
- the group's recipes, or the errors in them;
- the group's model and how much of its monthly cap it has used;
- what Workshop is thinking about, and the pull requests its processes opened.
Guests can read the board. Members and admins ask.
Asking
Ask the workshop offers two ways:
- In plain words: a title and details. Workshop, the group's orchestrator, chooses a recipe and its inputs, a runner and machines, and reports in the request's thread. This needs a group model, set by an admin.
- With a recipe: choose one of the group's recipes and fill in its inputs: text, a paper, a declaration or a thread.
For a recipe, you also choose:
- Whose machines: yours, a particular member's, or anyone's with a given runner, and optionally a given model.
- When: now, at a date and time, or every day, week or N hours, until you stop it or an end date.
- How long to wait for a machine: an hour, a day or a week.
Every request is a numbered thread, [[t42]]. Its header shows the recipe, inputs, schedule, pull requests, processes, machines and the tokens used. Anyone in the group can discuss the work there. A message from the requester or an admin wakes Workshop up.
The requester or an admin can cancel a request. A recurring request can be paused, resumed or stopped.
Approval belongs to the machine
Your requests start at once on your own computers. Someone else's request waits on your computer until you approve it. Hub admins and group admins cannot approve for you. Approve in the app, in This machine › Workshop › Pending offers, or in a terminal:
stemma workshop pending
stemma workshop approve 12 # this run
stemma workshop approve 12 --series --runs 8 # this recurring request, eight runs
stemma workshop approve 12 --recipe --until 2027-01-01T00:00:00Z
stemma workshop decline 13
stemma workshop approvals # standing approvals
stemma workshop revoke 1A standing approval covers this request's series, or this version of a recipe from this person. It can be limited by date, number of runs, and minutes per run. When the recipe changes, you are asked again.
What happens next
A process starts on the machine, in a container, in a folder of its own: the recipe's
run.shand files, with your inputs in place, and checkouts of the library and of the papers you named.run.shruns. Most recipes launch the agent you chose, which posts progress in the request's thread.The run delivers what it produced, as its recipe allows: messages in the request's thread, and pull requests from its own branch.
Each pull request gets a card in the request's header, from the git orchestrator:
- it merges cleanly into
main, or - it conflicts with
main, and Workshop prepared a merge that resolves it, explained in plain words.
The requester or an admin reads it, with what the process said in the pull request, and approves the merge. The card follows
main: whenmainmoves, the merge is prepared again.- it merges cleanly into
A failed process may be retried once on another machine, if it had not pushed anything yet.
The group's model
In Group settings › Workshop, an admin gives the workshop an API key for Anthropic, OpenAI or OpenRouter, and chooses a model. Workshop uses it to handle requests in plain words and report, and to resolve a pull request's conflicts with main. People's agents never use this key: processes run with their machine owner's own agents.
- Use a key made for this, with a spending limit at the provider.
- The hub encrypts the key. Nobody can read it back, and only its last four characters are shown. Whoever runs the hub could still read it.
- Admins set a monthly token cap, 1,000,000 tokens by default, and a step cap per turn. At the cap, Workshop stops thinking until the next month or a higher cap.
Without a key, recipes still run, and pull requests that merge cleanly can be approved. Requests in plain words, and merges with conflicts, wait, saying a key is needed.
Recipes
A group's recipes are folders in its recipes repository: what each takes and delivers, the run.sh a process runs, and its files. Every group always has one, Anything else (general), for any task: one agent works on it for up to a day, and delivers pull requests and messages. The hub provides it, unless the group's recipes repository has its own general/ folder, which replaces it. See Writing recipes to add your own.