I would like to share my experience of using DMJBot to automate my daily activities on Reddit.
This is not about spam. I just wanted to save some time on the routine stuff I do anyway. Usually I open a few of my favorite subreddits, read some posts, comment on them, upvote or downvote, and occasionally publish something myself. I use only my own account for this — no multiple accounts, no spam, no bot farm. Just me, doing the same clicks I always do, except now I don't have to.
So when I got DMJBot running, Reddit was the first thing I decided to hand over to it.
My setup
I run DMJBot in Docker on my VPS.
I also connected all my laptops to it, including two old ones I hadn't touched in a long time. Both just sit with closed lids in my utility room, plugged in and connected to my DMJBot instance. One of them runs Windows, and that's the one I use for Reddit automation.
On that laptop I installed the dmjbot-bridge tool and a Chrome browser, and gave DMJBot a way to drive Chrome on it. Before automating anything, I logged into my Reddit account in that browser by hand and confirmed everything worked. From then on, DMJBot uses that browser session — the same logged-in Chrome I would use myself.
For the AI side I mostly use DeepSeek models, but I have all the top models configured too (OpenAI, Google Gemini, Anthropic, and others) and switch between them when I feel like it.
That's the whole idea, really: a cheap always-on brain on the VPS, an old laptop doing the clicking, and my normal browser session doing the work.
Teaching DMJBot my Reddit workflow
I spent a couple of hours "teaching" DMJBot how I use Reddit. The outcome wasn't a brittle script — it was a skill, a reusable bit of know-how that DMJBot can now run on its own, quickly, without me hovering over it.
And the teaching was just a chat. No code. I literally explained what I wanted, the way I'd explain it to a new assistant:
Me: I want to automate my Reddit activities. I want to read posts, comment on them, upvote or downvote some posts — in my account only, no spam, no multiple accounts. Open Reddit in Chrome. Can you navigate the subreddits I joined?
While it worked, I watched over the remote desktop. I just wanted to see what DMJBot was actually doing, and honestly it was satisfying — it opened Reddit, moved through subreddits, opened posts, read them, came back. It behaved like a careful human, not a scraper hammering the site.
Reading from Reddit turned out to be the easy part. Once it had figured out my flow, I asked it to write down what it learned:
Me: Now summarize what we learned and create a skill, name it something like "reddit activities automation". Save this knowledge so we can reuse it next time.
And that was it for reading. The interesting challenge came next.
Posting and commenting is the hard part
Automating actions like posting and commenting is a lot like QA test automation: you have to reliably find the right buttons and input fields on the page and interact with them.
For a site like Reddit, that's genuinely hard. They don't love automation, so they have anti-bot protection, and their web app is complicated and constantly changing. There are no nice, stable handles to grab onto — and even if you find one today, it tends to break in a week. So I didn't expect to be able to write a script, or even a skill, that would keep working for long using the usual QA tricks.
This is exactly where an AI assistant like DMJBot shines: instead of hard-coding fragile instructions, it can look at the page and figure out the right thing to interact with every time it runs the workflow. The page changed? It just looks again.
But this is also where a lot of people automating with AI get stuck — and it's the part I want to spend a minute on, because it's the difference between a fun demo and something you can actually use every day.
The part nobody warns you about: tokens
The naive approach to "let the AI figure out the page" is simple to describe: grab the entire page, send it to the model, and ask "what should I click next?"
It works in a demo. Then you watch your token bill.
A modern web page — and Reddit especially — is enormous under the hood. Feeding that whole thing to a language model on every single step of every single action is staggeringly wasteful. You'll burn through a fortune of tokens before lunch, the model gets confused by the noise, and the whole thing is slow and unreliable. Lots of "AI browser automation" projects die right here. They technically work, but nobody can afford to leave them running.
DMJBot avoids this trap in two ways, and I could see both happening live in the chat.
First, it doesn't look at the whole page. Instead of shoving a giant blob of page markup at the model, the browser tools hand it a compact, cleaned-up view of the page that contains just the things you can actually interact with — the buttons, the fields, the links. (How that view is produced is the browser tools' own little bit of magic; I don't need to understand it and neither do you.) The result is that each step costs almost nothing.
You can see it in the chat. Here's DMJBot working through publishing a post for me, one step at a time:
Look at the little numbers on each step — 142 bytes, 134 bytes, 123 bytes, 1149 bytes. That's how much information moved on each action. Tiny. Compare that to dumping a full Reddit page (hundreds of kilobytes) into the model every step, and you understand instantly why one approach is sustainable and the other isn't.
Second, it delegates the fiddly work. Notice the line at the top of that screenshot:
Now I have all the info. This is a multi-round task — I'll delegate it to a subagent.
The back-and-forth of poking at a web form is handed off to a focused helper agent. All that step-by-step churn happens off to the side, so my main conversation with DMJBot stays clean and cheap. I get a tidy result, not a wall of clicks clogging up the chat.
The payoff
After the teaching session, posting to Reddit became a one-liner. I just tell DMJBot what I want:
…and a minute later it's done — title, flair, the works — with a link to the live post:
No selectors for me to maintain. No browser open on my main machine. No babysitting. The old Windows laptop in the utility room did the clicking, the cheap model on the VPS did the thinking, and the skill we built together held all the know-how.
And because it's a skill and not a script, when Reddit changes something, DMJBot just looks at the page again and adapts — and we update the skill once, in plain language, instead of debugging brittle code.
An honest note on cost
I should be straight with you about one thing: the session where all this actually happened — DMJBot working through Reddit for the first time and the skill getting built out of it — was not cheap. End to end, it burned through about 200K tokens. That's the price of figuring it out the first time.
So don't let the "each step costs almost nothing" part fool you into thinking the whole thing is free. Doing this kind of exploratory work often — spinning up new workflows, letting the AI grind through a complex page from scratch — will cost you real money. Budget for it. The trick is that you pay that cost once to produce a skill, and then the day-to-day runs are the cheap part. If you skip the skill and let the AI re-figure-out the page every single time, you're paying that expensive 200K-style discovery on every run — and that's exactly the trap that kills these projects.
Take the skill
The whole point of building this as a skill is that it's reusable — including by you. Here's the exact skill we ended up with for reading and posting on Reddit. Drop it into your own DMJBot and adapt it to your workflow.
⬇ Download the Reddit automation skill
The bigger picture
The takeaway for me wasn't really about Reddit. It was that automating a genuinely complex, hostile-to-automation web application is now realistic — and, just as important, affordable to leave running. The two usually don't go together. The thing that normally kills these projects isn't "can the AI do it," it's "can you afford to let the AI do it all day." DMJBot answered both for me.
If you've got a routine buried inside some fiddly web app, that's exactly the kind of thing worth handing over. Teach it once, in a chat, and let it run.
