How AI Helps Me Manage Life with ADHD

Bugz June 2026 BugzCloud.xyz

I was diagnosed with ADHD when I was nine, which means I’ve spent most of my life knowing my brain works differently. Knowing it and figuring out how to actually work with it are two different things though. For a long time I was just bad at finishing things, bad at remembering stuff, bad at sitting down and doing the thing I needed to do even when I genuinely wanted to. Eventually I started actually looking for tools that worked with my brain instead of against it

AI ended up being one of those tools. Not because it fixed anything — it didn’t — but because it quietly removed a handful of friction points that were making everything harder than it needed to be. This is just my experience. Your mileage will vary. But if you’ve got ADHD and you haven’t experimented with AI yet, here’s what it actually does for me day to day.

Starting Is the Hardest Part

There’s a specific kind of paralysis that comes with ADHD where you know what needs to get done, you want to do it, and you still can’t make yourself start. It’s not laziness. It’s more like your brain hits a wall and won’t budge. I used to just sit there feeling terrible about it.

What AI changed for me is the starting point. Instead of staring at a vague giant task, I can just describe what I’m trying to do and ask for the first three steps. That’s it. Three small steps I can actually look at and say “okay, I can do that one.” The momentum from step one usually carries me further than I expected. It sounds stupidly simple but for my brain it makes a real difference.

The Hyperfocus Trap

Hyperfocus is the thing people get wrong about ADHD. Everyone hears “attention deficit” and assumes we can’t focus on anything. The reality is we can focus intensely — just not always on what we’re supposed to be focusing on. I’ve lost entire days to a random topic I got curious about at 10am while trying to do something completely unrelated.

I started using AI to build simple daily checklists and structures that I can glance at when I come up for air. Nothing fancy. Just a list of things that need to happen today so that when I resurface from three hours of hyperfocus on whatever my brain decided was urgent, I have a visible reminder that other stuff exists and needs attention too. Having it written down somewhere means I don’t have to hold it in my head, which frees up mental space for actually doing things.

Decision Fatigue Is Real and It’s Exhausting

Here’s something I don’t think people without ADHD fully understand: making decisions is genuinely tiring for us. Not in a dramatic way. Just in a “I have been thinking about what to make for dinner for forty-five minutes and I still haven’t eaten” kind of way. Small decisions can pile up and drain the tank faster than you’d expect.

AI helps because I can offload some of that. “Here are my options, what’s the most logical choice given these constraints?” Sometimes I already know the answer and I just need something to confirm it out loud so I can stop second-guessing myself and move on. That sounds weird but it genuinely works. Decision made, move on, tank refilled a little.

Asking the Same Question Ten Different Ways

I learn better when I can ask the same question in five different ways until one of them clicks. In school that wasn’t really an option. You got the explanation once, maybe twice if you pushed it, and then you were on your own. Asking again felt embarrassing.

With AI there’s no judgment. I can say “I still don’t get it, explain it differently” as many times as I need to. I can ask for an analogy. I can ask for a simpler version. I can ask what the most confusing part usually is for people and work backwards from that. That flexibility changed how quickly I pick up new things because I’m not stuck on one explanation that didn’t land.

// Honest moment: The first time I realized I could just keep asking until it made sense without anyone getting frustrated with me, something genuinely shifted. That sounds small. It wasn’t small.

Getting the Noise Out of My Head

ADHD brains tend to run loud. There’s a constant background hum of things I need to do, things I forgot to do, things I’m worried about, things I’m excited about, ideas I had three days ago that I never wrote down. Holding all of that in working memory while also trying to function is exhausting.

Brain dumping into AI and asking it to help me sort and prioritize that mess has become one of the most useful things I do. Not every day. But when things feel chaotic and I can’t figure out what to actually focus on, getting everything out of my head and into an organized format cuts the noise significantly. It doesn’t fix the chaos but it makes it navigable.

It’s One Tool in a Bigger Toolbox

I want to be clear about something: AI is not a treatment for ADHD and I’m not suggesting it should be anyone’s primary support. Routines, reminders, therapy, medication if that’s right for you, support from people who get it — all of that matters more than any app or tool. What AI does is fill in some gaps and remove some friction. It’s useful specifically because it’s flexible, available whenever, and doesn’t require you to explain your situation to another person before it helps you.

For me it works best as a way to lower the activation energy on tasks I keep avoiding, to organize thoughts I can’t organize myself in the moment, and to learn things at my own pace without feeling like a burden for needing more time. Those are pretty specific use cases but they come up constantly when you have ADHD.

Final Thoughts

If you’ve got ADHD and you’re already using AI tools, you probably recognize some of this. If you haven’t tried it yet, it’s worth experimenting with. Don’t expect miracles. Do expect a tool that’s patient, flexible, and surprisingly good at helping you get unstuck.

The goal isn’t to rely on it for everything. The goal is to spend less energy on the friction and more energy on the stuff that actually matters. For me, that’s been worth it.

Running AI Locally — What I Learned Doing It on a Homelab | BugzCloud.xyz

← Blog · Homelab · AI

Running AI Locally — What I Learned Doing It on a Homelab

Bugz April 2026 BugzCloud.xyz

Running AI locally used to mean either spending a fortune on hardware or accepting that you’d be waiting minutes for results. That’s changed a lot. I’ve been running local AI models on my homelab for a while now — image generation, language models, text-to-speech — and the experience has gone from “technically possible but painful” to genuinely useful. Here’s what I’ve learned and what actually matters when you’re setting this up yourself.

Why Run AI Locally at All

The obvious answer is privacy — running AI locally means nothing you generate goes to external servers. But honestly, that wasn’t my main motivation. I got into it because I wanted to experiment without worrying about content policies, rate limits, or paying per generation. Once you have the hardware, it’s essentially free to run as many generations as you want.

The other reason is customization. Cloud AI services give you what they give you. Running locally means you can load specific models, use fine-tuned versions trained on particular styles, and configure things exactly how you want them. For image generation especially, the difference between a generic cloud result and a carefully configured local setup is significant.

// the honest caveat:
Local AI is genuinely useful but it’s not magic. You still need decent hardware, some patience for setup, and realistic expectations about what consumer-grade hardware can do versus data center compute. The results are impressive for what they cost — not impressive compared to unlimited cloud resources.

What Hardware You Actually Need

VRAM is the bottleneck for almost everything AI-related. More VRAM means you can run larger models, generate at higher resolutions, and keep more things loaded simultaneously. Here’s a rough breakdown of what you can do at different VRAM levels:

4GB VRAMBasic image generation, small language models only

6GB VRAMStandard image generation, moderate quality

8GB VRAMGood image generation, small-medium language models

12GB VRAMComfortable for most tasks, medium language models

16GB+ VRAMLarge models, high resolution, multiple simultaneous tasks

My home server currently runs a 6GB card which handles image generation fine but shows its limitations with larger language models — that’s the next upgrade on my list. Beyond VRAM, you want fast storage because model files are large and load times matter, and enough system RAM to handle models that spill over from VRAM. 32GB of system RAM is comfortable, 16GB works but you’ll feel the edges.

Image Generation — What the Setup Looks Like

The image generation ecosystem has matured a lot. There are several well-developed frontends that handle model management, prompt building, and generation queue. Most of them install relatively cleanly if you’re comfortable with the command line and have Python set up.

The learning curve isn’t really the software — it’s understanding how to prompt effectively and how to pick and combine models. The base models are a starting point. The community-trained fine-tunes and other add-ons on top of them are where it gets interesting. Finding ones that work well for your use case takes experimentation.

⚠️ Storage warning: Model files add up fast. A single checkpoint file can be 2-7GB. If you start collecting models and add-ons you’ll fill up storage faster than you expect. Plan for this before you start downloading everything.

Local Language Models

Running large language models locally is more hardware-demanding than image generation. The models that run well on consumer hardware are the quantized versions — compressed versions of larger models that trade some quality for dramatically lower VRAM requirements. A well-quantized 7-8 billion parameter model runs fine on 8GB VRAM and produces genuinely useful results for most tasks.

The tools for serving local language models have gotten much better. Several projects now expose an API-compatible interface which means you can point applications that support configurable AI backends at your local model instead of a cloud service. I use this to run local chat and tools on my own hardware — it works well for anything that doesn’t require the absolute latest model capabilities.

Text-to-Speech

This one surprised me with how good it’s gotten. Local TTS models can now produce natural-sounding speech that’s hard to distinguish from cloud services in many cases. The latency is low enough for real-time use on decent hardware. I run a TTS service on my homelab that integrates with my other local AI tools — it’s a small thing but it makes the whole setup feel more complete.

The Honest Tradeoffs

Running AI locally isn’t strictly better than cloud services — it’s different. Cloud services have newer models, more compute, and zero setup friction. Local setups have privacy, no per-use costs, and full control over configuration. Which matters more depends entirely on what you’re doing.

For experimentation, creative work, and anything privacy-sensitive, local is genuinely the better choice once you have the hardware. For tasks where you need the absolute best model quality and don’t want to think about infrastructure, cloud is still easier.

The hardware investment pays off faster than you’d expect if you use it regularly. The setup time is a one-time cost. And there’s something satisfying about running AI that lives entirely on hardware in your own house, with no external dependencies and no one else involved. If you’re thinking about trying it — start with whatever GPU you already have. The barrier to entry is lower than it used to be.