Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
75% Positive
Analyzed from 383 words in the discussion.
Trending Topics
#things#agent#doesn#scripts#don#kept#trying#system#using#agents
Discussion Sentiment
Analyzed from 383 words in the discussion.
Trending Topics
Discussion (9 Comments)Read Original on HackerNews
That's fine. Do what you do. But don't read this article as any sort of science. It's massively opinionated rage-bait.
[0]: https://www.patreon.com/davidgerard
A simple instruction in AGENTS.md fixed that.
I added one when it kept making the same mistake and using things from the wrong library version making compiler errors, adding in the common mistakes pre emptively.
All the scripts are designed to bail quickly. They all create a log in the background instead of blocking. They're all annotated with the necessary comments to keep it on path and locate files, track pratfalls, etc.
So any entrypoint to whatever I'm doing typically starts with one of these scripts. It's heavy handed but orientating your agent for the specific task is better than just dumping a whole set of context that will be ignored if it has nothing to do with your very next command.
Telling it how to do a pull request isn't going to help if you're trying to debug a technical issue.
Either way, you get no visibility or predictability.
Good luck.