Every commit made by a coding agent carries a signature at the bottom of the message: the Co-Authored-By trailer. Most devs never notice it. We did, because it is the simplest proof that Verboo Code actually works on our own codebase, not just on everyone else's.
How do you know if a commit was written by a coding agent?
Open the full commit message (git log -1 --format=%B, or the commit page on GitHub) and look for a line shaped like Co-Authored-By: Name <email> at the end. A commit trailer is formal Git metadata, recognized by git interpret-trailers, and GitHub uses that exact line to render a second author on the commit.
When the signer is an agent instead of a person, the name usually identifies the tool. A commit made with Verboo Code ends like this:
Co-Authored-By: Verboo Code <noreply@code.verboo.ai>This is not an informal team convention. It is fixed behavior baked into the CLI binary.
What does Verboo Code write in that trailer by default?
The value comes straight from the public source code, in src/utils/attribution.ts of the verbeux-ai/code repository:
export const VERBOO_COMMIT_CO_AUTHOR =
'Co-Authored-By: Verboo Code <noreply@code.verboo.ai>'Unlike agents that name the specific underlying model in the trailer (a particular Claude model, for example), Verboo Code always signs as "Verboo Code", regardless of whether the session is actually running mimo-v2.5, GLM, or deepseek underneath. The brand shows up in front of the model, every time.
How do you control that attribution from the terminal?
The CLI exposes a real /commit-message command inside the interactive session, with working subcommands:
| Command | What it does |
|---|---|
/commit-message status | Shows the configured value and the current effective value |
/commit-message off | Turns off the trailer for the next commits made with /commit |
/commit-message default | Resets to the default (Verboo Code <noreply@code.verboo.ai>) |
/commit-message set "Generated with Verboo Code using GPT-5.5" | Sets custom attribution text |
/commit-message co-author "Your Name" you@example.com | Swaps only the co-author, keeping the rest of the format |
In a CI pipeline, without an interactive session, the same effect as off is one environment variable away:
VERBOO_DISABLE_CO_AUTHORED_BY=1How much of our own code has Verboo Code actually signed?
We counted it directly on GitHub's search API, no estimate involved. Over the last three and a half months, the Co-Authored-By: Verboo Code trailer showed up in 427 real commits, spread across more than a dozen of our internal repositories.
gh api search/commits -f q='"Co-Authored-By: Verboo Code" org:your-org' --jq '.total_count'Swap "Verboo Code" for whatever name shows up in your tool's trailer, and "your-org" for your own GitHub organization. This works for any agent that leaves this trail: GitHub Copilot, Cursor, Claude Code, Verboo Code.
| Period | Commits with the trailer |
|---|---|
| May 2026 (from the 27th on) | 13 |
| June 2026 | 221 |
| July 2026 | 126 |
| August 2026 | 60 |
| September 2026 (through the 10th) | 7 |
| Total | 427 |
The number swings month to month because it reflects how many PRs the team actually opened in that period, not a permanently rising curve. What matters isn't the trend, it's that the trailer is auditable by anyone with repo access, including people who don't trust a number a tech company publishes about its own product.
If you want to see another slice of this same operation running on the product itself, read how Verboo runs marketing with 5 MCPs and 5 skills without a hired writer.
Want your own team's commits to carry this kind of auditable trail, without worrying about a token cap? Check out Verboo Code.
