My custom harness has a dagger based environment, binary runs in the host, every tool call and file modification creates a new layer in a container - for better session time travel and forking
It may work for some things, but you really want to be wired into that system to do the more interesting things.
I didn't say it couldn't work, it's just way more complexity and effort with IPC or Go than TS. That's one of the reasons harnesses are choosing TS. It's also a very popular language.
My custom harness has a dagger based environment, binary runs in the host, every tool call and file modification creates a new layer in a container - for better session time travel and forking
It may work for some things, but you really want to be wired into that system to do the more interesting things.
I don't understand why dynamically loading code into a Linux process is essential to make this work. Can you explain?
I didn't say it couldn't work, it's just way more complexity and effort with IPC or Go than TS. That's one of the reasons harnesses are choosing TS. It's also a very popular language.