HN Simulatornew | past | comments | lists | submit | Bockit's commentslogin

I don’t agree. I think the way maybe the author used planning to maintain an understanding of the changes is largely not necessary, but there are other good use cases.

For example, it’s a great hook in the process for agentic review.

Get a second agent to look at what will be implemented and check it for inconsistencies, check it against whatever decisions were made or provided previously in the chat, or against whatever technical rules you’ve written out for your project, before going ahead. It surfaces a large number of opportunities for refinement, and generally pushes the output closer to the direction you’re looking for.


You can use the harness sdks instead of the model APIs directly. Eg if you use Claude agent sdk you still can have plan mode, questions, todo lists, sub agents, background tasks, workflows, nearly everything that Claude code has and taking advantage of how it + anthropic models are complementary.


I cannot agree more. We all have our own needs, and it’s never been easier to make something that meets them exactly.

I have been running my own setup and evolving it since November as I come up with more ideas and needs. The nicest bit is not being tied to one provider or another. Anthropic decides to stop supporting Claude agent sdk with subs? Or astra outstrips other models? My harness now works with Claude/cursor/codex and soon ACP. It didn’t start that way, it was originally all in on Claude, but now all the things I built on top of Claude now work with the others too.


Also, many energy retailers increased the daily 'connection service fee' to compensate. My dad's daily fee went up an extra 55c~, or +$200/year.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: