@ClaudeDevs The resolution boundary is drawn in the wrong place. This is a stopgap with an intentional gap, not a permanent fix — so
the seam belongs somewhere else.
@mattpocockuk@petermekh I edited grill-with-docs to suggest possible next steps for me. Next session Codex - „great, now I have everything, let me jump straight to next step - implementation”.
It depends on the use case. Most of the "regular" cases are pretty common and they are customized from "the inside". Hermes' building blocks are on the right level of abstraction - gateway, cronjobs, computer use, browser use, etc. Me and the agent then compose them together achieving custom behavior. Also, Hermes is really happy (too happy IMO) to edit itself.
I thought chat memory is important. Its responses must get better if they know my story right?
Me everyday: „Tell me about Foo would it be better than Bar?”
Claude: „Given your work on XYZ the interesting question isn’t…”
😭
@niebezpiecznik Powodem oszustwa jest chciwość, brak edukacji oraz jedzenie majonezu innego niż Kielecki. Facebook co najwyżej jest medium, przez które oszustwo się dokonuje.
All the “well, actually” comments here about why Anthropic is not blocking anything usually miss the point. Attitude and perception matter. Not just the technical facts. Anthropic is not Apple yet. It cannot afford to casually play with developers’ trust and goodwill. We'll see whether they course-correct.
Huh.
So Anthropic doesn’t want an ecosystem built on top of their SDK.
Message received.
Between them banning OpenCode, their hostile stance for OpenClaw, and now this: Anthropic make it they don’t want 3rd parties to build on them.
Bug win for eg Codex, MinMax and others…
I think it is good enough for most purposes but also it’s great that you are concerned about all those things. Being concerned allows us not to blindly accept nor discard the tool but rather decide if it’s good enough for the project we are currently working on. You being concerned additionally produces articles I really appreciate ;)
For example, when I made an LLM do TDD and commit every step, I felt like it was easier for me to review the code later and see the whole process in chunks that fit in my head. This skill was actually helpful and anecdotally produces better code. That's why I got inspired by your post to maybe finish feature development with a "test critiquing" LLM. We'll see if this can improve the work or just add more complexity without any value.
@ploeh I guess in the end I can't trust it 100%. What I can do with all the knowledge I've gained from my experience and posts like this is layer LLM "agent" on top of "agent" and make my final review result in less rework. I usually try different setups and see if it actually helps.