Frequently Asked Questions

AI-Generated Code & Ownership

Do I own the code an AI tool generates for me?
Most AI vendors’ terms assign you whatever rights exist in the output. The problem is what exists: under current U.S. copyright law, output from purely generative AI lacks a human author and therefore cannot be copyrighted. You may hold the code, but there may be no copyright in it to own.
Does writing detailed prompts make me the author?
Prompts are instructions, and the model decides how to carry them out. The Copyright Office has said that a prompt alone does not give the user enough control over the resulting expression to make them the author, however detailed the prompt is.
Can I copyright AI-generated code?
Only the portions created or significantly modified by a human author qualify. Pure AI output cannot be copyrighted.
But I paid for it. Doesn't that make it mine?
No. Payment is irrelevant to copyright ownership. Ownership follows authorship: work created by an employee within the scope of employment belongs to the employer as a work made for hire, and anyone else who writes code keeps the copyright unless they sign a written assignment. The development shop you pay $250,000 to build your application still owns the copyright in that code unless the contract assigns it to you in writing, and the same is true of a freelancer you pay by the hour. AI-generated code adds a second problem: there is no author at all, so there is no copyright for anyone to assign to you, no matter what you paid for the tool or the prompts.
Can I monetize AI-generated code even if I don't own it?
Yes, but ownership uncertainty significantly increases risk in licensing, fundraising, enforcement, and exits. Without clear ownership, you cannot create or defend a lawful monopoly over your software, allowing competitors to copy it with impunity and leaving the company with revenue but no defensible asset to protect or sell.
If I don't own the AI-generated code, could someone else?
Possibly. AI models occasionally reproduce code from their training data, sometimes verbatim, sometimes with the license notice stripped. If that code lands in your product, the original author still owns it, and your product infringes as to that portion. If the source was under a copyleft license such as the GPL, the author may demand that you release your own code to comply. So the ownership question cuts both ways: you cannot claim what the model wrote, and you cannot be sure nobody else can. The same missing provenance causes both problems. Vendor indemnities (Microsoft, Google, OpenAI, Anthropic) cover some of this risk, but typically only on paid or enterprise tiers with duplicate-detection filters turned on. Scan AI output the way you already scan open-source dependencies.

Vibe Coding & AI Assistance

What is “vibe coding”?
“Vibe coding” refers to prompting an AI to generate large amounts of functional code with minimal human design, structure, or revision.
Why is vibe coding risky from an ownership perspective?
Because the AI, not the human, is doing the expressive work. Under current law, vibe-coded output is not human-authored and therefore not a legally protectable asset.
Is an AI prompt processed by a large language model equivalent to source code compiled by a traditional compiler?
No. A compiler transforms source code a human wrote into another form without adding expression of its own, so the chain of human authorship is preserved. A language model generates new expression in response to a prompt. Whether or not that output is repeatable, the expressive choices were the model’s, which breaks the chain of human authorship that copyright protection requires.
What if we set the temperature to zero? Does deterministic output mean we can own the code?

No. Temperature is a sampling setting that controls how much randomness the model uses when it picks each next token. At zero, the model takes (or nearly takes) its highest-probability choice every time, so repeated runs of the same prompt produce the same or nearly the same output. It does not change what the model knows or how it decides what is probable. Even zero is not truly deterministic in practice: floating-point differences across GPUs, request batching, infrastructure changes, and model updates mean identical prompts can still drift, and vendors do not guarantee bit-identical output. Most coding assistants, including Copilot, Cursor, and Claude Code, do not expose temperature at all; the vendor sets it internally and can change it at any time.

The real answer is that repeatability is not the legal test. Copyright requires a human author, meaning a human who made the expressive choices in the work. Thaler v. Perlmutter confirms that a human author is required, and the Copyright Office’s January 2025 report on copyrightability frames the question as whether the human controlled the expression, not whether the machine’s output can be reproduced. A model at temperature zero still decides every variable name, structure, algorithm, and line of code. The human supplied a request, and the model supplied the expression. Making the model’s choices repeatable does not make them the human’s choices. The compiler comparison makes the same point. A compiler is deterministic, and it preserves human expression: the developer wrote the source, and the compiler transforms it without adding expression of its own. A language model at temperature zero is (mostly) repeatable, but it generates new expression the human did not write. Determinism was never what made compiled code ownable; human-authored source was.

In fact, determinism cuts the wrong way. If the same prompt at temperature zero yields the same code for anyone who types it, that is evidence the prompt is an idea or instruction and the code is the model’s standard answer to it, not anyone’s original expression. Two developers at two companies could hold identical code, and neither would have authored it. The tool setting is irrelevant to ownership. What matters is documented human design, selection, and revision of the code, and the provenance records that prove it (see “How much human input is ‘enough’?” below).

Human Authorship & Mixed Codebases

If I edit or refine AI output, do I become the author?
Possibly. Meaningful human revision, selection, restructuring, or creative judgment may establish authorship.
How much human input is “enough”?
There is no bright-line rule. The U.S. Copyright Office makes this determination initially at registration, and its refusals can be challenged in court, which is precisely what cases like Allen v. Perlmutter are testing. Courts look for creative contribution and judgment, not just the volume of edits. In practice, the issue is typically resolved only if and when authorship is tested in litigation, where prompt history, revision records, and other AI usage artifacts may be examined or compelled through discovery or subpoena. Because this analysis is highly fact-specific, our workshops cover how to evaluate authorship risk before it is tested in court.
Does refactoring or rewriting AI code make it mine?
Not automatically. Deterministic or mechanical changes (such as simple transcription or formatting) are insufficient. Authorship may arise only where refactoring reflects independent creative decisions.
Can I fix it by having a human retype the AI output, or by publishing it?
No. Retyping, re-entering, reformatting, or running AI output through another tool is mechanical work, not creative judgment, so the result is still the AI’s expression with no human author. Publishing it does not help either: posting code to GitHub, a website, or social media fixes it in a tangible medium, but fixation only creates a copyright when a human authored what was fixed. Laundering the output through a person or a platform does not solve the authorship problem. Publishing it does not make it open source or public domain in the usual sense either; see “If nobody owns it, is AI-generated code public domain? Open source? What do we call it?” below.
Can I combine AI-generated and human-written code and own all of it?
You own what you create. AI-generated portions remain unowned unless replaced or transformed through human authorship.

Open Source, Licensing & Compliance

Can I apply MIT, GPL, or other licenses to AI-generated code?
Applying an open-source license requires copyright ownership. Because pure AI output has no copyright holder, any open-source license applied to that portion would be unenforceable as a copyright license, because there is no copyright to license; at most its terms might operate as a contract with those who accept it.
If nobody owns it, is AI-generated code public domain? Open source? What do we call it?
Call it unowned, or if you want the legal term, uncopyrightable. It is not open source, because open source is a license and a license needs an owner to grant it. “Public domain” is technically defensible, since the public domain includes material that was never eligible for copyright, but the phrase misleads: people hear “free and clear,” and AI output is neither. It may still contain someone else’s copyrighted code, it can still be a trade secret, and a contract can still restrict it. Dedications like CC0 or the Unlicense do not help either; they are tools for waiving rights you hold, and here you hold none. Human code is copyrighted, then licensed. Pure AI code is just unowned.
What if AI generates code similar to open-source material?
Similarity can still trigger licensing obligations or infringement risk, especially with copyleft licenses, and can retroactively undermine your IP position, turning what you believed was proprietary software into an enforceable obligation to share it. These issues often surface late and are expensive to unwind; identifying open-source exposure before audits or exits is a core topic in our workshops.
Can derivative works based on publicly available code be copyrighted?
Yes, but only the new, human-created portions qualify for protection, and the underlying code’s license still governs your use of it. This principle long predates AI, and AI does not change the rule. It only makes violations easier to create and harder to detect.
Can I use an AI agent to recreate someone else's software?
Not without permission. Pointing an AI agent at another company’s product and telling it to recreate that product is copying, and the person who directs the agent is responsible for the result. The agent is a tool, not a defendant. What the agent was given matters. If it worked from decompiled or leaked source, the output is a derivative of that code, and the reverse engineering exceptions in Sega v. Accolade and Sony v. Connectix cover interoperability, not building a substitute. If it worked only from the running product, the underlying mechanics and ideas are not protected, but the specific expression is, including code structure, artwork, audio, characters, and look and feel, as Tetris Holding v. Xio Interactive illustrates. The result is a double bind: the AI-written portions have no human author, so you cannot own them, while any portion that reproduces the original’s expression exposes you to an infringement claim. You end up holding code you cannot protect and may not be allowed to ship. “It was only an experiment” and “I will never monetize it” may affect a fair use analysis or damages, but they do not make the claim go away.
Does AI usage violate open-source terms?
Not inherently, but unmanaged mixing of sources can silently violate open-source obligations, forcing disclosure or redistribution of proprietary code and surfacing only when an audit, lawsuit, or acquisition makes the problem impossible to ignore.

Employment, Contractors & Work-for-Hire

If an employee uses AI, does the company own the code?
The company owns the human-authored portions via work-for-hire, but it cannot assert ownership over purely AI-generated sections. As a result, parts of a company’s core product may be legally unowned and unenforceable, creating ownership gaps that often surface only during litigation, audits, or an attempted exit.
What if a contractor uses AI to deliver code?
Ownership of AI-generated portions may not transfer unless contracts explicitly address AI usage, authorship, and IP allocation. This can leave critical components of your software legally outside the company’s control, with no clear right to enforce, license, or transfer, issues that are often discovered only during diligence or dispute. Our workshops cover how to structure these agreements before the gaps become irreversible.
Our development contract says we own everything the vendor delivers. Aren't we covered?
Not necessarily. An assignment clause can only transfer rights that exist. Under current U.S. law, code generated by AI without meaningful human authorship has no copyright to assign, so the clause transfers the files but not the exclusive right to stop others from copying them. Ask vendors to disclose how deliverables were produced, warrant the extent of human authorship, and retain the provenance records that would let you prove it in diligence or litigation.
Should contracts address AI usage?
Yes. Modern agreements should clearly define permitted AI use, authorship expectations, ownership, and documentation requirements. These provisions are best developed with an experienced IP attorney who knows which questions to ask, rather than relying on AI-generated contract language that may omit or misallocate critical rights, often discovered only after a dispute arises.

Contracts, Warranties & Insurance

Can I sign a customer contract warranting that I own the code?
Nearly every software license contains a warranty of title: the licensor represents that it has good right, title, and interest in the software sufficient to grant the license. If part of your product is purely AI-generated, you cannot truthfully give that warranty for that part. Signing anyway does not make the problem go away; it converts an ownership gap into a misrepresentation and a breach of contract waiting to be discovered. Government contracts typically add an accuracy warranty on top of that.
What about warranting accuracy or indemnifying my customers?
Sophisticated customers will not license software without indemnification: if they get sued for using your code, you defend them. They will also ask you to warrant that the deliverables are accurate and fit for purpose. With AI-generated code whose provenance you cannot trace, you are underwriting infringement and accuracy risk you cannot see. Many companies sign these clauses anyway because “everyone does it,” which is exactly how the exposure stays hidden until a claim arrives.
Will my AI vendor indemnify me if I get sued over its output?
Read the terms. Consumer and individual plans generally disclaim liability for what the model produces. Some enterprise and business tiers now offer limited copyright indemnities, usually conditioned on using the paid plan, leaving the vendor’s safety filters on, not modifying the output, and other requirements. Even where it exists, vendor indemnity covers a lawsuit; it does not make the output yours, and it does not satisfy a customer’s warranty of title. The assessment asks about your tool tier for this reason.
Could prompting an AI tool violate my NDAs?
Yes. Most companies are party to far more confidentiality agreements than anyone can keep in their head, and pasting a counterparty’s confidential information, or your own trade secrets, into an AI tool can breach those agreements and can jeopardize trade-secret status. Consumer tools may also use inputs for training. A written prompting policy that says what may and may not go into an AI tool is a basic control, and the assessment asks whether you have one.
Does my liability insurance cover AI-related claims?
Maybe not. General liability, E&O, and cyber policies increasingly carry explicit AI exclusions, and they tend to sit deep in the exclusions section where no one reads them. Before you rely on coverage for an infringement, hallucination, or disclosure claim involving AI-generated code, read the exclusions and ask your broker directly.
Can I use my code as collateral for a loan?
Lenders routinely take a security interest in all of a borrower’s assets, including general intangibles such as copyrights and code, and the loan documents have you represent that you own them. If a material part of your codebase is unowned AI output, that representation is inaccurate, and when the lender finds out, you are in breach of your loan covenants.

Patents, Disclosure & Other Law

If copyright won't protect AI output, can I patent it instead?
Not if the AI did the inventing. In Thaler v. Vidal, the Federal Circuit held that an inventor under the Patent Act must be a natural person, and the Supreme Court declined to review that decision. USPTO guidance allows patents on AI-assisted inventions where a natural person contributed to the conception of the invention; an invention with no human inventive contribution is not patentable. Submitting an invention that an AI conceived, and naming a human as the inventor, risks invalidating the patent later. So for purely AI-generated work, copyright says no and patent says no. See the Resources page.
Can putting an invention into an AI prompt hurt my patent or trade-secret rights?
It can. You typically have no confidentiality agreement with the AI vendor, so describing an invention in a prompt may be treated as a disclosure outside your control. That can undermine trade-secret protection and, depending on the tool’s terms and the jurisdiction, may start the clock on patent filing deadlines. If an idea might be patentable, talk to patent counsel before describing it to an AI tool.
Do I have to disclose that I used AI?
Increasingly, yes. A growing body of law targets disclosure rather than prohibition: the EU AI Act’s transparency obligations, California’s AI Transparency Act, Utah’s AI Policy Act, and a growing number of other state laws, including several in Idaho. Most of these focus on consumer-facing AI content and interactions rather than internal code generation, but the direction is clear. Beyond legal obligations, buyers, investors, and customers are asking the question directly, and a product that cannot carry the normal warranties may need to disclose why.

Investment, Audits & Exit Strategy

Why do investors ask “Who owns the code?”
Clear ownership is required to enforce rights, defend against competitors, and justify valuation. Without legally enforceable ownership, an investor is being asked to fund a business whose core asset may not be protectable, transferable, or owned at all.
Does AI-generated code reduce valuation?
It can. Unowned or unenforceable assets weaken competitive barriers and increase diligence risk. Investors routinely reduce valuation or abandon transactions when a company cannot demonstrate clear ownership of its core technology.
What must I disclose during due diligence?
AI usage, code provenance, and where demonstrable human authorship exists. Undisclosed or poorly documented AI involvement often surfaces during diligence, triggering valuation reductions, indemnities, escrow holdbacks, or transaction termination, each of which can carry significant monetary consequences. In the event of a dispute, these disclosures may be examined under oath and compared against actual prompt history and other contemporaneous records, including those compelled through discovery or subpoena.
How do I prepare for an audit of AI-generated software?
Maintain prompts, revision history, commit logs, design documents, and evidence of human decision-making. Audit preparation is often where undocumented AI usage is first uncovered. Building defensible documentation practices before diligence begins is covered in depth in our workshops.
If customers are paying us, why does ownership still matter?
Revenue does not create ownership. Without enforceable intellectual property rights, you do not possess a lawful monopoly over your software, meaning competitors may legally copy it without consequence. Customer payments confer no exclusivity, no barrier to entry, and no defense against replication. First-mover advantage is temporary; only ownership creates durable control, defensible value, and an asset that can be enforced, licensed, or sold. Without it, revenue exists, but the company does not own what it is selling.

Risk Management & Development Best Practices

Isn't copyright irrelevant now that anyone can regenerate the code with AI?
No. Copyright still gives a software company four things nothing else does. A lawful monopoly: the right to stop others from copying and using your code, stronger in practice than patent protection for source code. Statutory damages and attorney’s fees: available in copyright cases if you registered on time, and in almost no other body of law. DMCA takedowns: the ability to have infringing code removed from GitHub or any other platform without a lawyer or a courtroom. International reach: the same protection in the more than 180 countries of the Berne Convention. Walk away from copyright because “it’s faster and cheaper to let the AI write it,” and you walk away from every tool you would use to stop downstream theft and to monetize the asset.
How do I actually protect the code my humans write?
Copyright exists the moment a human fixes the code in a tangible medium, but you cannot file an infringement suit in the U.S. for a U.S. work until the Copyright Office has actually issued a registration (the Supreme Court’s 2019 Fourth Estate decision confirmed an application alone is not enough), and you only get statutory damages and attorney’s fees if you registered before the infringement began or within three months of first publication. Registration costs about $65 per work. The practical rule: register human-authored code early, well before it ships, and keep the records (commit history, design documents, who wrote what) that prove a human authored it. A © notice is fine to include, but it is not registration; its main legal effect is to defeat an infringer’s claim of innocent infringement.
Can engineers still use AI safely?
Yes, when AI is used intentionally and with an understanding of ownership implications. AI should assist, not replace, human design, judgment, and authorship, particularly in critical code paths. Teams should adopt clear usage guidelines and maintain documentation showing meaningful human review and decision-making. When used this way, AI can accelerate development without undermining ownership or defensibility.
Where is the boundary between AI assistance and authorship?
There is no bright-line rule. Authorship exists when a human exercises independent creative judgment by conceptualizing the solution, selecting among alternatives, and structuring or materially rewriting the code in a non-trivial way. Courts evaluate authorship qualitatively, based on creative contribution rather than the amount of AI involvement. This analysis is highly fact-specific.
What risks arise if AI creates critical code paths?
Reliance on AI for critical functionality can result in code that is legally unowned or unenforceable, weakening your ability to exclude competitors or defend the software as a proprietary asset. This may increase exposure to infringement, open-source compliance, and diligence risk, often surfacing only during audits, litigation, or an attempted transaction.
How should teams document AI usage?
Documentation is critical to establishing ownership, defensibility, and audit readiness. Teams should retain records of AI prompts, generated outputs, revisions, and the human decisions that shaped the final code. This provenance supports compliance, valuation, and enforcement, and should be maintained with the expectation that it may be discoverable in litigation or subject to subpoena, just like email, chat logs, or source control history.

This FAQ reflects current U.S. copyright law. Other jurisdictions treat AI authorship differently, and nothing here should be assumed to apply outside the United States. Provided for educational purposes; not legal advice.