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

It sounds like what they are primarly aiming for is introducing backpressure in their own review pipelines.


They have for sure improved the safeguard classifier. I have a coding agent guard OSS tool [1] and I use Claude to build it. When Fable first came out, I was simply unable to do any work with it. Nowadays their classifier triggers but very rarely.

[1]: https://github.com/manuelschipper/nah


I have used Fable, Astra, Opus 5 and Sol 5.6 in Claude Code and Codex heavily since each of these have been released. Recently, I settled for Sol 5.6 as my daily driver, but with this release Opus 5.5 might be the one.

Fable is on a class of its own when it comes to coding and orchestration, but it runs out pretty quick and is prohibitively expensive and slow. For me, Astra wasn't as good of an upgrade from Sol when it comes to coding and orchestration, and it runs out pretty quick too. Opus 5 had so much potential but was such a pain to talk to, so I only had other agents delegate to it.

Given this, I kept coming back to Sol 5.6 as my daily driver (with consultations from Fable and Astra when available). Sol has an autistic character that smells like RL deepfry, which can be annoying, but it is nonetheless predictable, communicates more plainly than Claude, and is good at code and orchestration.

But this Opus 5.5 might just be it. Fable-level performance that's cheaper and faster, and communicates plainly and briefly. If it pans out in practice, I might just have a new daily driver and it might be time to raise the bar for what can be achieved.

I'll try out the new Sol 6, though Opus 5.5 seems to beat that release fair and square (at least on paper)

I'm also glad we are paying attention now to the experience of using a model, not just how good it is at 'x' class of tasks.


I’m working on nah, a coding agent guard to block catastrophic tool calls.

It’s easily extensible, has a nice simple TUI, and is resilient to an adversarial agent that tries to remove the guard.

https://github.com/manuelschipper/nah


I’m working on “nah” [1] an agent hook guard that blocks catastrophic agent actions like filesystem destruction, secrets exfiltration, and git disasters.

All the agent hook guards I’ve seen can be easily removed by agents (and they often do so they can get going with the task). I made mine harder to remove, and I’m working on making it impossible.

I also made “nah” easily extensible. Just point your agent to the docs which ship with the CLI, and ask it to build a custom guard.

I’m working on strong Python and Typescript pseudo-interpreters so I can detect disasters in inline code with less false positives. Bash parser is already very strong.

This is a side-project that I want to be proud off. I spend a lot of time designing, not just coding.

[1] nahguard.ai


Love the vibe of the website!


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

Search: