Most code files are usually too large to 'cat' because of the context size limitations. Even if they fit within the context window, it's waste of API credits to provide it the information that it doesn't need.

Anyways posting this here isn't to get this particular problem solved. It is to see if there is a prompt that can solve it. And this is the only problem I found it not able to solve. It's not like it doesn't know about sed/awk/grep or other Linux tools, it is an expert on most of the common options involving them. My guess is there is something going on with this prompt that just breaks it's 'though patterns' for the lack of a better word :)

> Most code files are usually too large to 'cat' because of the context size limitations

These are command line tools though, not piping it into the llm.

My point though was more about giving it space to reason. It's very important for good results on more complex tasks.

Aah, in case it wasn't clear the use case I'm trying to solve is exactly that: piping shell commands to and fro so that LLM has a bit of autonomy. I know that things like LangChain, AutoGPT exist but frankly they are really poorly thought out and seem to have become kitchen sinks too fast without solving anything properly.

Thank you for the pointer. Very interesting approach. If you don't mind could you suggest some resources where I could learn more about your approach.

Email your GitHub username to my HN username at gmail and I'll add you to the repo so you can take a look!