mo

AI orchestrator review: Paseo paseo.sh/ TBH I've never heard of this app until my harness research had suggested it. At first glance, it seemed very similar to t3.code. Similar layout, similar features, runs 3rd party harnesses. The website puts accent on mobile apps and remote control, which is for me a nice to have, but not the killer feature. Also supports CLI workers + remote control, which looks enticing, but I haven't tried it yet. But then, I realized it has one amazing concept that I haven't seen anywhere before, and that might just be good enough to rethink my workflow. Instead of the usual project -> chat structure, it has a 3 layer structure: project -> workspace -> chat. Workspace can include multiple chats, but can also include terminals and browser windows. And you can set them up in an arbitrary layout. The most interesting part: paseo can inject MCP into the agent context, which allows it to control the terminals and browser windows within the workspace. I can totally see what they're aiming at here. You start a new workspace, and the orchestrator + agent automatically setup a worktree, install your stuff into it, and then boot up dev servers and open browsers in attached terminals. You can tell agents to restart your dev servers or interact with your browsers. When you toggle between workspaces, you toggle between entire entire instances of your work - chats, shells and browsers together. This solves an actual problem, in that it's difficult to toggle between things you're working at among a heap of different browsers, IDE-s, and chats. I vaguely remember people talking about this pain, but I don't remember seeing an actual solution. This feels like one. I'm still exploring here, but as I said, this is the first orchestrator idea good enough to make me consider adapting to it. Downsides? The usual slopbase ills. Eg. voice recording just silently failed for me, no idea why. Plus, it doesn't know how to deal with my symlink-based setup, but none of these apps do, so whatever🤷. So why isn't this app better known around these parts? Marketing, I think. The author ( @moboudra ), doesn't have the same twitter presence and clout as theo and dax. On pure merit, paseo *seems* to be on the same level as opencode and t3.code, and maybe even better. Certainly more innovative.