Bot attribution on GitHub
How commits and comments the factory's agents make are marked, so anyone reading the history can see an agent made them and trace them back to the session.
Inside a Pix Sandbox, every commit Belai makes carries trailers that say an agent made it:
Co-authored-by: ...
Signed-off-by: Pix [bot] <...>with a link to the session that made it and, when the caller passes them, to the vulnerability ids the session touched (at most 10).
When trailers are added
- Only inside a Pix Sandbox. The sandbox writes
~/.pix/attribution. Without it, Belai is not in a sandbox and adds nothing, so a developer’s own commits are never signed off by a bot. - Belai’s own commits (a worker’s commit, the TUI’s auto-commit, remote control’s auto-commit) add them in code.
- A model’s own
git commitgets them from the sandbox’s commit hook. - Before a branch is published, Belai adds any trailers a repository’s own hooks kept out. If that rewrite fails, the branch is published as it was.
- The comment that closes a duplicate pull request carries them too.
Agents are told the trailers are added for them and must not write, change or remove them.
On GitHub
The factory recognises its own identities: the Vulnetix App’s bot, Pix [bot] and commits authored by security@vulnetix.com. Events from them never start runs. See Triggers. Delivery lists them under “Seen, and left out” and never counts them as people.