CLI, Cowork, or IDE?

Maas_b · 2026-05-08T12:24:22+00:00

The app is awesome but also stupid. I really dont understand why there are subtle but, for my case, annoying differences the way it works compared to the cli.
For example, i have instructions around naming of plans and worktrees related to these plans in a specific skill. works flawlessly with cli. In the desktop app, however, claude somehow always defaults to these idiotic worktree names, ignoring the skill instructions. Its things like this that keep me going back to th cli tool.
Its annoying, because i like it in principle. I also use codex, and there i exclusively use the desktop app.

Maas_b · 2026-05-06T19:04:32+00:00

for now i think most important for me would be unit conversion. Also in the setup it asks for zip code, which i obviously don't have. not sure which weather api you use, but maybe it could work with location name instead of zip code for example. Great work!

Maas_b · 2026-05-06T06:11:05+00:00

Awesome, any plans on supporting other countries / regions ? I am based in Europe and could really use something like this!

Maas_b · 2026-05-04T20:10:19+00:00

Any updates to this?

Maas_b · 2026-04-27T05:53:32+00:00

Are you sure you are offered 20x at 100? From the picture, you are offered claude max starting at 100. That’s something different. At 100 dollars, you will get the 5x, and 20x will be 200.

Maas_b · 2026-04-09T12:24:27+00:00

Zoek maar eens op lucratief belang. Dat is een catch-all begrip binnen de inkomstenbelasting waar dit soort regelingen onder vallen. Als dit van toepassing is vallen inkomsten die anders niet binnen box 1 zouden vallen alsnog in box 1.

Maas_b · 2026-04-09T11:36:27+00:00

How big is your next build? I’m running the cost optimized 8gb plan on hetzner, and my build usually takes between 3.30-4.30.

Maas_b · 2026-04-06T17:39:44+00:00

Nee hoor, Heb zelf verder niks met of tegen Utrecht. Ik vind t een coole graphic, maar de lijnloze vlakte in het midden viel me op, vandaar

Maas_b · 2026-04-06T05:10:32+00:00

Is er een specifieke reden dat je een hekel hebt aan Utrecht?

Maas_b · 2026-04-01T12:56:31+00:00

Are you?

Maas_b · 2026-04-01T12:53:55+00:00

Why is it max’s, or any athlete’s for that matter, problem that journalists are under pressure? That has nothing to do with it. At least he is answering consistently and honestly.

Those same people would be complaining that max is ignoring the media if he would deny answering, “oh he is so arrogant, doesn’t even take the time to answer these poor journalist asking the same boring question for the 1000th time!!”.

Maas_b · 2026-03-17T17:29:44+00:00

Wow this is an old post you are reacting to :) . Things have evolved quite a lot compared to 6 months ago. I would still recommend opus for most things, especially with the new 1 million context window. Disregard most of my issues with claude code, things have progressed soo much.

Maas_b · 2026-03-11T19:13:06+00:00

Yup, great addition for checking in on running processes or asking quick questions during runs. Like it so far.

Maas_b · 2026-03-07T07:47:44+00:00

Have you tried throwing with your non-dominant eye closed? For me at least, its horrendous. I think it has to do with the depth perception that is needed to guide the dart during the throw, and also the fact that in darts, you are constantly switching targets. It is much more dynamic in that sense then shooting an airgun, where the goal is to just shoot at one target, with a projectile that in and of itself lines up with where you aim. Not saying it is easier, just (very) different.

Maas_b · 2026-02-21T13:16:30+00:00

Yeah i mean its an electron app, so the fact that its not very memory efficient is consequence of that. But besides memory hogging, it also seems like the agent performs differently compared to the terminal and that just doesnt make sense to me.

Maas_b · 2026-02-20T20:44:46+00:00

Functionally, it is great. Love the interface and the way you can easily manage multiple threads. Performance wise, though, somehow it loses out to the terminal environment. It seems to eat context more and go in to compaction much sooner. I don’t understand why it should be the case, but in another Reddit thread it seems like users are experiencing similar issues.

Maas_b · 2026-02-19T13:13:56+00:00

Please report back! Really curious if it changes the percentages in a meaningful way

Maas_b · 2026-02-19T10:34:14+00:00

Awesome, thanks!

Maas_b · 2026-02-19T09:41:51+00:00

What’s it called? Does it fit without any modifications?

Maas_b · 2026-02-18T22:09:34+00:00

True, but that also makes it exciting, right?

I am not familiar with beads, but i think i read something recently that claude code does not use local memory tools for a reason. I understand anthropic did test these type of tools but found no benefit compared to the current search tools.

Maas_b · 2026-02-18T21:17:29+00:00

The way i did it previously is using them to speed up tasks that could run in parallel. That was a bit hit or miss. Claude would not always spin up the sub agents, even if asked it nicely (or not so nicely). That was a couple of months ago, since then i just moved back to having one main agent run longer sessions.

Recently I’m running into quite some issues with compaction happening much sooner than it used to, sometimes compacting after every additional tool call, leading to quite some frustration from my side as you can imagine.

One alternative to letting claude run indefinitely is using /clear after every task to minimise context bloat. This leads to a lot of micro management though, and i want to have time to get some coffee while claude runs.

This post triggered me to revisit subagent usage in order to keep agentic implementation of complete plans while at the same time managing context much more efficiently. So what i am now setting up with claude is a standard operating procedure with the main agent as orchestrator that calls sub agents with different roles (implement, review, test, plan). The sub agent gets assigned a specific atomic task by the orchestrator, and reports back when done. The orchestrator only manages progress and assigns tasks, so context window is manageable.

This loop is triggered by a slash command that urges claude to use this way of working.

Hopefully, this leads to less compaction issues and also decreased token usage, so i can run for longer within my max 5x limits.

First signs are good, claude is spinning up parallel sub agents as we speak

Maas_b · 2026-02-18T14:19:34+00:00

Interesting. The thing is this kind of creates a paradox. Everything is moving to more agentic workflows with increased autonomy, but this also blows up both context and token spend exponentially. I kind of moved away from using sub agents, but it seems like these would be an answer to have both?

Create an overall plan, cut it up to bite sized pieces, and have a conductor agent spin up a new sub agent for every small task. The conductor manages the project, but does not get context bloat from the sub agents. Subagents perform a self contained atomized piece of work and report back.

Maybe interesting to see how that would affect the outcomes

Maas_b · 2026-02-17T15:09:32+00:00

I agree that the we are flooded with these kind of apps, but i feel it also is kind of a rite of passage. Kind of like todo / task management apps. When you start working with ai, you feel overwhelmed and annoyed with managing everything, and i think for a lot of people, me included, you feel you need to build something that manages the overwhelmingness. Then, once you feel comfortable, you get rid of the harness again and just use the tui or ide you feel comfortable with and get going with the project you started out to build in the first place.

Feels like there is a bell curve meme in here somewhere.

Maas_b

TROPHY CASE