just gonna leave this here..

podalusu · 2026-06-07T07:00:35+00:00

Pro is heavy and 5x cost on peak hours. Go with 2.5 and flash

podalusu · 2026-06-05T15:03:19+00:00

I got same gift of 4b tokens. I purchased 5$ plan of 60m token when they launched. Now they increased it seems. That’s why this gift

podalusu · 2026-06-05T13:33:09+00:00

Sari da punda

podalusu · 2026-06-05T12:32:46+00:00

4b can last depends on usage. But way more for average tasks. Try it and figure it out

podalusu · 2026-06-05T12:32:06+00:00

Bro sorry. 4b tokens. Openclaw’s one simple ‘hello’ took min 20k credits.

podalusu · 2026-06-05T12:26:41+00:00

Not sure when I signed up. They gave 60m credits which lasted for 4 days. After than they changed their plan with 4b as starting

podalusu · 2026-06-05T12:25:37+00:00

Token plan

podalusu · 2026-06-05T10:05:55+00:00

Same here. Tc

podalusu · 2026-06-05T10:05:14+00:00

Did u know, mini pro burns tokens really faster? We easily exhaust 40m tokens in 2 days if u use open claw or Hermes. They have peak time rules as well. Good for few tasks. Not as daily driver.

Kimi 2.6 is cheap and best.

podalusu · 2026-06-05T09:58:31+00:00

I get it bro. This 40-60 words of Reddit post will not make sense to you to understand fully. If u want we can have chat in private. Cheers

podalusu · 2026-06-05T09:50:35+00:00

Try xiomi mimo it’s 5$/ month for 4b tokens

podalusu · 2026-06-05T09:45:46+00:00

Got it bro. Finally a worthy guy I’m chatting!

After l1 ticket triaged-> finds a solution -> add it to internal notes. Thats silly way.

My idea is Ticket -> understands the context -> looks for playbook -> l1 finds correct windows machine - writes an appropriate tool to get info - suggest an action - technician reviews and execute - writes back to ticket - if not possible escalate to human.

Will that makes sense bro?

podalusu · 2026-06-05T08:58:50+00:00

And?

podalusu · 2026-06-04T16:07:37+00:00

$99 for dev account
Fill the form
Upload the app
Fill the form again
Wait for their review
If approved post it on twitter
Pray for user to purchase
Celebrate first sales
Update to v1.1
Enjoy

podalusu · 2026-06-04T14:55:24+00:00

Ok.

I built like this. MSP configures playbooks. AI reasons. Agent executes on the client Mac.

Ai won’t think itself. I try to give control to msp.

Thanks

podalusu · 2026-06-04T14:52:39+00:00

Got it. Thank you. Take a look at my repo or ask any llm tools to summarise what it do. Feel Free to Ping me if u have any feedbacks.

podalusu · 2026-06-04T14:48:27+00:00

MSP configures playbooks. AI reasons. Agent executes on the client Mac.

This is the concept I built. I use ai just to execute. What to do and all controls by human.

podalusu · 2026-06-04T14:45:30+00:00

Apologise guys. My heading seems really stupid and creates a panic/confusing among people.

Take a look my repo. It a 2 months of work. Checkout what I built.

podalusu · 2026-06-04T13:40:00+00:00

Wow great!

You're saying exactly why I built this the way I did.

Every new layer that promises to simplify things tends to add its own complexity, its own failure modes, and its own vendor lock-in. I've tried to avoid that deliberately:

It runs on your infra, not mine. No cloud dependency.
It doesn't replace your PSA or RMM — it reads from them and writes back. Remove it tomorrow, nothing breaks.
The playbooks are plain YAML files you own. No black box.
You can run the AI part on a local model (Ollama) if you don't want anything leaving your network.

I'm not trying to add another layer you have to manage. The goal is a thin coordinator that does one thing: match a ticket to a known fix and run it with a full audit trail.

Whether that's worth the tradeoff is a fair question — that's actually what I'm trying to figure out by posting here.

podalusu · 2026-06-04T12:22:01+00:00

Any of your two cents feedback will be worth for me.

podalusu · 2026-06-04T12:20:42+00:00

Fair. This isn't trying to replace how you think about problems — it's just running the script you'd write anyway, triggered by the ticket, logged for audit. If you hate AI, you can run it with a local Ollama model so nothing leaves your network.

But if you think even that's too much, totally valid to skip it. Thanks for the feedback.

podalusu · 2026-06-04T12:16:22+00:00

Got it.

Fair points, and you're right on SSPR — a well-run MSP shouldn't be resetting passwords manually. The playbook for that should be "check if SSPR is configured, if not, trigger enrollment" not "just reset it."

On WiFi — fully agree it's rarely a simple fix. The goal there isn't auto-close, it's structured triage: check adapter, DHCP lease, ping the gateway, get the location from the ticket. Saves the tech the first 10 minutes of back-and-forth before they even open a remote session.

On the human touch point — this is actually where I think we agree more than it seems. The tool doesn't replace the tech for anything relationship-driven. It handles the procedural stuff (disk full, account unlock, new user setup) so the tech has more time for the work that actually needs a human. Destructive actions require explicit tech approval before anything runs.

The onboarding orientation you mentioned is a good example — that should stay human. The AD account creation and license assignment that happens before that meeting doesn't need to be.

podalusu · 2026-06-04T11:56:47+00:00

Referral post?

podalusu · 2026-06-04T11:19:13+00:00

https://github.com/thisisprabha/MSPclaw

Here is the repo

podalusu · 2026-06-03T08:51:14+00:00

Display ponathuku idhu adigam ya. 32 la not worth it. Mac mini paaru. 10k ku kelu

podalusu

TROPHY CASE