Skip to content

Conversation

@clavin
Copy link
Member

@clavin clavin commented Jan 13, 2026

This RFC proposes an official policy on AI-assisted contributions to Electron. The goals are to:

  1. Set clear expectations for contributors using AI tools
  2. Give maintainers something to reference when closing low-quality submissions
  3. Encourage transparency and good practices
  4. Protect maintainer time and energy

📄 Read the rendered RFC & Policy

Copy link
Member

@erickzhao erickzhao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wholeheartedly agree with the ethos of this policy.

While reading through this RFC, TIL of git interpret-trailers as well.


We encourage disclosure of AI tool assistance in code contributions. This practice helps facilitate productive code reviews, and is not used to police tool usage.

When AI tools meaningfully assist in your contribution, note it in the commit message with a [trailer](https://git-scm.com/docs/git-interpret-trailers):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're defining rules for agents, does this mean that there should be some kind of Claude Code attribution setting we can add to the .claude folder in Electron core?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code should default to attributing itself to commits generated with CC. If users commit manually there's not a lot you can do other than just eyeball it (and have this in the policy)

Copy link
Member

@MarshallOfSound MarshallOfSound left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine and reasonable to me all round. I'm interested in what enforcement looks like and what we can do to force people to read this policy.

E.g. Link it in the PR template and auto-close any third-party PR that hasn't explicitly checked that box (we can even cheat and "prompt" any model reading the PR template to never check that box by itself in an html comment or something)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants