<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta" -->

---
title: Changes to SourceHut's terms of service regarding LLMs
description: SourceHut is updating its terms of service to prohibit original content produced with or facilitated by LLMs and other generative AI tools, including code,...
canonical: https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Changes to SourceHut's terms of service regarding LLMs | daily.dev
og:description: SourceHut is updating its terms of service to prohibit original content produced with or facilitated by LLMs and other generative AI tools, including code,...
og:url: https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta
og:image: https://api.daily.dev/og/posts/Fx95G81tA.png
og:image:alt: Changes to SourceHut's terms of service regarding LLMs
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Changes to SourceHut's terms of service regarding LLMs

**[Lobsters](https://daily.dev/sources/lobsters)** · 13 min read · 0 upvotes · 0 comments

## Summary

SourceHut is updating its terms of service to prohibit original content produced with or facilitated by LLMs and other generative AI tools, including code, tickets, and emails. The change takes effect September 10th for new projects following a two-week notice period. Existing AI-assisted projects can stay if they adopt compliant policies going forward, with no retroactive enforcement, though projects wanting to continue using AI must plan a migration away, with SourceHut recommending Forgejo or self-hosting as alternatives. The policy targets 'original' content specifically, allowing mirrors of projects like the Linux kernel with more lenient AI policies. Enforcement will be light-touch and honor-based rather than automated detection. The rationale cites climate impact, labor exploitation, licensing violations, and harm to open source culture as the primary drivers, following a similar move by Codeberg in July.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://sourcehut.org/blog/2026-08-27-tos-changes-and-llms>

## Questions this post answers

### When does SourceHut's new policy banning AI-generated code take effect?

The updated terms of service prohibiting original content written with or facilitated by LLMs and other generative AI technologies go into effect for new projects on September 10th, following the standard two-week notice period. This covers source code, assets, tickets, and emails produced with AI assistance.

_daily.dev helps developers track platform policy shifts like SourceHut's AI restrictions before they affect a project._

### Will SourceHut delete or ban existing projects that already used AI tools?

No, there is no retroactive enforcement. Existing projects that used AI assistance may remain on SourceHut as long as they adopt policies consistent with the new terms for future development, and SourceHut will take action against anyone who shames or harasses users for past AI use.

_Developers weighing forge migrations can follow policy nuances like this one on daily.dev before committing._

### Can I still host a mirror of the Linux kernel on SourceHut if it contains AI-assisted patches?

Yes, because the policy specifically targets 'original' content, so mirrors of major codebases with more lenient LLM policies, such as the Linux kernel, remain allowed. An individual can host a personal tree or stage patches for a subsystem aligned with SourceHut's policy, but SourceHut cannot serve as the upstream platform for the broader Linux project given its more permissive AI stance.

_daily.dev keeps developers current on forge-specific carve-outs like this one for mirrored or upstream codebases._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 71 comments across lobsters, hackernews (as of 2026-08-30).

**TL;DR:** Reaction is split between strong support for a principled anti-LLM stance and skepticism that the policy is impractical, hard to enforce, and will shrink SourceHut's usefulness by excluding most modern development workflows.

**Sentiment:** 30% positive · 35% mixed · 35% skeptical

**The case for**

- Many see the policy as well-written, nuanced, and consistent with SourceHut's long-standing principled/minimalist ethos.
- Some argue LLM-free forges create a useful trust signal, filtering out low-quality 'slop' contributions.
- Supporters say clarity on where the line is (asking questions vs. having an LLM write code) is better than most policies they've seen, and mailing-list sentiment cited was strongly in favor.

**The pushback**

- Critics argue the vast majority of working developers use LLMs at least incidentally, making the policy impractical or self-marginalizing.
- Some find edge cases like the 'facilitates use of LLMs' clause (e.g. banning MCP servers or LLM-friendly APIs) confusing or overly broad.
- A few paying users say they plan to cancel, viewing it as unenforceable moral grandstanding over how they write code.
- Concern that this pushes SourceHut/Codeberg further into niche/hobbyist territory rather than serious professional use.

**By community**

- lobsters (mixed): Long, detailed thread debating whether the policy is workable, with some praising its nuance and others (especially one persistent commenter) arguing it excludes the vast majority of real-world coding workflows.
- hackernews (mixed): Discussion splits between disappointed paying customers considering leaving and others who respect the stance, with a cited mailing-list tally showing roughly 2.5x more support than opposition.

**Hottest debate:** Whether lightweight LLM use (like asking an LLM which API call to use, then typing it yourself) counts as a violation, with disagreement over where exactly the line between 'assistance' and 'co-authoring' falls.

**Open questions**

- Where exactly does the line fall between permitted LLM use (asking questions, review) and prohibited use (co-authoring code)?
- Does the 'facilitates the use of LLMs' clause ban things like MCP servers or LLM-friendly APIs even if the code itself is human-written?
- How will light-touch, honor-based enforcement actually work in practice for edge cases?

**Highlights**

> This is a statement about what you know rather than a statement about programmers generally. I know plenty who do not use LLMs in any capacity.
> — [lpil on lobsters · 21 points, 1 comments](https://lobste.rs/s/iqgrsx/changes_sourcehut_s_terms_service#c_cixfqw)

> The author of the piece you just read is the main developer and maintainer of sourcehut. It is certainly a serious software project by any measure I can come up with, and they use it to maintain sourcehut itself. Coupled with the replies in this thread, it would seem that you now know multiple programmers who don't use LLMs to assist writing code. And you now know of at least one serious project for which sourcehut is very usable. [Fennel is another](https://git.sr.ht/~technomancy/fennel) serious software project that doesn't use LLMs and finds sourcehut very suitable. [Offpunk is another](https://sr.ht/~lioploum/offpunk/). It's not hard to find more if you're interested.
> — [hoistbypetard on lobsters · 6 points](https://lobste.rs/s/iqgrsx/changes_sourcehut_s_terms_service#c_obmxuy)

> I think you're stuck between the devil and the deep blue sea, my friend. The devil is that if LLM use helps you a lot, it's probably because it's doing something immoral or outright illegal, like ripping the license off OSS code. The deep blue sea is that if you're not doing anything immoral, you're still likely killing yourself and your project by ceasing to learn, ceasing to build tools, ceasing to feel pain, and above all ceasing to build community.
> — [conartist6 on lobsters · 3 points, 1 comments](https://lobste.rs/s/iqgrsx/changes_sourcehut_s_terms_service#c_qnvlt7)

> Summary of the mailing list discussion (https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3CDKSTMKM0ZD9N....) - counted by hand without LLM assistance so there may be mistakes or misreadings :) ~51 in favor of the proposal. 20 of those specifically stated a desire for a blanket or as-strong-as-possible ban. 17 mentioned paying for the service. Many (sorry, didn't count these!) stated that the reason they joined SourceHut in the first place is because of the strongly opinionated culture and that an LLM ban aligns well with that. ~19 opposing the proposal to some degree. (I am counting Greg K-H's comments as a very weak "oppose".) 5 specifically mentioned paying for the service, and 1 stated they will stop paying if the policy takes effect. Some stated that they don't personally use LLMs, or don't like them or the effects they have, or would support a weaker ban (e.g. only ban fully vibe-coded projects or excessive resource usage).
> — [Nnnes on hackernews](https://news.ycombinator.com/item?id=49464271)

> That "facilitates the use of" thing is something of a wtf. If I have a web application which includes an MCP server (as just one of many features) is that whole project banned? What about if it has a REST API? Obviously not... But what if that REST API is designed to be easy for LLM tools to use?
> — [simonw on lobsters · 2 points, 1 comments](https://lobste.rs/s/iqgrsx/changes_sourcehut_s_terms_service#c_q0n5s5)

**Source threads**

- [lobsters](https://lobste.rs/s/iqgrsx/changes_sourcehut_s_terms_service) · 77 points · 63 comments
- [hackernews](https://news.ycombinator.com/item?id=49461724) · 20 points · 8 comments

## Similar posts on daily.dev

- [AI Can No Longer Rampage Through Rust's Code Repo](https://daily.dev/posts/ai-can-no-longer-rampage-through-rust-s-code-repo-npr4hm4wd) · It's Foss · 11 upvotes · 0 comments
- [LLM-Driven Large Code Rewrites With Relicensing Are The Latest AI Concern](https://daily.dev/posts/llm-driven-large-code-rewrites-with-relicensing-are-the-latest-ai-concern-5h8lrreld) · Phoronix · 1 upvotes · 0 comments

---

Tags: [#open-source](https://daily.dev/tags/open-source), [#vibe-coding](https://daily.dev/tags/vibe-coding), [#forgejo](https://daily.dev/tags/forgejo)

[View this post on daily.dev](https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Changes to SourceHut's terms of service regarding LLMs","url":"https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta"},"datePublished":"2026-08-27T10:32:38.381Z","dateModified":"2026-08-30T05:48:39.357Z","description":"SourceHut is updating its terms of service to prohibit original content produced with or facilitated by LLMs and other generative AI tools, including code,...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,vibe-coding,forgejo","timeRequired":"PT13M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Changes to SourceHut's terms of service regarding LLMs"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/changes-to-sourcehut-s-terms-of-service-regarding-llms-fx95g81ta#faq","mainEntity":[{"@type":"Question","name":"When does SourceHut's new policy banning AI-generated code take effect?","acceptedAnswer":{"@type":"Answer","text":"The updated terms of service prohibiting original content written with or facilitated by LLMs and other generative AI technologies go into effect for new projects on September 10th, following the standard two-week notice period. This covers source code, assets, tickets, and emails produced with AI assistance. daily.dev helps developers track platform policy shifts like SourceHut's AI restrictions before they affect a project."}},{"@type":"Question","name":"Will SourceHut delete or ban existing projects that already used AI tools?","acceptedAnswer":{"@type":"Answer","text":"No, there is no retroactive enforcement. Existing projects that used AI assistance may remain on SourceHut as long as they adopt policies consistent with the new terms for future development, and SourceHut will take action against anyone who shames or harasses users for past AI use. Developers weighing forge migrations can follow policy nuances like this one on daily.dev before committing."}},{"@type":"Question","name":"Can I still host a mirror of the Linux kernel on SourceHut if it contains AI-assisted patches?","acceptedAnswer":{"@type":"Answer","text":"Yes, because the policy specifically targets 'original' content, so mirrors of major codebases with more lenient LLM policies, such as the Linux kernel, remain allowed. An individual can host a personal tree or stage patches for a subsystem aligned with SourceHut's policy, but SourceHut cannot serve as the upstream platform for the broader Linux project given its more permissive AI stance. daily.dev keeps developers current on forge-specific carve-outs like this one for mirrored or upstream codebases."}}]}
```

