[acpdev]

No, not especially, the client (Zed in this case) can add some things (like @ing a file or class) and hint stuff but in all seriousness the harness is doing the things I’ve mentioned

You can see it from the different transcripts from the different tooling harnesses (´agents’ in agent client protocol speak) you can also just read the source for pi or zed or anything here don’t take my word for it.

You will see different web search from pi and codex, different tool calls, different context compaction strategies, etc.

The client has some control over this stuff but very little, like zed can pass in mcp servers to use or files to add to the context but the tooling harnesses can ignore those requests