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

this is ultimately the right approach. You are going to get more mileage by giving your agent a specific set of tools and operations it can freely access and restrict the rest. Ive also found that any dynamic rejections pollute the context and may lead the agent to go find worse workarounds.

Put your agent in a restricted but fixed environment, and let it do its task. Anything else is mostly theatre and token burn.


A good % of the Google of yesterday is now in working in frontier labs, crushing it.


id' normally hate this but with agents this is awesome


An anthropic employee did a talk earlier this year or last and i think it was said that yeah, they eat it up. Tools to find errors because it is visible is great


Nobody is going to read that though, reading will go the way of code reviews. That’s the problem.


Ever since coding agents came out, It felt a little like we were implementing the self improving lisp programs of old.

This idea almost gets us there.

Could the next step be to make it the program itself?


Well, I've had success loading Lisp programs into Autolith and letting it poke at them from the inside, haha!


At least it’s safe


The state of Agent APIs is bad. completions API (supported indefinitely) but does not support reasoning. OpenAI's reasoning API started out well, but is moving in the direction as described well in the article. Anthropic's messages API is odd. It includes changes such as the recently introduced system messages that can be injected mid turn, but are not supported in all models (sonnet 5). So you are left with a pretty fragmented state. For coding agents, the practical move is to focus on getting it right with one API - eg reasoning, and let the router/provider handle the conversion for you.

Perhaps, there is value in having the de-facto API not be the Reasoning API from OpenAI but something from a neutral party?

Maybe a well defined open standard that facades over these APIs that can gain adoption. For that to happen, the party championing the API needs to have some reasonable traffic capture - OpenRouter perhaps, or a group of such routers coming together? While it wont solve the encrypted payload from the frontier lab problem, it will at least be a backstop in these APIs just becoming a back and forth of encrypted payloads over time.


Seems to be doing too much, a 1 line in the system prompt is all you need. And it works well enough.

“Output tokens are precious, be succinct in your responses. Use ASD-STE100 simplified technical english”


Does this actually work for you? I've tried adding rules in my user profile as well as adding instruction in my CLAUDE.md but my models always eventually go off the rails and start spewing technical jargon in doc strings & descriptions.

At this point I'd do anything to get claude to dumb down and simplify it's explanations in my code, so I'm looking forward to giving this a try and seeing how it goes.


Use gpt ⁵. ⁵or⁶

Clause is a token torment machine that licks your balls while stealing your wallet


yes it does - https://github.com/hsaliak/std_slop/blob/main/system_prompt....

I've added the same thing to the system prompt of the internal agent I wrote for work, which talks to claude models. I have not gone into the details on whether it adheres to the format exactly, but i do see visibly less slop and less marketing nonsense in the Assistant messages.


Let all trust this team to deliver AGI.


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

Search: