𝙳☈
@sadasant
Because at the process / runtime level, harnesses are entirely replaceable by models bitter-lesson-style, what’s left, and it should be obvious since OpenClaw, is accessibility and distribution. This is entirely the domain of hyperscallers. Making a harness today with the hypot
@cometaj2 you can even orchestrate them remotely with unix addresses, tunnels, etc. I do this all the time
@cometaj2 usually you’d want an expensive model orchestrating the cheaper ones. You can do this today. You don’t even need MCP. Tell any expensive model to use tmux directly to orchestrate agents in other harnesses (codex, claude, pi, etc). Done
@cometaj2 yes, but a better model will solve the same thing.
You can read my thoughts in more detail here: https://medium.com/sadasant/delete-the-harness-55892f50699f
Trying OpenAI dots like https://x.com/sadasant/status/2106562912118809062/photo/1
OpenAI’s dot is really good. They have artifacts now, besides a fully remote desktop, and you can link your devices. I don't need tailscale nor cloudflare for my personal setup anymore.
The main agent of dot is Astra. It acts as an orchestrator that can spawn indefinite sub-agents. It’s a pattern I was already following.
I'm quite surprised / pleased.
I’m still testing it, but the lack of friction alone seems worthwhile.
While the models can already take control and manage remote desktops, servers, phones, and networks very effectively, I believe the consumer version of this will likely come in waves. Remote computers, enterprise level, perhaps next year. Remote control of phones, for example, pe
@capajj I don’t believe we are talking about the same thing 🤔
@zetalyrae IMO the best way to learn for me is to develop a toy model first, then read as test