State-by-State AI Non-Compete Enforcement: there is no single national answer, and state law is the first gate. Upload notices, contracts, reports or court papers to Caira and turn them into a document checklist.
Open Caira
Current-law note: reviewed against current official-source posture for the 2026 refresh.
Current Federal Posture
Do not treat a federal FTC non-compete ban as the controlling rule for 2026 planning. The safer analysis starts with state law, then the contract text, then the worker's actual role. Federal antitrust, trade-secret and unfair-competition issues can still matter, but ordinary enforceability usually turns on state statutes and state courts.
States To Separate First
California: employee non-competes are generally void, and California also resists attempts to route California workers around that policy through contract drafting.
Massachusetts: non-competes are possible only under detailed statutory conditions, including notice and garden-leave or other agreed consideration concepts; do not reduce the rule to a simple income threshold.
Washington, Colorado, Illinois, Oregon and similar reform states: salary thresholds, notice rules, duration limits or worker categories may matter and should be checked against current statutes.
New York, Texas, Florida and Delaware: enforceability can be more fact-specific, with reasonableness and protectable-interest analysis doing much of the work.
Why AI Makes State Tables Harder
AI workers often have remote-work histories, equity grants, invention-assignment documents, cross-border teams and confidential model or data exposure. One agreement may select Delaware or New York law while the employee lives in California or Washington. That mismatch should be flagged before anyone assumes the clause is enforceable or void.
Document Checklist
employment agreement and all restrictive covenant amendments
state of residence and work locations when each agreement was signed
offer, promotion, equity and severance documents
job duties, product area and confidential-information exposure
new employer role, team and competitive overlap
Red Flags
a clause that bans all AI, machine learning or cloud work without product limits
a governing-law clause that conflicts with the worker's actual state connection
a non-solicit or confidentiality clause being used as a disguised non-compete
a separation agreement adding new restrictions without clear consideration
no clean onboarding plan for a hire from a direct AI competitor
How To Use Caira
Upload the agreement, role descriptions and state facts. Ask Caira to split the document into covenant type, state-law issue, factual overlap, confidential-information issue and practical next step. That creates a useful checklist before escalation.
This guide is general information, not legal, financial, medical or tax advice.
