Page:
Reference Exit codes
Pages
Dev Development
Explanation Architecture
Explanation Configuration tiers
Explanation Knowledge and commitment
Explanation Language boundaries
Explanation Model and effort selection
Explanation Ownership and templates
Explanation Pipeline rationale
Explanation Telemetry and evaluation
Explanation Version model
Explanation Why gates are code
Explanation
Home
How to Back up to a synced folder
How to Browse with obsidian
How to Capture repository docs
How to Collect from a synced folder
How to Export guidelines
How to Export to a synced folder
How to Fetch pages behind a login
How to Ingest a source
How to Maintain the wiki
How to Query the wiki
How to Run the weekly review
How to Set up the mcp server
How to Trace and score sessions
How to Troubleshoot
How to Update an instance
How to Use 1password for settings
How to Write a site handler
How to
Install
Reference Commands Catalog and log
Reference Commands Configuration
Reference Commands Content migrations
Reference Commands Distribution and versioning
Reference Commands Exports
Reference Commands Finding and checking
Reference Commands Git
Reference Commands Instance health
Reference Commands Links and citations
Reference Commands Pages
Reference Commands Provenance
Reference Commands Raw material and uploads
Reference Commands Telemetry
Reference Commands Types instructions and docs
Reference Commands Workshop runs and session budget
Reference Commands
Reference Configuration
Reference Exit codes
Reference Page types
Reference Skills
Reference
Tutorials First source to first answer
Tutorials Sample source
Tutorials
Clone
This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Generated from docs/reference/exit-codes.md at v10.1.0 – edit the repository, not this wiki.
Exit codes and gates
Which wikitool commands can stop and wait for a person - exit 42 - and for which gate, generated
from the command records.
What each exit code means, and how a caller reacts to it, is AGENTS.md § Tool error contract. What a gate is and why it is enforced in code is AGENTS.md § Gates. This page lists which commands declare a gate, and every cause for which a command exits 42.
Gates by command
guideline-push
mass-update
publish-remote
rebase-review
upload-review
Exit 42 causes
new: new project: The provider cannot create the project itself (Super Productivity'saccess: "api"); the output says what a human has to createtask new: The tracker settings file of an earlier version is still there, or a secret source (1Password) needs unlockingtask list: The tracker settings file of an earlier version is still there, or a secret source (1Password) needs unlockingtask close: The tracker settings file of an earlier version is still there, or a secret source (1Password) needs unlockingreview: The tracker settings file of an earlier version is still there, or a secret source (1Password) needs unlockingraw fetch: The host is fetched with the user's session and none is stored, or the page arrived without the sign of being signed in that its site handler names (the session expired)raw fetch: The site handler declaresrenderand the optional browser component is not installedraw login: The optional browser component is not installedupload accept: Upload Review Gate:--confirmis absent or does not match the manifest's current tokensync: Rebase-Review Gate:<remote>/<branch>moved and both sides changed the same file, generated files aside; the output lists the upstream commits, the overlapping files and their diffpublish: The remotes settings file of an earlier version is still therepublish: Mass-Update Gate:--threshold(default 10) or more counted files would be committed, or the--confirmtoken does not match this changesetpublish: Rebase-Review Gate:<remote>/<branch>moved and both sides changed the same file; the output lists the upstream commits, the overlapping files and their diffpublish: Publish-Remote Gate:remotes.allowed_push_urlsis set and the push URL of--remoteis not listed in it, or--remoteresolves to no push URLexport guidelines: Guideline Push Gate:--pushwithout--confirm, or with a token that does not match the current set of targetsconfig set: The field names a program to run or affects a gate
- Chemenu - Personal IT Knowledge Base
- Install a Chemenu instance
- Tutorials
- How-to guides
- Back up to a synced folder
- Browse the wiki in Obsidian
- Capture documentation from a git repository
- Collect documents from a synced folder
- Export guidelines to captured repositories
- Export to a synced folder
- Fetch pages behind a login
- Ingest a source
- Maintain the wiki
- Query the wiki
- Run the weekly review
- Set up the MCP read server
- Trace and score agent sessions
- Troubleshoot an instance
- Update an instance
- Use 1Password for settings
- Write a site handler
- Reference
- Explanation
- Architecture
- Configuration tiers
- Why knowledge and commitments are two layers
- Language Boundaries
- Choosing a Claude Code model and effort level
- Ownership and Templates
- Why the pipeline has four stages
- Telemetry and evaluation
- Why the stack version splits compatibility from migration
- Why gates are code
- Dev