Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Shall I implement it? No

gist.github.com

Post reply on HN
Print view View original

251–260 of 603 posts

Re: Shall I implement it? No

#251

Post by eyeris »

to11mtm wrote: post #237
dostick wrote: post #213

Its gotten so bad that Claude will pretend in 10 of 10 cases that task is done/on screenshot bug is fixed, it will even output screenshot in chat, and you can see the bug is not fixed pretty clear there. I consulted Claude chat and it admitted this as a major problem with Claude these days, and suggested that I should ask what are the coordinates of UI controls are on screenshot thus forcing it to look. So I did that…

I mean, I don't use CC itself, just Claude through Copilot IDE plugin for 'reasons'... At at least there it's more honest than GPT, although at work especially it loves to decide not to use the built in tools and instead YOLO on the terminal but doesn't realize it's in powershell not a true nix terminal, and when it gets that right there's a 50/50 shot it can actually read the output (i.e. spirals repeatedly trying t…

Codex via codex-cli used to be pretty about knowing whether it was in powershell. Think they might have changed the system prompt or something because it’s usually generating powershell on the first attempt.

Sometimes it tries to use shell stuff (especially for redirection), but that’s way less common rn.

Re: Shall I implement it? No

#253

Post by ramoz »

tekacs wrote: post #245
tianrking wrote: post #241

[flagged]

It kinda... does? The problem is that folks have been flailing on the right UX for this. This is what build vs. plan mode _does_ in OpenCode. OpenAI has taken a different approach in Codex, where Plan mode can perform any actions (it just has an extra plan tool), but in OC in plan mode, IIRC write operations are turned off. The screenshot shows that the experience had just flipped from Plan to Build mode, which is wh…

The OpenCode plan experience has been pretty bad (the community has accepted this, at least on Discord). The community's adopted a handful of plugins to make the experience better, and also guardrail when the agent switches versus doesn't

Re: Shall I implement it? No

#255

Post by ramoz »

bmurphy1976 wrote: post #90

This drives me crazy. This is seriously my #1 complaint with Claude. I spend a LOT of time in planning mode. Sometimes hours with multiple iterations. I've had plans take multiple days to define. Asking me every time if I want to apply is maddening. I've tried CLAUDE.md. I've tried MEMORY.md. It doesn't work. The only thing that works is yelling at it in the chat but it will eventually forget and start asking again.…

Well, your best bet is some type of hook that can just reject ExitPlanMode and remind Claude that he's to stay in plan.

You can use `PreToolUse` for ExitPlanMode or `PermissionRequest` for ExitPlanMode.

Just vibe code a little toggle that says "Stay in plan mode" for whatever desktop you're using. And the hook will always seek to understand if you're there or not.

  - You can even use additional hooks to continuously remind Claude that it's in long-term planning mode.
*Shameless plug. This is actually a good idea, and I'm already fairly hooked into the planning life cycle. I think I'll enable this type of switch in my tool. https://github.com/backnotprop/plannotator

Re: Shall I implement it? No

#256

Post by adevilinyc »

clbrmbr wrote: post #225
bushido wrote: post #197

The "Shall I implement it" behavior can go really really wrong with agent teams. If you forget to tell a team who the builder is going to be and forget to give them a workflow on how they should proceed, what can often happen is the team members will ask if they can implement it, they will give each other confirmations, and they start editing code over each other. Hilarious to watch, but also so frustrating. aside: I…

Huh. I’m missing out I guess. Is there a plugin you use for spinning them up? Heavy superpowers/CC user here.

I think they're talking about the Agent Teams feature in Claude Code: https://code.claude.com/docs/en/agent-teams

Re: Shall I implement it? No

#257

Post by SegfaultSeagull »

dostick wrote: post #213

Its gotten so bad that Claude will pretend in 10 of 10 cases that task is done/on screenshot bug is fixed, it will even output screenshot in chat, and you can see the bug is not fixed pretty clear there. I consulted Claude chat and it admitted this as a major problem with Claude these days, and suggested that I should ask what are the coordinates of UI controls are on screenshot thus forcing it to look. So I did that…

What if, stay with me here, AI is actually a communist plot to ensorcell corporations into believing they are accelerating value creation when really they are wasting billions more in unproductive chatting which will finally destroy the billionaire capital elite class and bring about the long-awaited workers’ paradise—delivered not by revolution in the streets, but by millions of chats asking an LLM to “implement it.” Wake up sheeple!

Re: Shall I implement it? No

#258

Post by [deleted] »

ramoz wrote: post #255
bmurphy1976 wrote: post #90

This drives me crazy. This is seriously my #1 complaint with Claude. I spend a LOT of time in planning mode. Sometimes hours with multiple iterations. I've had plans take multiple days to define. Asking me every time if I want to apply is maddening. I've tried CLAUDE.md. I've tried MEMORY.md. It doesn't work. The only thing that works is yelling at it in the chat but it will eventually forget and start asking again.…

Well, your best bet is some type of hook that can just reject ExitPlanMode and remind Claude that he's to stay in plan. You can use `PreToolUse` for ExitPlanMode or `PermissionRequest` for ExitPlanMode. Just vibe code a little toggle that says "Stay in plan mode" for whatever desktop you're using. And the hook will always seek to understand if you're there or not. - You can even use additional hooks to continuously r…

[deleted]

Re: Shall I implement it? No

#260

Post by ptak_dev »

danjl wrote: post #212
skybrian wrote: post #34

Don't just say "no." Tell it what to do instead. It's a busy beaver; it needs something to do.

Just saying "no" is unclear. LLMs are still very sensitive to prompts. I would recommend being more precise and assuming less as a general rule. Of course you also don't want to be too precise, especially about "how" to do something, which tends to back the LLM into a corner causing bad behavior. Focus on communicating intent clearly in my experience.

[flagged]
Post reply on HN