Ghostty 貢獻的更新 AI 使用政策

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

To see all available qualifiers, see our documentation.

Updated AI usage policy for contributions

      #10412

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Are you sure you want to change the base?

Updated AI usage policy for contributions

#10412

Conversation

mitchellh

  commented


    Jan 22, 2026


  

•

      edited
      
    
    


  


  

    



Loading






  

          Uh oh!

          There was an error while loading. Please reload this page.

Uh oh!

There was an error while loading. Please reload this page.

Follow up to #8289

The rise of agentic programming has eliminated the natural effort-based backpressure that previously limited low-effort contributions. It is now too easy to create large amounts of bad content with minimal effort.

Open source projects have always had poor quality issues, PRs, etc. That comes with the territory. Unfortunately, the ease and carelessness by which these are now manifested has increased the "bad" count by 10x if not more. It's ruining it for the rest of us. This policy is a result of the bad, and I'm sorry about it.

Going forward, AI generated contributions will only be allowed for accepted issues and maintainers. Drive-by pull requests with AI generated content will be immediately closed.

Going further, users who contribute bad AI generated content will be immediately banned from all future contributions. This is a zero-tolerance policy. If you use AI, you are responsible for the quality of your contributions. If you're using low-effort AI to create low-effort content, I have no human obligation to help you.

If you are a junior developer who is really trying to learn and get better, then please put aside the AI, do your best, and I will still help. I want to help. But I expect effort and organic thinking in return.

Important

This is not an anti-AI stance. This is an anti-idiot stance. Ghostty is written with plenty of AI assistance and many of our maintainers use AI daily. We just want quality contributions, regardless of how they are made.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

jcollie

  left a comment

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

LGTM

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

nexxai

  commented


    Jan 22, 2026

In the updated policy, you say that the "tool" used must be disclosed, but it feels like requiring the model might be more helpful, since tools like Opencode can interface with multiple models? Thoughts?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

mitchellh

  commented


    Jan 22, 2026


  

•

      edited
      
    
    


  


  

    



Loading






  

          Uh oh!

          There was an error while loading. Please reload this page.

Uh oh!

There was an error while loading. Please reload this page.

In the updated policy, you say that the "tool" used must be disclosed, but it feels like requiring the model might be more helpful, since tools like Opencode can interface with multiple models? Thoughts?

No, it's more important to me to know that AI was used. I don't particularly care what model. In the future, once there is more broad support, I plan on requiring full transcripts for any AI assistance that we can map 1:1 to the diff. But there isn't broad enough tool support for that yet.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Reviewers

jcollie

jcollie approved these changes

Assignees

Labels

Projects

Milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

4 participants

Footer

Footer navigation