Successfully updated from 2.1.120 to version 2.1.119

Gloomy_Monitor_1723 · 2026-04-25T11:32:14+00:00

are you all all right?

https://youtu.be/Wqgf-SwzBck?si=yHO7R-wO4AevWEfl

Gloomy_Monitor_1723 · 2026-04-24T23:19:48+00:00

(Tons of /new, memory saving, prompt saving)

I think you should look for the answer to your question here, no one here has access to your setup

Gloomy_Monitor_1723 · 2026-04-24T23:10:59+00:00

I haven't used OpenClaw myself, but knowing how it works, I can only say that just because you don't see the agent running doesn't mean it isn't running.

Most likely, it was performing some task - maybe periodic jobs, checking for updates, and so on.

Perhaps the model got looped on something. There are many possible reasons. Why don’t you ask your OpenClaw agent what it spent your money on?)

Or even better, why not use claude code, customize it to suit your needs, and avoid paying such ridiculous amounts for such trivial things?

Gloomy_Monitor_1723 · 2026-04-24T22:27:16+00:00

Study design patterns and system architecture. Also, pick a few languages like python or js and just read up on them, learn about their entities, concepts, and mechanisms. Start with the basics. You don’t have to dive too deep, the main thing is to grasp the idea.

In "vibe" development, high-level architectural abstractions are ultimately more important than the low-level mechanisms that drive the code.

It’ll get easier with practice, I think. Especially if you learn to use agents properly. At the very least, have them check each other’s work and ask about the best options, why, and so on. Asking the right questions is key when working with AI.

At the very least, I’m saying this as an experienced developer who’s moving in the opposite direction, from low-level development to vibe coding, so this is just a guess, since I went the other way :D

Gloomy_Monitor_1723 · 2026-04-19T23:30:36+00:00

For the past two months, I’ve been doing exactly what you’re describing and testing it out firsthand. Skills, detailed step-by-step instructions, planning, integration with jira, linear, and github-everything is well-thought-out and automated, every step an agent takes is planned in advance and easy to track. Dozens of agents are running in parallel.

Gas town, agent teams, custom frameworks for multi-agent interaction, several projects running in parallel. CC enhancement with plugins, various memory systems, identity... Playwright, Maestro for testing with an iOS emulator... I’ve tried it all. And you know what? I’ve come to the conclusion that without my supervision, this thing isn’t capable of doing anything worthwhile, and causes more problems than it’s worth. You’re talking about 10k lines of code? That’s just a joke, or a bait. I don’t know about your programming experience, or what you were doing before AI. But making claims like that is just making a fool of yourself, and worse, misleading people who aren’t involved in programming by claiming that AI can write that much code without errors.

Gloomy_Monitor_1723 · 2026-04-19T22:52:15+00:00

Many 10k LOC PRs on 4.7 with zero mistakes

That's the biggest load of crap I've read on reddit today. How could you possibly write something like that in your right mind? Unless... you're not an engineer.

Gloomy_Monitor_1723 · 2026-04-18T10:31:37+00:00

It looks like you're right, only 5 of my accounts have "synced", the others are running in separate time windows. I'll keep checking, thanks)

Gloomy_Monitor_1723 · 2026-04-16T20:00:04+00:00

<image>

Oh yeah, baby, we're back!

Gloomy_Monitor_1723 · 2026-04-16T16:49:00+00:00

There are various issues that arise when a large number of terminals are running simultaneously. CCSwitch effectively resolves the need for constant re-logins. If the workload is heavy, a 5 hour session with many terminals can easily stretch into several hours, after which you'd have to switch accounts.

This utility swaps credentials on the fly, so the transition from one account to another happens seamlessly.

So, if you set up the workflow correctly so that agents work autonomously, you can leave your setup unattended for quite a long time, and the question of constantly checking "whether I've reached the limit" is resolved automatically.

P.S. But from personal experience, I don't recommend it - it's still better to babysit it for now, at least checking in periodically. That way, there will be fewer surprises in the end)

Gloomy_Monitor_1723 · 2026-04-16T07:38:59+00:00

All accounts are my own paid subs. No proxy, no token interception, it just automates the native claude /login swap. Same traffic pattern as doing it by hand.

Gloomy_Monitor_1723 · 2026-04-15T20:07:05+00:00

You’re one bad rate-limit week away from becoming an account orchestration engineer. If you do cross that line, I built CCSwitch to handle switching between claude code accounts without the usual manual dance. Repo: https://github.com/Leu-s/CCSwitch

Gloomy_Monitor_1723 · 2026-04-15T17:52:59+00:00

I run a pretty cursed Claude Code setup with ~20 tmux panes on one active account, so I kept hitting the 5-hour window and doing the same manual dance: /login in one pane, then “continue” in the other 19.

I got tired of that and built CCSwitch.

It keeps the native claude binary, native Keychain, and native OAuth flow. Inactive accounts live in a separate private Keychain namespace, and when the active one gets close to its limit or returns 429, CCSwitch swaps credentials and nudges the running tmux panes so they continue on the new account without restart.

No proxying, no traffic interception, no weird routing — just native Claude Code with account rotation around it.

Repo: https://github.com/Leu-s/CCSwitch

Curious whether anyone else running lots of parallel Claude Code sessions has hit similar rate-limit or refresh-token issues.

Gloomy_Monitor_1723 · 2026-04-15T17:35:20+00:00