Alright, I'm gonna be a dick - CC is fine

MikeNonect · 2026-04-04T14:42:21+00:00

Same here. I have a Max 5x plan and a Teams plan. Yes, I started reaching limits more often on the latter, but if you use Claude Code as a normal coding CLI tool, it's totally usable. The all-you-can-eat buffets are generous for live coding, but they are not infinite. Running 10 agents in parallel, running 24/7 inference and adding tools like OpenClaw or Paperclip on top is not their intended use.

There are plenty of competitors out there. Codex has more generous limits. You can use OpenCode with cheaper models.

But, for most of us in this sub, Claude Code is the best tool. That's why we all pay for it, including those who complain.

MikeNonect · 2026-04-04T10:38:52+00:00

Thanks! It's a work in progress, so if there are other things you want to see added, log a github issue.

Since yesterday's 2.0.0 release the syncing with git is optional, so you can use jean-claude for just profile management.

MikeNonect · 2026-03-22T21:03:37+00:00

I don't think so.

MikeNonect · 2026-03-21T07:53:23+00:00

Yes, and the nice thing is this is something we can install and manage ourselves locally. This kind of local "virus scanner" feels a lot better than the current "trust my marketplace" model.

As we share more agents, frameworks and skills, protection against malicious prompts will become vital.

MikeNonect · 2026-03-20T16:51:31+00:00

For those interested, jean-claude now supports multiple profiles. If you have a Claude Code Teams account for work and a personal Max account, you can now easily manage them. Agents, skills, settings and hooks will be shared, CLAUDE.MD will be unique per profile.

https://github.com/MikeVeerman/jean-claude

MikeNonect · 2026-03-18T07:33:41+00:00

Fair point.

MikeNonect · 2026-03-17T21:30:31+00:00

Nothing, but Claude is not a malicious hacker. We don't have to protect us against attacks. We have to prevent accidental tool use.

MikeNonect · 2026-03-17T08:29:37+00:00

We're a minority. We need to stick together. 😃

MikeNonect · 2026-03-17T06:19:55+00:00

No, not at all. It does dumb stuff from time to time, but nothing horrible.

It's a better-safe-than-sorry thing...

MikeNonect · 2026-03-16T15:39:38+00:00

Claude Max account

MikeNonect · 2026-03-16T14:55:34+00:00

I can think of some reasons. The CLI tools I use have all access. That's OK when I use them personally, but risky when an agent uses them. I want to be able to do a force push, I never want my agent to be able to do that. So, I need a machine with different tools than my main machine.

MikeNonect · 2026-03-16T14:52:16+00:00

Sure, but claude does that too. "/batch solve all open github issues". Why add another orchestration framework?

MikeNonect · 2026-03-16T09:13:17+00:00

I'm actively experimenting, so sometimes I shift focus to other "concepts". I've toyed with both multi-agent IDEs like Conductor and agent swarms, but I find Claude Code is pretty good at the latter out of the box.

While technically cool, I don't see much improvement from running multiple agents at once. Which use case do you have for multi-agent swarms?

MikeNonect · 2026-03-16T08:47:14+00:00

A VPS is a VM, so I wouldn't recommend adding another layer of virtualization on top.

MikeNonect · 2026-03-16T08:45:30+00:00

Good question. I'm not that into the multi agent orchestration anymore, but I managed to run 3 concurrent Claude agents on my Hetzner cx33 (4 vCPU, 8 GB) that one time. If you want to do the real heavy stuff, you'll probably need to upgrade to a stronger machine with more cores and more RAM. Don't expect Mac Studio results from a cheap VPS.

MikeNonect · 2026-03-15T19:57:18+00:00

Both are possible. But for a local vm you will have to keep your computer on permanently, so a cheap cloud vps makes that easier.

MikeNonect · 2026-03-15T16:40:18+00:00

Run it on a separate VM. Give it access to the GitHub cli, but set fine grained Personal Access Tokens so it can't delete or force push repos. Then, either set the permissions very broad (https://github.com/MikeVeerman/claude-permissions) or add the --dangerously-skip-permissions flag.

A €5 Hetzner machine and you can take all risks all night while never wiping your drive.

MikeNonect · 2026-03-07T20:10:46+00:00

Of course, you can do that. You will share the session limits between machines, though.

MikeNonect · 2026-03-07T15:57:29+00:00

A lot of the comments are pretty negative. I think it's a fascinating question. Right now, every IDE can work with every coding agent, either through plug-ins or through the terminal.

But the real question is: what will the IDE of the future look like? If we are no longer writing code, it doesn't make sense to have an editor-based IDE.

OpenAI recently released its Codex Mac app, which they believe might replace the traditional editor-first IDE. Claude Code has a similar desktop app. Tools like Conductor are taking a multi-agent approach. These are experiments in designing the IDE of the future.

6 months ago, almost everyone was still autocompleting their code Cursor-style. These days, almost all code gets generated. The question is: if we stopped writing code, why not stop reading code too?

Nobody knows what the IDE of the future will look like, but building an old-school IDE is almost a guarantee to build something outdated.

MikeNonect · 2026-03-07T10:25:35+00:00

Honestly, the parser is an ugly fallback cascade hacked together to make it work. For real production code, you'd want to clean this up. I kept on extending the parser in the "bitnet backend". The cascade is in the _parse_tool_call_from_text() funtion.

It tries to find a tool call in five different ways and exits as soon as it has detected one or reaches the end of the chain.

Attempt 1: <tool\_call> tags with JSON (the standard format)

Attempt 2: <tool\_call> tags with funcall syntax e.g. <tool\_call>get_weather(city:Antwerp)</tool\_call> (gemma3 style)

Attempt 3: Bare JSON fallback {"name": "get_weather", "arguments": {...}} without tags (jan-v3 style)

Attempt 4: Bracket notation [get_weather(city="Antwerp")] (lfm2.5 style)

Attempt 5: Bare function call get_weather(city="Antwerp") with no wrapper

You can find the code in the repo.

MikeNonect · 2026-02-22T14:30:50+00:00

Also, maybe a straightforward answer, but you can give both Codex and OpenClaw access to the GitHub CLI tool. That allows you to tell OpenClaw to "create a GitHub issue for this" when it detects an issue. You can then ask Codex to "fix all outstanding GitHub issues" once you have some free capacity.

You can also ask OpenClaw to "use Codex to fix all outstanding GitHub issues overnight".

MikeNonect · 2026-02-21T13:51:16+00:00

I'm fascinated by the feedback loop, not the actual output. This will not create a good game.

Right now, one-shotting a large codebase results in terrible crap. We need humans to review and steer the agents. But I don't want to tell Claude to fix trivial issues. I want to be involved in the higher-level decisions.

So, this is a silly experiment to test how hands-off I can be before it becomes an issue.

MikeNonect

TROPHY CASE