Agents
What is an agent harness?
An agent harness is the data and tool layer an agent runs against — tables, memory, retrieval, and HTTP — so the loop is not just a prompt file.
Updated
How it works
- Tables hold memory and media.
- Queries are the tools.
- HTTP exposes the same schema to callers who are not the agent.
What it is not
It is not an eval dashboard, and it is not an orchestrator with no store.
agent harness: this, and the thing it is confused with
| This | Not this | |
|---|---|---|
| Prompt file | Not sufficient | The whole product |
| Includes | Store, retrieval, routes | A chain of API calls only |
| You inspect | Rows | A trace UI you cannot join |
Where Pixeltable fits
Pixeltable is that harness when the agent’s tools are queries and inserts on multimodal tables.
Questions
- How does agent harness work?
- Tables hold memory and media. Queries are the tools. HTTP exposes the same schema to callers who are not the agent.
- What is agent harness often confused with?
- It is not an eval dashboard, and it is not an orchestrator with no store.