Customizing ampm's agents from your repo (.ampm/)
Any repository ampm works on can tune the agents that work on it, without touching ampm. Add files under .ampm/ in the repository root, and the agents read them from the checked-out working tree. Each job has its own short page, listed below. This address stays as the hub, so older links keep working.
Pages
- Tell ampm's agents how your repository works (markdown): use this when you want to add guidance for a role or a step in
.ampm/personas/and.ampm/steps/. - Give each step the sandbox it needs (markdown): use this when a step needs a database, a browser or another system tool, declared in
.ampm/environment.json. - Decide what a step's sandbox is missing (markdown): use this when a step has reported a missing tool, service or variable and you need to approve or refuse it.
- Land pull requests that always collide one at a time (markdown): use this when two kinds of change in your repository always conflict, declared in
.ampm/serializing-paths.json. - Choose what Autopilot trusts before it merges (markdown): use this when you want to name the checks that count as CI or the paths that make a merge riskier, in
.ampm/ci-evidence.jsonand.ampm/diff-risk.json.
Where each older section went
The older single-page guide had these sections. Each heading below links to the page and section that now holds that content.