I think the thesis of Pi is that there isn't much special about agents.
Model + prompt + function calls.
There are many such wrappers, and they differ largely on UI deployment/integration. Harness feels like a decent term, though "coding harness" feels a bit vague.
When I hear "coding agent", I think of both the harness and the LLM as a pair. Like, Claude Opus 4.6 and Claude Code is a coding agent, or Gemini 3 Pro and Pi is a coding agent.
"Harness" is a way to reference the coding agent minus the "LLM" part.
If an agent is an LLM in a loop with tool calls, there are two components: 1) the LLM. 2) The loop with tool calls. That second part could be called the harness.
I think the thesis of Pi is that there isn't much special about agents.
Model + prompt + function calls.
There are many such wrappers, and they differ largely on UI deployment/integration. Harness feels like a decent term, though "coding harness" feels a bit vague.
We all call that a coding agent already
When I hear "coding agent", I think of both the harness and the LLM as a pair. Like, Claude Opus 4.6 and Claude Code is a coding agent, or Gemini 3 Pro and Pi is a coding agent.
"Harness" is a way to reference the coding agent minus the "LLM" part.
If an agent is an LLM in a loop with tool calls, there are two components: 1) the LLM. 2) The loop with tool calls. That second part could be called the harness.
Yes, and sometimes new terms are introduced. This is expected in a new field.
[dead]