These are two different layers in the stack that do two different jobs. Agent to agent communication across remote machines is definitely lubricated with tailscale, I’m not sure what value moving up the stack would bring at this stage?

My read here isn’t about connecting to remote machines in the sense of ssh, but presenting a unified view across herdr instances running on multiple remote machines.

This stinks of the same enshittification moves Docker made 10 years ago.

Tailscale's connectivity solutions should allow private connection between agents and between human-agents, by layering on top of the existing connectivity substrate. (I was stating "general impression", and I haven't looked into details yet.)

What I need is to have a general solution to connect me to my agents running somewhere. The motivation is that any hosted solution deprives me of ownership of my data. And I am planning to share more private data with my agents, that cannot be done to have hosted agents today. (I plan to build a hosted solution myself where users can declarative define their own agents, and completely own their own data without my service save anything, I'll ask users to connect to their own storage solutions like Google doc)

I of course can build everything myself. But I think a tailscale offering could be very convenient.

I am guessing cloud flare should have building blocks of their own, but it's a different layer than tailscale's.