This seems a lot like Cloudflare OS (https://blog.cloudflare.com/cloudflare-os/). Is that a fair comparison? If so I'd be keen to understand how this differs aside from not being baked into the Cloudflare estate.
Fair comparisons. Paperclip does the org chart and the orchestration but it depends on other runtimes to actually run the agents. OtoDock also runs on Claude Code and Codex, the difference is the agents run inside it, as persistent processes in a sandbox on your server. Or also you can pair one of your machines with one command and you make any agent run on it with its tools and files synced to the platform, with automatic fall back to the server when the machine is offline. Cloudflare OS I only know from their post, so I cannot compare it properly yet.
The map is mainly there to see the whole installation at a glance. The departments, the agents in them and who delegates to whom. There is a plain grid view as well.
The actual UX of departments is when you put agents in one, delegation between them is configured automatically, so agents can talk to each other and tranfer files between their workspaces.
I work on a realtime collaboration platform, and I've been building something similar for internal use - cool to see your mental model.
Do you find voice mode to be helpful? How do you route to the right agent?
Some minor feedback, but the mobile site is pretty unusable on my device (Firefox, Android). I'm also turned off by the 3d visualizations and ai stuff in marketing (even though it is an AI infra product).
Thank you for checking this out and for your feedback, I will check Firefox now!
The voice mode started from the phone service. I built a full duplex pipeline so agents can connect to frerPBX and use a phone line, and then I ported the same architecture into the dashboard as a voice mode for any agent. Personally I use it for quick things and questions. For real work I use simple dictation or type.
There is no automatic routing. You start sessions with an agent for doing work and if a job needs more than one agent you wire delegation between them so they can talk directly or department head can hand work down and get the result back.
On the 3D map, I was not a fan myself, it came from user feedback but I 've found it useful to see the whole setup at a glance.
This seems a lot like Cloudflare OS (https://blog.cloudflare.com/cloudflare-os/). Is that a fair comparison? If so I'd be keen to understand how this differs aside from not being baked into the Cloudflare estate.
Also seems very similar to Paperclip (https://paperclipai.net/). It's a "company" with an org chart of agents.
Fair comparisons. Paperclip does the org chart and the orchestration but it depends on other runtimes to actually run the agents. OtoDock also runs on Claude Code and Codex, the difference is the agents run inside it, as persistent processes in a sandbox on your server. Or also you can pair one of your machines with one command and you make any agent run on it with its tools and files synced to the platform, with automatic fall back to the server when the machine is offline. Cloudflare OS I only know from their post, so I cannot compare it properly yet.
I need to understand what is the UX of departments. 3d animated wood panels on a forest floor??
The map is mainly there to see the whole installation at a glance. The departments, the agents in them and who delegates to whom. There is a plain grid view as well.
The actual UX of departments is when you put agents in one, delegation between them is configured automatically, so agents can talk to each other and tranfer files between their workspaces.
I think it's just missing the high walls between each.
I work on a realtime collaboration platform, and I've been building something similar for internal use - cool to see your mental model.
Do you find voice mode to be helpful? How do you route to the right agent?
Some minor feedback, but the mobile site is pretty unusable on my device (Firefox, Android). I'm also turned off by the 3d visualizations and ai stuff in marketing (even though it is an AI infra product).
Good luck!
Thank you for checking this out and for your feedback, I will check Firefox now!
The voice mode started from the phone service. I built a full duplex pipeline so agents can connect to frerPBX and use a phone line, and then I ported the same architecture into the dashboard as a voice mode for any agent. Personally I use it for quick things and questions. For real work I use simple dictation or type.
There is no automatic routing. You start sessions with an agent for doing work and if a job needs more than one agent you wire delegation between them so they can talk directly or department head can hand work down and get the result back.
On the 3D map, I was not a fan myself, it came from user feedback but I 've found it useful to see the whole setup at a glance.