| title | Safety |
|---|---|
| description | Safety rules and constraints in clawpatch |
Current safety rules:
review,status,report,doctor, andmap --dry-rundo not edit source files.fixrequires explicit--finding <id>.fixrefuses a dirty source worktree by default..clawpatch/state changes are allowed during runs.- review and revalidate provider calls use a read-only sandbox for the
codexprovider. Theclaudeprovider restricts available tools to read/search tools for read-only operations. Theacpxprovider relies onacpx --approve-readsplus an explicit read-only prompt directive; underlying agents that bypass ACP permissions (e.g. agents running in their own full-access mode) may not be strictly sandboxed. See docs/providers.md. - provider output must pass runtime schema validation.
- feature locks are stored in feature records and
.clawpatch/locks/;statussurfaces both. Claims automatically reclaim same-host locks whose process is dead, andclean-locks --stale-onlyapplies the same conservative rule without clearing live local or remote locks. - the mapper skips symlinked directories and common generated directories.
Not implemented today:
- automatic commits
- automatic PRs
- automatic landing
- rollback snapshots
- global process locks
Git safety remains the caller's responsibility after a fix. Inspect git diff
and run project tests before committing.