It's pretty effective because of the reasons you noted, but there's a composability problem since each MCP has its own sandbox and can't call into the other ones.

IIUC Pi offer a workaround for this, the harness runs the sandbox and populate it with the MCP tools, that way the composability problem is solved and every MCP do not have to implement their own sandbox.

If this is the case: I think introducing tsrx as part of Octane muddies the water a bit and makes me more hesitant to try (even if it is optional).

The idea to make tsx files more readable may be interesting but in that case it should go into its own separate project, and maybe just put a lang toggle in Octane docs and a page about tsrx compat, that way if people are intrigued by the new syntax they can just look it up but the docs stay focused.

- how do/would you add the WebSearch tool to your harness? pay for a separate service or does deepseek offer something with their subscriptions?

- do pi/opencode support pasting images in prompts?

- how do you handle reading images? deepseek is not multi modal IIRC? do you pay for another model and route to it?

Any of these missing would really annoy me in day to day use...