Skip to content

Commit 78f6a93

Browse files
committed
feat(blog): add note about Assisted-by commit footers being a good idea
Assisted-by: GPT-OSS 120b on local hardware via OpenAI Codex Signed-off-by: Xe Iaso <me@xeiaso.net>
1 parent 3e876ba commit 78f6a93

1 file changed

Lines changed: 40 additions & 0 deletions

File tree

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: "Using Assisted-by commit footers instead of banning AI tools"
3+
desc: "It sounds like ceding ground to the pro-AI crowd, however if you get people to be honest about it then everyone benefits."
4+
date: 2025-11-02
5+
---
6+
7+
Something I've seen around the internet is that many projects want [a blanket policy of no AI tools being allowed](https://wiki.gentoo.org/wiki/Project:Council/AI_policy) for contributors. As much as I agree with the sentiment of policies like this, I don't think it's entirely realistic because it's trivial to lie about not using them when you actually do.
8+
9+
I think a better middle ground is something like [Fedora's AI-Assisted Contributions Policy](https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/). This demands that you include a commit footer that discloses what AI tools you've used in your process, such as this:
10+
11+
```text
12+
Assisted-by: GPT-OSS 120b via OpenAI Codex (locally hosted)
13+
```
14+
15+
Amusingly, you can actually tell AI agents to write this commit footer and they'll happily do it. Consider this part of [this repo's AGENTS.md file](https://github.com/Xe/site/blob/main/AGENTS.md) (AGENTS.md is a set of instructions for AI agents to know how to best contribute to the policy):
16+
17+
> **Attribution Requirements**
18+
>
19+
> AI agents must disclose what tool and model they are using in
20+
> the "Assisted-by" commit footer:
21+
>
22+
> ```text
23+
> Assisted-by: [Model Name] via [Tool Name]
24+
> ```
25+
>
26+
> Example:
27+
>
28+
> ```text
29+
> Assisted-by: GLM 4.6 via Claude Code
30+
> ```
31+
32+
Not only does this make it trivial for automation to detect when AI tools are being used (and add appropriate tagging so reviewers can be more particular), it lets you know which AI tools cause more issues in the longer run. This can help guide policy and assist contributors that want to use AI tooling into picking the best tools for the job.
33+
34+
Anyways, at a high level if you ask people to disclose what AI tools they are using and make it so that the default configuration of most AI tooling will just add that disclosure for you, people are much more likely to comply with that policy. I think that this is a better middle ground than having witch hunts trying to figure out who used what tool and letting it become a free ground for noisy, low‑quality contributions.
35+
36+
I want to see a future where people are allowed to experiment with fancy new tools. However, given the risks involved with low‑effort contributions causing issues, I think it's better for everyone to simply require an easy machine‑readable footer.
37+
38+
Also, if you want to put `Assisted-by: GNU Emacs`, I won't stop you.
39+
40+
This post was edited with help from GPT-OSS 120b on a DGX Spark, a device which only consumes 150 watts at maximum load. While I was writing this, I had Final Fantasy 14 open in the background to listen to bards perform in Limsa Lominsa. This made my workstation's RTX 4080 pull 150 watts of power constantly.

0 commit comments

Comments
 (0)