--- title: Oracle just banned AI-generated code | daily.dev description: Oracle has banned contributing AI-generated content to OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images—while... canonical: https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Oracle just banned AI-generated code | daily.dev og:description: Oracle has banned contributing AI-generated content to OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images—while... og:url: https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj og:image: https://api.daily.dev/og/posts/wJ3LH7DBJ.png og:image:alt: Oracle just banned AI-generated code 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. # Oracle just banned AI-generated code **[Awesome](https://daily.dev/sources/awesome-coding)** · 8 min read · 11 upvotes · 0 comments ## Summary Oracle has banned contributing AI-generated content to OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images—while still allowing private LLM use for understanding code, debugging, and research. The stated reasons are reviewer workload, safety/security, and IP concerns. The piece compares this to similar policies at Zig (strict no-AI, even for brainstorming), Rust (private use fine, but generated docs/comments banned, generated code allowed only under a disclosed, reviewed experimental process since August 5th), LLVM (AI contributions allowed if a human takes responsibility), and the Linux kernel (AI-generated code and AI-discovered bugs allowed but must be reproduced, tested, and disclosed by a human). The author argues software will split into three tiers—low-stakes slop-codeable projects, customer-facing code needing quality and ownership, and high-leverage systems like kernels, runtimes, and banking infrastructure that demand handcrafted, high-quality code. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Oracle's new policy on AI-generated code contributions to OpenJDK? Oracle bans contributing AI-generated output back into OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images. Contributors may still privately use LLMs to understand the codebase, debug problems, review code, and do research, but cannot submit AI-generated output as a contribution. Oracle cites reviewer workload, safety and security, and intellectual property concerns as the reasons. _Developers weighing AI contribution rules across ecosystems can track policy shifts like this one on daily.dev._ ### How does Rust's AI contribution policy differ from a full ban? Since August 5th, several Rust teams allow private AI usage but generally ban AI-generated documentation, diagnostics, and comments. AI-generated code can be accepted only under an experimental process that requires disclosure, prior arrangement with a reviewer, non-critical scope, proper testing, and full understanding by both author and reviewer. _Anyone deciding how to use AI safely in a codebase can follow how projects like Rust set contribution guardrails on daily.dev._ ### What does the Linux kernel require for AI-generated code and AI-discovered bug contributions? Linux kernel documentation requires that AI-generated code be reviewed by the human submitter, who must ensure licensing compliance, test the fix, and take full responsibility for the contribution. For AI-discovered bugs, agents must reproduce the problem, produce a fix, build it, test it, and disclose anything they could not verify. _Maintainers weighing AI-assisted bug fixes against accountability requirements can follow policy details like these on daily.dev._ ## Similar posts on daily.dev - [Oracle's OpenJDK Bans Generative AI Contributions While Oracle's GraalVM Allows Them](https://daily.dev/posts/oracle-s-openjdk-bans-generative-ai-contributions-while-oracle-s-graalvm-allows-them-mhc6rcp78) · InfoQ · 4 upvotes · 0 comments - [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 --- Tags: [#open-source](https://daily.dev/tags/open-source), [#java](https://daily.dev/tags/java), [#ai-coding](https://daily.dev/tags/ai-coding), [#oracle](https://daily.dev/tags/oracle) [View this post on daily.dev](https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj) ```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":"Oracle just banned AI-generated code","url":"https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj"},"datePublished":"2026-08-20T09:17:57.968Z","dateModified":"2026-09-14T08:37:14.022Z","description":"Oracle has banned contributing AI-generated content to OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images—while...","image":"https://i.ytimg.com/vi/sxyYoNNTpU8/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/sxyYoNNTpU8/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Awesome","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":"Awesome","logo":"https://media.daily.dev/image/upload/s--mj_0cdD8--/f_auto/v1710506099/logos/awesome-coding","url":"https://daily.dev/sources/awesome-coding"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":11},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,java,ai-coding,oracle","timeRequired":"PT8M","video":{"@type":"VideoObject","name":"Oracle just banned AI-generated code","description":"Oracle has banned contributing AI-generated content to OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images—while...","thumbnailUrl":"https://i.ytimg.com/vi/sxyYoNNTpU8/sddefault.jpg","uploadDate":"2026-08-20T09:17:57.968Z","duration":"PT8M","url":"https://api.daily.dev/r/wJ3LH7DBJ","embedUrl":"https://www.youtube.com/embed/sxyYoNNTpU8"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Awesome","item":"https://daily.dev/sources/awesome-coding"},{"@type":"ListItem","position":3,"name":"Oracle just banned AI-generated code"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/oracle-just-banned-ai-generated-code-wj3lh7dbj#faq","mainEntity":[{"@type":"Question","name":"What is Oracle's new policy on AI-generated code contributions to OpenJDK?","acceptedAnswer":{"@type":"Answer","text":"Oracle bans contributing AI-generated output back into OpenJDK, covering source code, pull requests, emails, wiki pages, bug reports, text, and images. Contributors may still privately use LLMs to understand the codebase, debug problems, review code, and do research, but cannot submit AI-generated output as a contribution. Oracle cites reviewer workload, safety and security, and intellectual property concerns as the reasons. Developers weighing AI contribution rules across ecosystems can track policy shifts like this one on daily.dev."}},{"@type":"Question","name":"How does Rust's AI contribution policy differ from a full ban?","acceptedAnswer":{"@type":"Answer","text":"Since August 5th, several Rust teams allow private AI usage but generally ban AI-generated documentation, diagnostics, and comments. AI-generated code can be accepted only under an experimental process that requires disclosure, prior arrangement with a reviewer, non-critical scope, proper testing, and full understanding by both author and reviewer. Anyone deciding how to use AI safely in a codebase can follow how projects like Rust set contribution guardrails on daily.dev."}},{"@type":"Question","name":"What does the Linux kernel require for AI-generated code and AI-discovered bug contributions?","acceptedAnswer":{"@type":"Answer","text":"Linux kernel documentation requires that AI-generated code be reviewed by the human submitter, who must ensure licensing compliance, test the fix, and take full responsibility for the contribution. For AI-discovered bugs, agents must reproduce the problem, produce a fix, build it, test it, and disclose anything they could not verify. Maintainers weighing AI-assisted bug fixes against accountability requirements can follow policy details like these on daily.dev."}}]} ```