AI Regulation Tracker / Litigation
xAI sues Minnesota's attorney general to block the state nudification law before August 1
A complaint is not a ruling. xAI filed one on July 27, 2026 against Attorney General Keith Ellison in his official capacity, asking a federal court to stop HF 1606 five days before it takes effect. No court has decided anything, and no injunction has issued.
What was actually filed, and what it is not
xAI filed a civil complaint. That is the opening pleading in a lawsuit. It sets out what the plaintiff wants and why it says it is entitled to it. It has no legal effect on the statute it attacks.
This matters more than usual here because of the calendar. The complaint went in on July 27, 2026. HF 1606 takes effect on August 1, 2026. Five days. A filing does not pause a statute, and nothing on the public docket as of July 28 indicates that a court has entered any order. If you are advising a company that serves Minnesota users, the operating assumption this week is that the law applies on August 1.
The tracker covers the statute itself separately. This entry covers the challenge to it.
What does the complaint allege about HF 1606?
The pleading opens with its own framing of the case. Quoting paragraph 1:
This suit challenges House File 1606 ('HF 1606'), a Minnesota statute that imposes an overbroad, content-based ban on free speech and the tools of visual expression in a clumsy attempt to prohibit 'nudification.'Complaint, X.AI LLC v. Ellison, No. 0:26-cv-03425 (D. Minn.), Doc. 1 at para. 1
Read that as advocacy, because that is what it is. Overbreadth and content-based discrimination are the two doctrinal hooks a plaintiff reaches for when it wants strict scrutiny applied to a speech regulation. Pleading them is not the same as establishing them. The state has not yet answered, and the Attorney General's office had issued no responsive statement as of publication.
The complaint also puts a number and a business consequence on the record. This is xAI's characterization, not a court finding. Again quoting the filing:
Confronted with $500,000-per-image strict liability and no safe harbor, xAI has no practical choice but to restrict Grok Imagine's image-editing features in various ways when the statute takes effect on August 1, 2026.Complaint, Doc. 1
Two things are being asserted there at once. One is a legal characterisation of the statute: strict liability, per image, no safe harbor for a general-purpose tool. The other is a factual assertion about the plaintiff's own conduct, that it will restrict features rather than accept the exposure. The second is the sort of allegation that supports standing in a pre-enforcement case. Neither has been tested.
According to the complaint, the statute contains no knowledge or intent element. That is xAI's reading. Anyone building a compliance position on it should read Minn. Stat. section 325E.91 directly rather than take the plaintiff's summary as the text.
Who is affected before August 1?
The exposed population is wider than xAI. It covers providers of general-purpose AI image and video generation and editing tools reachable by Minnesota users, whether or not the provider has any presence in the state, and it covers Minnesota users of those tools. It also reaches the drafters of the parallel nudification statutes other states have passed, because a ruling either way here becomes the first data point on how those statutes fare against a platform-brought First Amendment challenge.
For trust and safety teams the near-term question is not who wins. It is what your product does on August 1 if nothing has changed. xAI has told a federal court in writing that its answer is to restrict image-editing features. That is one provider's disclosed choice, not a benchmark anyone else is obliged to match.
What is alleged, and what is established?
The single most useful thing to hold in mind this week is the difference between the two columns below. Everything in the middle column comes from a pleading filed by one party. Nothing in it has been tested, answered or ruled on.
| Point | What xAI alleges in the complaint | Status on the record as of July 28, 2026 |
|---|---|---|
| Character of the statute | An overbroad, content-based ban on speech and on the tools of visual expression (para. 1) | No court has characterised HF 1606. The Attorney General has not answered. |
| Liability standard | Strict liability at $500,000 per image, with no safe harbor | Untested. It is the plaintiff's reading of Minn. Stat. section 325E.91, not a judicial construction of it. |
| Knowledge or intent element | None, according to the complaint | Untested. Read the statutory text directly before relying on this. |
| xAI's stated response | It will restrict Grok Imagine image-editing features when the statute takes effect | A disclosed intention in a pleading. It supports standing; it is not a finding and binds no other provider. |
| Effect of the filing | Declaratory and injunctive relief sought against enforcement | No ruling. No injunction. HF 1606 takes effect August 1, 2026 absent a court order. |
A complaint is a request, and the calendar does not wait for it. Anyone telling you the constitutional question is settled in either direction is ahead of the record.
What should platform counsel do this week?
Plan for the statute to be in force on August 1 and treat any injunction as upside. That is the only posture that does not require predicting a ruling.
Watch the docket, not the press. The two filings that would change the answer are a motion for a temporary restraining order or preliminary injunction, and the court's order on it. Both appear on the public docket for No. 0:26-cv-03425. A TRO can issue quickly, sometimes within days, which is presumably the point of filing on July 27 rather than in August. It can also not issue at all.
Keep the statutory question separate from the litigation question. Whether HF 1606 reaches your product turns on the statutory text and your feature set. Whether it gets enforced against you next month turns on the docket. And if you are geofencing or restricting features, record the decision and its date, because in a strict-liability posture the date you turned something off is the fact that matters.
What has not been decided
All of it. No court has held that HF 1606 is content-based. No court has held that it is valid. No court has assessed whether the $500,000-per-image figure or the absence of a safe harbor accurately describes the statute. The Attorney General has not filed a response. There is no ruling on standing, on ripeness, or on the merits. A well-resourced plaintiff has raised a serious constitutional question about a statute that takes effect in days, and the question is open.
Frequently asked questions
Has a court blocked Minnesota's HF 1606?
No. As of July 28, 2026 no court has ruled and no injunction has issued in X.AI LLC v. Ellison, No. 0:26-cv-03425 (D. Minn.). The complaint was filed on July 27, 2026. Absent an order from the court, HF 1606 takes effect on August 1, 2026 on schedule.
What does xAI's complaint actually argue?
The complaint pleads that HF 1606 is a content-based restriction on speech. It states at paragraph 1 that the statute 'imposes an overbroad, content-based ban on free speech and the tools of visual expression in a clumsy attempt to prohibit nudification.' These are allegations in a pleading, not findings by any court.
Where does the $500,000 per image figure come from?
It appears in xAI's own complaint, which alleges that 'confronted with $500,000-per-image strict liability and no safe harbor, xAI has no practical choice but to restrict Grok Imagine's image-editing features in various ways when the statute takes effect on August 1, 2026.' Treat both the exposure figure and the absence of a safe harbor as the plaintiff's characterisation until a court or the statutory text is independently checked.
Why is the Minnesota Attorney General the named defendant?
Keith Ellison is sued in his official capacity as Attorney General of Minnesota because a pre-enforcement challenge is brought against the officer who would enforce the statute. Naming the enforcing officer in his official capacity is the ordinary posture for this kind of suit and says nothing about him personally.
What should a platform watch for on the docket?
A motion for a temporary restraining order or preliminary injunction and any ruling on it. The docket is public at CourtListener under X.AI LLC v. Ellison, No. 0:26-cv-03425 (D. Minn.). If nothing issues before August 1, 2026, the statute applies on that date.
Last verified: July 28, 2026