I don't think this will work. There are too many tools, a lot of them legacy, and it will be an incredible pain to get them all coordinated on a new standard. Instead I think it'd be better to solve this on the agent side by checking every ~5 seconds what the console output is and sending that, along with the amount of time the process has been running (or perhaps every line could be timestamped?), to a smaller model (like Haiku or GPT5-mini). The model could then provide some input, kill the process or do nothing.
there's a long tail of edge cases where a smaller model does something dumb with input/output, which causes a decent amount of pain to the user (e.g. nodemon, do we stop/do we start?). Coding agent developers can't make an opinion on every possible terminal command
maybe what we're asking for is that terminal commands keep in mind that agents are now the primary users of them, and have a feeling that new packages or commands could get wider adoption if they are better understood by a coding agent
- similar to SEO for LLMs growing in adoption
- documentation sites offering .md file raw for LLMs to ingest easily
These things will make it so that your packages or libs adopted faster
