The harder problem with personal agents is not getting a model to respond; it is giving agents access to computers and connected apps without surrendering control. This project makes the agent roster feel like a messaging app while keeping the agent processes and conversation data on the user's machine. The key tradeoff is explicit: local control is the default, while cloud desktops and app integrations remain optional services.
What Sets It Apart
- Agents are real processes, not chat personas. It runs supported provider CLIs and streams their activity into a shared interface, so users can see work unfold rather than interact with a simulated bot.
- Permission prompts sit in the workflow. Commands, file edits, and questions can be presented as approval cards. This gives users a point to review actions, though it still requires attention when agents request access.
- Computer and app access are separable. Agents can use local or cloud computer environments and connect to services through OAuth-based integrations. This makes broader tasks possible without making every integration mandatory.
- The architecture is designed for multiple agents. Separate bots can have their own instructions, models, working folders, and conversations, while channels organize them around different contexts.
Great Fit If...
It suits people who want to coordinate several agents from a desktop interface, already have access to supported agent engines, and prefer keeping transcripts and credentials locally. Look elsewhere if you need a fully hosted, always-available service with no setup, or if your workflow depends on mature mobile access: hosted and mobile connectivity is still being built, and Ubuntu support remains beta with platform-specific computer-control limits. Model usage and some optional cloud services may also have separate costs.
Where It Fits
Compared with a conventional single-model chat client, the focus here is agent orchestration: each conversation can map to an actual CLI-driven process with tools and a computer. Compared with fully hosted personal agents, it offers more local control and provider choice, but asks users to manage their own engine accounts and optional service credentials.
