A test harness is a collection of software and test data configured to test a program unit by running it under varying conditions and monitoring its behavior and outputs. It automates the execution of test suites, providing the necessary stubs, drivers, and runtime environments so developers can isolate and verify specific code components.
I use opencode (lockedcode is still vaporware), claude, kimi and codex.
And most models. Just no Google models so far, I don't trust them.
There's no particular reason "agent harness" can't have practically the same definition, substituting test-specific concepts for agent-specific ones.
So yes the generel meaning applies to test setup and running and also to the agent cli which is the harness for the model.
Is it about quality issues (lack of guardrails, agent runs dangerous commands)? I have seen first-hand Gemini-cli going out of the project directory and using my home directory as a work area.
Or is it about terms of service?
Or other concerns?
And the lack of ease of use.
Learning when to let go is an incredibly important skill that I have learned way too late in life.