No AI Fridays is a weekly pledge, mostly among software teams, to turn off AI coding assistants and chatbots for one full workday. The idea started as a small pledge site built by an engineer at htmx and spread through Hacker News in August 2026, built on the argument that constant AI use is quietly costing developers the skills and focus they used to rely on.
Short answer: No AI Fridays means picking one weekday to turn off AI coding assistants and chatbots, then doing the work by hand — writing code without Copilot, reading docs instead of asking ChatGPT. It's a voluntary practice, not a product, started by an htmx engineer in 2026, and costs nothing to try for a single day.
I tried a version of this myself before writing this guide: one full Friday with GitHub Copilot disabled in my editor, ChatGPT and Claude tabs closed, and a self-imposed rule that if I got stuck I had to open the official docs, not a chat window. It was slower, and I noticed how often my hand moved toward the Copilot shortcut out of pure habit before catching itself. Below is what the practice actually is, how to run your own version of it, and what the research it leans on does and doesn't prove.
What No AI Fridays actually is
The site behind the name, noaifridays.com, was built by an engineer who goes by "xendo" online (X handle @lazilyevaluated), who has described it as COO of htmx — the small library behind the htmx web framework. He's said openly, in the Hacker News thread where the idea picked up traction, that part of the motivation was convincing his own team (which is to say, himself) to actually do it. As of this writing, htmx is the only company listed on the site as having adopted the practice, though the page invites other teams to request to be added.
The rules on the pledge page are short: disable your AI assistant for one day a week, write code manually, read documentation instead of asking a chatbot, and work through problems yourself. Tools that only give feedback on work you already did by hand — a linter or a code-review bot, for instance — are still fair game. It's meant to be a light, repeatable habit, not a strict detox. For people who want a bigger version of the same idea, No-AI December applies the same logic to an entire month and covers any generative AI tool, not just coding assistants.
What you'll need before you try it
Nothing to buy and nothing to install. You need a day you can actually protect — most people pick a lighter day, which is part of why "Friday" is in the name — and a clear sense of which tools count as AI. That's a longer list than most people expect: Copilot or Cursor's AI completions, ChatGPT or Claude in a browser tab, an AI code-review bot, and increasingly, AI features baked into your IDE by default. If you work on a team, tell people the day before, so nobody's blocked waiting on a code review from you that would normally take ten minutes. If you manage or work with a team, my guide to how to disable or avoid intrusive AI covers turning off the ambient AI features (in Gmail, in Windows, in your browser) that keep resurfacing even after you've closed the obvious tabs.
Step-by-step: running a No AI Fridays experiment
1. Pick one day and put it on the calendar
Don't leave it as a vague intention. Block the day, and if you work with others, say so in your team channel the day before — "no AI tomorrow, replies might be slower" — so nobody assumes you're ignoring them.
2. Turn off every AI surface, not just the obvious one
Disabling Copilot in your editor is the easy part. Also close ChatGPT and Claude tabs, turn off AI code review bots for your PRs that day, and check whether your IDE has an ambient AI feature (inline suggestions, an AI chat panel) that's on by default. In my testing, the browser tabs were the easy part to remember — the inline editor suggestions were what I kept forgetting to disable.
3. Keep a running note of what you reach for
Every time you catch yourself about to ask an AI something, jot it down instead of doing it. By the end of the day you'll have a real list of what you actually lean on AI for, which is more useful than a vague sense that "I use it a lot."
4. Swap in the manual equivalent
For a coding question, that's official documentation, a search engine, or a colleague, in that order. For debugging, it's reading the stack trace and setting a breakpoint instead of pasting the error into a chat window. My guide on AI coding without the vibes covers what disciplined manual debugging looks like if AI-assisted debugging is the habit you're trying to break.
5. Debrief once the day is over
Look at your list from step 3. Some items will be genuinely faster with AI and not worth avoiding long-term — boilerplate, for instance. Others will reveal a skill you've let slide, which is the more useful finding.
6. Decide whether to repeat it
Some people who try it once don't keep it up; others make it a fixed weekly habit. Both are legitimate outcomes — the point of the exercise is the data from your one day, not obligation to continue.
Rules and messages you can copy
- Team Slack message: "Trying a No AI Fridays experiment tomorrow — no Copilot, no ChatGPT, docs and manual debugging only. PR reviews and answers might be a little slower than usual. Back to normal Monday."
- Personal pledge, pinned somewhere visible: "Every Friday: AI coding assistant off, chat tools closed, docs and manual debugging only. Linters and static analysis still allowed."
- PR description note, if a review runs slower than usual: "Written and reviewed without AI assistance today as part of a No AI Fridays trial — flag anything that reads unusually verbose or slow."
Common mistakes to avoid
The biggest one, in my own attempt, was forgetting an AI surface I didn't think of as "AI" — inline editor suggestions especially, since they're on by default and don't announce themselves the way a chat window does. The second is picking a day with a hard deadline; the whole point is a lower-stakes day where being slower doesn't cost you anything real. Third, people treat one Friday as proof of something — either that they don't need AI at all, or that they can't function without it — when one data point from one day tells you less than it feels like it does. And fourth, teams sometimes spring it on people without warning, which just creates friction instead of insight; say something the day before, the way the sample Slack message above does.
Does it actually work? What the research and the pushback say
The strongest piece of research the practice leans on is a MIT Media Lab study published June 10, 2025, which used EEG to compare people writing essays with an LLM, with a search engine, or with neither. Across four months and 54 participants in the main phase, the group using an LLM showed the weakest brain connectivity of the three and "consistently underperformed at neural, linguistic, and behavioral levels," per the study's own summary. It's a real, specific finding — but it's a single, not-yet-peer-reviewed study on essay writing, not coding, and a similar concern about skill erosion shows up in a Stanford-linked study on AI-boosted homework scores followed by lower exam scores, a pattern I've also seen argued for professional coding skill in my piece on why coding expertise may collapse from AI reliance.
The pushback is just as real. On the Hacker News thread where No AI Fridays picked up attention, one developer pushed back hard, saying AI tools let them ship "10-20x" what they could before, and questioned whether the cited research proves causation rather than correlation. That's a fair objection — cognitive-debt research so far is small-sample and specific to writing tasks, not a settled verdict on all AI-assisted work.
| Approach | Commitment | Best for | Where to start |
|---|---|---|---|
| No AI Fridays | One day a week | Developers who want a low-stakes, recurring check-in | noaifridays.com |
| No-AI December | One full month, any generative AI | Anyone reassessing AI use broadly, not just coding | noaidecember.com |
| Ad hoc breaks | No fixed schedule | People who'd rather notice AI reliance case by case | Keep the running note from step 3 above, no pledge needed |
Tools that make this easier
If your team decides No AI Fridays isn't for you but you still want to use AI coding tools well instead of by default, my AI coding assistant guide covers picking one deliberately rather than defaulting to whatever your editor ships with. For evaluating whether a specific AI tool's claims hold up before you build a habit around it, AI tool ratings explains how to read vendor claims skeptically. And if the skill you're most worried about losing isn't coding but something you're actively trying to learn, my guide to how to use ChatGPT for learning covers using AI deliberately as a tutor rather than a crutch, which is closer to the middle ground most people land on after a few weeks of trying something like this.
My take
No AI Fridays is a small, low-cost experiment dressed up as a movement — one engineer's pledge page, one company (his own) currently listed as doing it. That's not a knock on the idea itself. In my one day of trying it, the value wasn't some dramatic productivity finding; it was the list of moments where I reached for AI out of habit rather than need. Whether the research behind it (a single, not-yet-peer-reviewed study) proves what its advocates claim is genuinely contested, and the Hacker News pushback about real productivity gains is worth taking seriously too. Try it for one Friday before deciding whether it's worth a standing weekly habit — you'll learn more from your own list than from the debate about whose study is right.
Frequently Asked Questions
Is No AI Fridays free?
Yes. It's a self-imposed rule, not a product or subscription — there's nothing to buy, download, or sign up for beyond reading the pledge on noaifridays.com if you want to add your team to the list.
How long does it take to see a difference?
One day is enough to produce a useful list of what you reach for AI to do, which is the actual point of the exercise. Whether it changes a skill you've let slide takes longer — closer to several weeks of repeating it, based on how similar habit-change practices like No-AI December are usually run.
What's the easiest way to start?
Pick a lower-stakes day, tell your team the day before using a message like the one above, and turn off every AI surface you can find — not just the obvious chat window, but inline editor suggestions and AI code review bots too.
Who created No AI Fridays, and is any major company doing it?
An engineer who posts as "xendo" (@lazilyevaluated on X), who has described himself as COO of htmx, built the pledge site. As of this writing, htmx is the only company listed as having formally adopted it, though the site invites others to request to be added.
Does the research actually prove AI use hurts your skills?
Not conclusively. The MIT Media Lab study most often cited found real differences in brain connectivity between LLM users, search-engine users, and unaided writers, but it's a single, not-yet-peer-reviewed study focused on essay writing, not a broad verdict on all AI-assisted work — a limitation critics raised directly in the Hacker News discussion of the idea.