- Capture an edit checkpoint before the agent changes files.
- Capture the agent’s edit after it writes files.
- Feed that data to
autter checkpointwith a stable preset name. - Let Autter write the authorship log on commit.
What an integration needs
Recommended shape
If your agent supports before-edit and after-edit hooks, wire Autter into those hooks first.1
Choose a preset name
Pick a name that matches the agent or workflow, such as
cursor, claude, codex, github-copilot, or windsurf.2
Emit the hook input
Serialize the edit event, workspace root, file list, and session identifiers in the format your integration already owns.
3
Call Autter
Run
autter checkpoint <preset> --hook-input stdin from the hook or integration layer.4
Test the full flow
Confirm that
autter status shows the expected authorship and that autter stats counts the change correctly after commit.How to test
Test the same integration in the shells and operating systems you plan to support. Check these cases:- A single file edit
- A multi-file edit
- A human edit followed by an agent edit
- A commit that lands on a branch, rebase, or cherry-pick path
What to document for users
When you ship support for a new agent, tell users:- whether they need
autter install-hooks - whether they should restart the editor or agent after install
- which shell and OS combinations you tested
- how to remove the integration with
autter uninstall-hooks
CLI command reference
See the checkpoint command and related CLI flags.
Troubleshooting
Help users recover if attribution does not appear.

