Your ADHD brain is bouncing between four open thoughts. Your autistic brain is locked on the one detail that did not parse cleanly. They are running simultaneously, in opposite directions, on the same brain.
You are in bed. The texture of the duvet is wrong tonight, you have noticed it eleven times. At the same time you are mentally re-reading a Slack message from your manager, drafting an email to your sister, wondering if you locked the front door, and trying to remember whether the word your friend used at dinner was "weird" or "wired." Your brain is doing all of these at once. None of them are finishing.
This pattern has a name people use for themselves. AuDHD stacked loops: two-engine overthinking where an ADHD-style scatter loop and an autistic-style perseveration loop run at the same time, on the same brain, on completely different tracks.
If you self-identify as AuDHD, this is probably a Tuesday.
so why does it feel like two brains arguing
Most overthinking advice assumes one engine. Either your brain is jumping (ADHD) or your brain is stuck (autistic perseveration). For a lot of people who identify as AuDHD, both are true, in the same minute, about different things.
The ADHD engine is described well in Russell Barkley's 1997 model of executive function in ADHD, which framed ADHD less as an attention problem and more as a problem of self-regulation: the brain has trouble inhibiting one signal so another can win. So four things stay open. The mental tabs do not close. You are not "distracted." You are running parallel processes with no garbage collector.
The autistic engine is described in literature on cognitive flexibility and set-shifting. Hill's 2004 review in Trends in Cognitive Sciences synthesized the executive function evidence in autism and named one consistent finding: autistic brains often have a harder time disengaging from a current frame to adopt a new one. So the one thing that did not parse cleanly stays loaded. The detail that was slightly off keeps requesting attention until it resolves.
You can probably see the problem. The first engine wants to keep four things open. The second engine wants to fully resolve the one thing that snagged. Neither engine wins. Neither engine quits. They run.
a few ways the stack actually shows up
You leave a meeting. The ADHD engine is already pulling you toward your next three tasks, your snack, and that email you forgot to send. At the same time the autistic engine is replaying the moment your manager said the word "concerning" with a half-second pause before it. The pause did not parse. So now you are mentally everywhere at once and also stuck on a 0.5-second piece of audio.
You are trying to fall asleep. The ADHD engine is opening tomorrow's calendar, last week's argument, a song lyric, and a regret from age 14. The autistic engine is locked on the fact that one of the lights in the kitchen has a slightly different color temperature than the others and you have not figured out why. You feel scattered and stuck simultaneously. Both descriptions are accurate.
You sent a text. The ADHD engine has already moved on to four other texts you owe people. The autistic engine is parsing the exact phrasing of the one you just sent, the punctuation, whether the word "fine" reads as fine or as Fine, whether the period at the end is normal-period or angry-period. You feel like you are flaking on five conversations and over-investing in one, at the same time. Because you are.
You are at a dinner. The ADHD engine is tracking three side conversations, the playlist, and whether you turned the oven off at home. The autistic engine is locked on a sentence someone said earlier that you cannot tell if was a joke. You leave feeling like you missed half the night and also dissected one minute of it for an hour.
If two of those felt specific, that is the stack.
what the clinical picture actually looks like (and what it does not)
A note before going further: AuDHD is identity language. People use it to describe themselves when they identify with both autistic and ADHD experience. It is not a clinical diagnosis someone hands you. The clinical literature uses phrases like "co-occurring autism and ADHD" or "ASD/ADHD comorbidity," which sound like a medical chart and read nothing like the inside of your head. Self-advocates pushed AuDHD into wider use because the lived experience is not "two separate diagnoses." It is one brain running two different operating systems at once.
The reason this feels like a single experience and not two stacked symptoms goes back to the engines. When the inhibition piece Barkley described and the set-shifting piece Hill described show up in the same brain, the result is not additive. It is recursive. The thing the autistic engine cannot let go of becomes one of the four things the ADHD engine keeps open. The four things the ADHD engine keeps open each contain a detail the autistic engine wants to fully resolve. So you get loops inside loops.
There is also a relational layer most one-engine frameworks miss. Damian Milton's 2012 paper in Disability and Society introduced what he called the double empathy problem: when autistic and non-autistic people communicate, the friction is mutual, not a one-sided autistic deficit. For AuDHD readers this matters because a huge chunk of what loads into the autistic engine is social ambiguity, the moments where someone said something and you genuinely cannot tell what they meant. That ambiguity is not because your brain is broken. It is what happens when two communication styles meet and neither side automatically translates. The autistic engine then tries to resolve it. The ADHD engine, meanwhile, has already moved on to the next four interactions, leaving the unresolved one running in the background.
You may have heard of rejection sensitive dysphoria, the intense emotional response many ADHD-identifying people describe to perceived criticism or rejection. In an AuDHD stack, RSD often becomes the fuel for the autistic engine: the unparsed social moment is also the threatening one, which makes it sticky in a particular way. Engine one keeps it open. Engine two keeps re-running it.
why "just stop overthinking" is a useless instruction here
Standard overthinking advice tends to come in two shapes. The first shape is "let it go," variations on cognitive defusion or distraction. That works on the ADHD engine sometimes; it does almost nothing for the autistic engine, because perseveration is not the same as worry. You cannot defuse a thing that has not finished parsing. The second shape is "fully process it," variations on journaling everything until the loop closes. That works on the autistic engine sometimes; it crashes the ADHD engine, because the ADHD engine cannot stay on one thing long enough to process it to completion.
Most apps in this space pick a side. Mood trackers and gratitude prompts push toward the "let it go" school. Long-form journaling prompts push toward the "fully process it" school. Neither acknowledges that an AuDHD brain is running both engines and needs different moves for each.
There is a traditional journaling problem for ADHD brains specifically that compounds when you stack the autistic engine on top: a blank page asks you to do executive function (sequencing, prioritizing, deciding what matters) on top of the thing you are already trying to process. For the ADHD engine that is too much overhead. For the autistic engine that is the wrong question, because the engine is not asking "what should I write about." It is asking "what is the precise shape of the thing that did not parse."
This is part of why a lot of AuDHD readers describe writing as helpful "until it isn't." The first ten minutes feel productive. Then the ADHD engine wanders, the autistic engine spirals on a single phrase you wrote three sentences ago, and you close the notebook feeling worse than when you opened it.
what writing or talking it out actually does (when it works)
When externalization works for an AuDHD brain, it is doing two specific jobs at once.
For the ADHD engine, externalization unloads working memory. James Pennebaker's four decades of expressive writing research at UT Austin showed that putting language to internal experience produces measurable psychological benefits across a wide range of populations and conditions. The mechanism most relevant to ADHD-style scatter is the offload: the four open tabs do not all need to stay loaded if some of them are written down somewhere your brain trusts to find them later. The tabs can close. The engine can run on fewer.
For the autistic engine, externalization names the shape of the thing that snagged. The unparsed detail wants to be parsed. Sometimes parsing it means resolving it; more often it means giving it a precise enough description that the engine can stop trying to fully resolve it and let it sit as a known unfinished thing. "I am stuck on whether the period at the end of her text was a normal-period or an angry-period" is more useful than "something feels off." The engine does not need closure. It needs accuracy.
Voice is interesting here because it sidesteps a piece of the executive function tax that written journaling charges you. You do not have to decide where to start. You do not have to spell. You do not have to sequence. You start talking, and both engines have somewhere to dump load. Some of what the ADHD engine is holding falls out. Some of what the autistic engine is parsing gets named.
This is the layer where you might want to learn more about Loop Mind. It was built around voice and around naming the pattern, not around prompts that assume one engine.
the stacked-loops version of "noticing"
You will not detangle the two engines in real time. You probably do not need to. What seems to help most AuDHD readers is something smaller: noticing which engine is loud at a given moment.
When the scatter engine is loud, the move that helps is offloading. Say or write the four things, in any order, badly. You are not journaling, you are dumping. The point is to close the tabs.
When the perseveration engine is loud, the move that helps is naming the snag with as much precision as you can. Not "I am being weird about this," but "I am stuck on the word 'concerning' and the half-second pause before it." The engine does not need you to fix it. It needs you to describe it accurately enough that it can stop asking you to.
When both are loud at the same time, which is most of the time, you alternate. A minute of dumping. A minute of naming. The goal is not silence. The goal is to be running the engines instead of being run by them.
For some AuDHD readers the stack will feel structurally similar to the ADHD hyperfixation/rumination pattern, where one thing locks the spotlight while everything else screams in the background. The stacked-loops frame is one specific flavor of that, and it sits inside the broader taxonomy of overthinking patterns Loop Mind uses to describe what brains do when they will not stop. If your nighttime version of this is more familiar than your daytime version, the ADHD-brain-at-night piece is the closest companion.
how loop mind thinks about this
Loop Mind is a voice-first journaling app for chronic overthinkers. It was not built for autism or ADHD specifically, and it is not a treatment for either. What it does, that seems to land for AuDHD users, is two things: it lets you talk instead of write, which lowers the executive function tax both engines are charged; and it tries to name the pattern in your speech back to you, so the autistic engine has something accurate to point at and the ADHD engine has something concrete to close.
Your brain is not broken. It is running two engines that were not designed to run together, and the result is a particular kind of loud. Naming the engines does not make them quiet. It makes them visible.
If any of this felt specific, download Loop Mind to get started and see what your brain is doing while it is doing it. Or learn more about Loop Mind first.
