mnemom. Mnemom checks the request, seals it as a contract and starts a job. An agent does the work and opens a PR. The Mnemom record check on that PR shows the sealed contract.
Contracted agents build on durable sessions. Mnemom durable agent and Mnemom contracted agents come with the Durable agent invite tier, enabled per Mnemom org by invitation. Ask for access at mnemom.ai/waitlist.
setup contracted checks this first. The server runner needs the experimental dispatch feature. It may change or be removed with no deprecation period.Set up a repo
--dry-run prints the first screen and changes nothing. --json prints the plan and outcome as JSON and never prompts.
With the default runner (your CI), the steps are:
- Durable. Checks that durable sessions are on for your org and turns the Mnemom record on.
- GitHub App. Checks that the Mnemom Record App is installed on the repo. If not, it prints the install link and waits.
--app <slug>names a different App. - Model key. Checks that the repo has an
ANTHROPIC_API_KEYsecret (by name only, never the value). If not, it takes the key from$ANTHROPIC_API_KEYor a hidden prompt. It also gives the same key to Mnemom for the intake check. - Turn on. Switches the repo on with Mnemom.
- Runner. Checks that GitHub Actions is on, then opens a PR that adds the runner workflow and merges it.
--branch <name>sets the PR branch (defaultmnemom/record-enable).
Set up without a browser
Setup can run on a machine with no browser or terminal, such as CI or a server:- Sign in with an API key. Set
MNEMOM_API_KEY. Setup uses the key’s own org. An org you selected earlier on this machine still wins. - Name the agent. Set
MNEMOM_AGENTto an agent your org already has. The agent step needs it, because an API key has no login email to name the agent from. - Prove you administer the repo. Where setup would ask you to approve through GitHub in your browser, it uses
MNEMOM_GITHUB_TOKEN, elseGH_TOKEN, instead. Use a GitHub token of a repo admin. Setup never usesGITHUB_TOKEN: inside GitHub Actions that is the workflow’s own token, which cannot show that a person administers the repo. The token is used for that one check and is not stored.
Start a job from an issue
Label an issuemnemom to start. Without the label, opening or editing an issue does nothing. Mnemom checks the request, seals it as a contract and starts a job. If the request is not clear enough, Mnemom sends it back with a comment, and you edit the issue to answer.
The job opens a PR against the default branch and keeps working on it as you review. The PR gets a Mnemom record check that shows the sealed contract.
Hand an issue to the contracted agent covers how to write an issue that seals the first time, the optional limits block, and what the agent does on its PR.
Runners
Every job runs on exactly one runner. The repo has a default, and a single job can use another.CI
The runner is a GitHub Actions workflow that setup adds to the repo. It runs only on the default branch, is started by Mnemom, and needs theANTHROPIC_API_KEY repo secret.
A job can run for up to 6 hours (timeout-minutes: 360). This is GitHub’s hard limit for a job. The key the job gets from Mnemom also lasts 6 hours.
The Actions minutes are your own.
Server
With--runner server, jobs wait for a runner on your own machine:
mnemom agent run --once runs a single job and exits.
- A server job waits for a runner with no timeout, and it does not fall back to another runner.
mnemom agent sessionsandmnemom agent showsay why a waiting server job waits: no runner is enrolled for the repo, or no runner has claimed the job yet. Afix:line gives the command to run. With--json, the reason is inwaiting_reason.- The job’s transcript stays on your machine. The two newest are kept.
- A re-run of setup without
--runnerkeeps the repo on the server runner. To move it back to CI, pass--runner ci.
Revoke a server runner
If a runner machine is lost or its key leaks, revoke it from any machine signed in as the person who enrolled it:- The runner’s key stops working at once, so it claims no more jobs.
- Locked durable sessions the runner held are parked. The command says how many.
- Only the person who enrolled a runner can revoke it. Anyone else gets the same answer as for an unknown id.
- Revoking a runner that is already revoked changes nothing.
- If the command reports a server or network error, the runner may still be live. Run it again.
- To enroll the same machine again:
mnemom agent runner enroll --force.
--json.
Mnemom-hosted (experimental)
The Mnemom-hosted runner is experimental. It is open to invited orgs, and each org can run only a capped number of hosted jobs at once.
--hosted, Mnemom runs the jobs. There is no workflow PR, no repo secret and no machine to keep running.
- Hosted. Confirms through GitHub that you administer the repo: you enter a code in your browser. The repo then switches to the hosted runner. You need admin or maintain on the repo, and the Mnemom Record App installed on it.
- Model key. Checks that an Anthropic key is stored for your org. If not, it reads one from a hidden prompt, or from stdin with
--model-key-stdin. The key is stored encrypted at Mnemom. It pays for the intake check and for hosted runs, billed to you by Anthropic.
--json cannot finish the GitHub step, so run setup once in a terminal. With no active org, setup uses your only team org. If you belong to several, it stops and asks you to run mnemom org use <slug>.
- A hosted job needs a Mnemom balance. With none left, the job ends instead of starting.
- When your org already has as many hosted jobs running as its cap allows, a new job waits and starts when one finishes. To raise your org’s cap, email support@mnemom.ai.
- A re-run of setup with neither flag keeps the repo hosted. To leave hosted, pass
--runner cior--runner server. - If setup says the hosted runner is not turned on yet, it is not open to your org. Use CI or a server runner.
Run one job on a different runner
mnemom agent fuel seals a batch of contracts in one confirmation. --runner ci|server|hosted runs that batch’s jobs on the runner you name. Without it, they use the repo’s default.
What it costs
You pay Anthropic directly for the model. Your Anthropic key pays for the intake check and for the agent’s work. CI jobs also use your own GitHub Actions minutes. Hosted jobs draw on your Mnemom balance. Contracted agents are not a plan tier.Turn a repo off
--off to turn the repo back on.