Usage
momonga [options] [prompt]The reference lists every option and command, with the options of each command, the settings keys, the environment variables, and the exit codes. It is generated from the product's own tables. Run momonga <command> --help for the options of each command.
momonga update replaces the executable with the latest release after verifying its checksum and signature. momonga update --check only reports whether a newer release exists. An update never interrupts running work. If the daemon was running, both momonga update and the automatic update start a daemon of the new version beside it. The new one serves every new request at once. The old one accepts no new work, finishes the steps and background jobs it already runs, and then ends by itself; momonga daemon status lists it as retiring until then. A session opened before the update keeps working on the old daemon while that daemon lives, and is then told that momonga was updated and to reopen it. If the new daemon does not start, the new version stays installed, the old daemon keeps running, and the message says what to run. momonga daemon stop is the only command that interrupts running work: it stops every running daemon, and it first prints how many running steps and background jobs it interrupts.
A release build also checks for updates in the background, at most once every 24 hours. When it starts a command other than update and the internal ones, it runs the check in a detached process and, if a newer release exists, installs it on its own. The installation verifies the release's signed checksum list, the executable's sha256 and, where the build pins an Apple Team ID, its Developer ID signature, and it runs the new executable with --version before it replaces the file. If the check or the installation fails, nothing is replaced. Once the new executable is in place, a daemon of the new version is started beside a running one as described above, and a session that was already open keeps the old one until that daemon ends. Before a later command runs, momonga prints a one-line notice once (on standard error, or in the interactive session's notices) that the update was installed or that the check failed. Set "autoUpdates": false in the user settings to turn the background check and its notices off; it is read only from user settings. A build run from source never updates itself.
Delegated work
A mandate is a named grant in your user settings, under mandates: the rules it adds (allow, ask, deny), the completion conditions it owes (until, require), and its budget (steps, tokens, costUsd, timeMs, retries). A run under a mandate runs only what the mandate and your rules allow; a call the mandate asks about is held for your approval while the rest of the run goes on, and onQuiescent says whether a run with nothing else to do waits for that approval (wait) or ends with a report (report). Start one with momonga -p --mandate <name> "<request>", or /delegate <mandate> <request> in the interactive session. Mandates are read only from the user settings. When a run under a mandate is created, the daemon checks the rules of the folder together with the mandate's, and refuses the run if an allow rule gets around a deny rule.
Git and pull request operations (GitPush, GitFetch, the pull request and issue tools) reach a remote only through a forge you declare in forges: an entry with an id, a descriptor, its hosts, its apiBaseUrl, and one credential reference, credential.env or credential.secret. A remote written for SSH on a declared forge is reached through that forge's HTTPS address with its credential; a remote on no declared forge is refused, and the refusal names the entry to add. Git started for such an operation takes no hook, credential helper or proxy program from the repository.
momonga -p --issue <address> --mandate <name> works on one issue of a declared forge and ends with a pull request that closes it and a comment on the issue. The issue watch, issues.watch in the user settings, asks the declared forge of each entry every five minutes for open issues that carry its labels and whose author has one of its authorAssociation values, and starts each new one once in the entry's folder under its mandate. An entry with neither filter takes no issue, and pull requests are never taken.
A budget bounds every run. Without one, a run stops after 50 steps or 1 000 000 tokens. --max-cost-usd <usd> on momonga -p, or limits.maxCostUsd in the user settings, stops a run before a model request that would pass that amount; a mandate's budget bounds the runs under it.
Verification and reports
momonga reliability reports, over the runs of a period, how many completed, recovered, repeated work, needed you, ran out of budget, and what they took in time and cost, grouped by model, mode, agent, origin or period; --json and --out <file> keep the report. momonga eval bench <folder> runs every case of the bench set in the folder on one model, each trial in a fresh copy of its repository, and checks it with the oracle of that case; momonga eval compare <baseline> <candidate> --gate reliability judges two such reports. momonga permissions review lists a sample of recorded calls that ran without asking you and of calls that asked, and stores your review of each (--label correct, unneeded_ask, or missed_ask).
When a run fails its conditions, it ends STOPPED; no stronger model takes it over.
Verifiable completion
A run declares its completion conditions when it starts, and the set does not change while it runs. The declaration is the union of three sources:
- the request:
--untiland--requireonmomonga -p, or the mandate an ACP client or a benchmark task sends; - the agent definition:
conditionsandrequirementsin the front matter of a custom agent (inherit: falsein a request or an agent narrows the declaration to its own conditions); - the settings: every command you set in
verification.commands, and the check of the folder that you accepted, is a standing condition of the folder. It is owed only by a run that changed the workspace; a run that only answers a question does not pay for a test suite. The default list ofverification.commandsdeclares no condition.
When the model stops, MomongaCode runs every owed condition itself. A command the model ran, even the same command with exit code 0, is never evidence. If a condition fails and the run changed the workspace since the last failed round, the failures go back to the model; if the model stops again without a change, the run ends STOPPED with the reason conditions_unmet. A check runs for at most its declared timeout, or 600 seconds. With "verification": { "required": true }, a run that changed the workspace without any declared condition also ends conditions_unmet. A condition that a deny rule matches refuses the run when it is created.
momonga report [run-id], and /report inside the interactive session, show the report of a run: each condition with its state and exit code, what was not run and why, the files the run changed, the residual risk as counted facts, and the commands the model ran that equal a condition (informational). The interactive session, --print and ACP show each check as it runs and name the unmet conditions when the run ends. The check of a folder is proposed once: when the interactive session starts in a trusted folder that declares a test command (a test script of package.json, or a test rule of a Makefile or justfile), it asks whether that command is the check of the folder. Your answer, accepted, typed or declined, is kept in your user settings under projectChecks. /init and /config show and change it, and so does momonga project-check show, set <command> and clear. A run that changed the workspace with no declared condition and no check ends unverified: nothing is learned from it, and a notice says how to declare a check. verification.required is false by default; with true, such a run ends conditions_unmet instead.
Changed behaviour for folders that set verification.commands. Before this release these commands only told the memory which commands count as verification. They are now also completion conditions: a run that edits files ends STOPPED (conditions_unmet) where it used to end COMPLETED, whenever one of the commands fails on the final state of the workspace, and each of them runs after the model stops. momonga -p exits non-zero for such a run. Memory follows the same verdict: a run is a verified success, and so may propose memories and repository facts, only when it declared at least one condition and all of them passed; a passing command the model ran itself no longer counts.
Inside the interactive session, slash commands include /help, /clear, /exit, /mode, /model, /rule, /memory, /auto-mode, and /cost, /status, /jobs, /trace, /report, /mcp, /context, /policy, /gateway, which run the command of the same name. /help lists the rest. The configured models are seen and changed from the last row of /model, Model settingsā¦, or from the Models entry of /config.