Loving the capabilities, but the “local agent + web chat” split feels awkward

Site Feedback
1

Hi Anna team,

I’ve been trialing Anna and I really like the core idea: a local agent that can actually execute tasks and work with my files, while the cloud side handles memory and settings sync. That part makes sense on paper.

In practice, though, the two-part experience feels a bit fragmented:

  • I have to download and install a desktop agent, but then I’m primarily interacting through a browser for the actual chat and day-to-day usage.

  • It creates constant context switching (app for status, web for conversation, web for settings), and it makes the product feel “split” rather than cohesive.

  • From a user trust perspective, “the thing that can touch my local files” being separate from “the thing I talk to” can feel less transparent, even if the architecture is technically sound.

To explain what I mean: tools like the Codex desktop app provide a single, unified experience where the chat UI, local file access, and project/workspace context all live in one place on the machine. You can still have account sync and cloud features, but the primary workflow doesn’t require living in a browser.

A few questions / suggestions:

  • Is there a roadmap for a fully integrated desktop app (chat + settings + agent) where the web dashboard is optional?

  • If the web chat is staying, could the desktop app embed the chat UI (or offer a “desktop chat” mode) so users don’t need to bounce between app and browser?

  • Are there specific constraints (security model, deployment speed, enterprise requirements) that made you choose “browser-first chat” instead of a single client?

  • Would you consider an “all-local” mode (with optional sign-in for sync) for users who want everything in one place?

I’m sharing this because the underlying functionality is strong, and a more unified UX would make it feel much more polished and intuitive. Curious to hear the reasoning behind the current design, and what direction you’re aiming for longer-term.

Thanks!

1 Like
2

Thanks for taking the time to write this up, and for being candid about the experience. The “split” you’re describing is real, and it’s feedback we’ve been hearing from other early users as well.

  1. Integrated desktop app is already in progress. ** We’re actively building a fully integrated desktop experience where the app includes the chat UI directly. The goal is that you’ll download and install a single application, chat inside the desktop app, and manage everything there without needing to sign into the web interface for day-to-day use. We’re close on this and plan to ship it soon.

  2. Our direction is multi-device collaboration, not fully local-only. ** Anna is designed around having multiple devices (and potentially multiple agents) working together with shared memory and settings. Because of that, we don’t currently have plans for a “fully local mode” where everything stays on one machine with no cloud component. We know that’s a preference for some users, but our roadmap is focused on cross-device continuity and coordination.

Really appreciate you calling this out. If you’re open to it, we’d love to know what your ideal “single app” workflow looks like (for example: how you expect projects/workspaces, agent status, and settings to be organized in-app), so we can make sure the integrated desktop release solves the right problems.

1 Like