all harness generated messages should follow a strict format #134

New issue

Closed

opened 2026-08-12 09:17:30 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-08-12 09:17:30 +00:00

Owner

example harness generated message:

http 500 internal server error

a very similar sounding message but manually crafted by the agent might be

"the http server had an internal server error"

A few things are important here:

harness generated messages should explicitly be short form variants that semi technical users would understand
in the example example, the quote and code block are literal. some literal examples follow. truly literal.

http 404 not found

eco tool not available

rate limit exceeded

the quote + code block are for visual styling

example harness generated message: > `http 500 internal server error` a very similar sounding message but manually crafted by the agent might be _"the http server had an internal server error"_ A few things are important here: - harness generated messages should explicitly be short form variants that semi technical users would understand - in the example example, the quote and code block are literal. some literal examples follow. truly literal. > `http 404 not found` > `eco tool not available` > `rate limit exceeded` the quote + code block are for visual styling