Skip to main content
HTTP status: 400

Error message

Example: caller-declared tool names collide with the tools the harness provides (bash, file_read, file_write, job_monitor, sleep, wait_for): sleep.

When this error occurs

POST /agents/conversations or POST /agents/conversations/{id}/runs with config_override was called with a tools[].name that matches one of the platform-provided harness tools. Those names are reserved so the model always sees the platform’s implementation for that name — a sandbox tool, or one of the waiting primitives (sleep, job_monitor, wait_for).

How to fix

Rename the caller-declared tool to something outside the reserved set. Any dash-free name that is not one of the harness tools is accepted; the harness set is small and stable.