It feels like the pace at which the industry is defining things may be faster than the actual pace of change sometimes.
It feels like the pace at which the industry is defining things may be faster than the actual pace of change sometimes.
> AI client is doing this on its own
Well, the llm api on its own cant do anything other than return a stream of text. The harness takes that and decides, this text is part of the response, this text is an edit tool call, this is a bash call to compile, runs the commands and calls the api again (as long as the llm didn't emit a stop_token. They now have a tool_call token the llm sends in between intermittent responses). And saves a session record to disk so that you can exit and resume the conversation later. It also auto injects things like agents.md etc...
I'd say thats the bare minimum. But then usually also includes hooks, introducing tool calls to allow the main session to launch "subagent", and the bits and pieces pile on....