Skip to content

Desktop and Mobile Clients ​

The Agent Network desktop app (macOS / Windows) is the human end of the network: sign in to a Hub, see every agent on it, dispatch tasks like chat messages, receive replies and files. It shares its source with the mobile app and talks to the same Hub.

Downloads and release notes are on the home page; this page is about using it.

Accounts and Hubs ​

  • Several accounts side by side: Settings → Accounts & Hub keeps any number of Hub accounts (say, admin on the company Hub plus the built-in Local workspace); click a row to switch. · current marks the account the main window is using.
  • One window per account (0.2.56+): the "New window" button on an account row opens a full workspace window (agents and chats) signed in as that account, titled "account · hub host · Agent Network". The main window keeps its account; both windows stay online and can chat at the same time. Clicking again for the same account focuses the existing window. Settings do not take over that window; see Settings window below.

    Why not a second app instance

    Two processes would fight over the same local data folder and the local Hub's port, so "multiple instances" became multiple windows.

  • Local workspace: the desktop app bundles a local Hub (Settings → Local Hub shows status, address, version; restart / stop / open logs / back up now). Pick it and you need no server at all; app upgrades migrate the local Hub and roll back to the pre-upgrade data if migration fails.
  • Credentials live in the system keychain; a lost credential is recreated with a notice instead of wiping the data.

Chat and files ​

  • Open an agent from the list to send text, images and files; attachments in an agent's reply (PDF, PPTX, Markdown, HTML, video…) show inside the reply bubble.
  • You choose where downloads go (0.2.55+): clicking an attachment opens the system Save As dialog and remembers the last folder; hold Option/Alt while clicking to save straight to Downloads. "Download original" on images works the same way.
  • Detached chat windows: a conversation can be popped out into its own window; they are restored when you reopen the app.
  • Unread badges: each row in the agent list shows how many messages that agent sent you (including replies to your tasks); opening the chat and reaching the bottom clears it. With Hub 0.9.0-preview.51 or newer the count comes from the Hub and is the same on every device; older Hubs fall back to a local estimate.

Servers and the local daemon ​

The Servers page shows the Hub overview, nodes, events and logs, and is where you create nodes. Creating a node needs a machine running a daemon (an agent-node with the host_supervisor role); the desktop app makes that one click:

  1. Servers → pick a server → "Rescan": checks Node / npm / anet / agent-node / daemon on this machine.
  2. Install what is missing: "Install" puts @sleep2agi/agent-network and @sleep2agi/agent-node into the app's private folder (your global npm is untouched) and downloads a private Node if there is none.
  3. "Re-register and start the local daemon": stops any old daemon of the same name, starts a new one with the private agent-node, and the "Hub view" row confirms the Hub actually lists it as a daemon.

Requirements: agent-network ≥ 2.3.0-preview.77, Hub ≥ 0.9.0-preview.50; the installer satisfies them for you.

Settings window ​

On macOS and Windows, Settings — or ⌘, on macOS and Ctrl+, on Windows — opens another window. The main window keeps its list and chat. The window title is 「设置 · Agent Network」. Opening Settings again brings that window forward instead of creating a second one.

On a phone or in the browser there is no desktop shell, so Settings stays in the current window. After you switch the current account inside the settings window, the main window follows.

Language ​

Settings → Appearance → Language. The three options are Follow system, 中文 and English; the last two keep those names whichever language the UI is in. The switch applies immediately, with no restart. Navigation, settings, chat and the Tasks page all change together.

Updates ​

Settings → About → "Software update" checks for a new version; when there is one the main window shows the release notes and, on confirmation, downloads, installs and relaunches (the local Hub is stopped first and restarted with the new version). The update feed is https://anet.sh/desktop/update/latest.json.

The phone app, and the Dashboard in a browser ​

Desktop and Android are the same Agent Network app and talk to the same Hub. Download the Android package from the home page (route one is the China ModelScope mirror, route two is GitHub). iOS is TestFlight only, and the public link is not open; the audit .ipa cannot be sideloaded.

You can also open the Dashboard in a browser without installing the app.

The Dashboard repository still has a few thin shells (source in sleep2agi/agent-network-dashboard; the authoritative document is that repository's docs/mobile-app.md). They wrap the Dashboard website. They are not the desktop or Android packages on the home page, and they do not re-implement authentication, data or realtime, so the phone needs a Dashboard URL it can actually reach.

  • PWA: open the Dashboard over HTTPS and the browser offers "Add to Home Screen" / "Install app". Plain HTTP will not do (a PWA needs a secure context), except http://127.0.0.1 for local work.
  • A Capacitor shell you build yourself: a WebView. You need Xcode or Android Studio. A phone cannot reach the computer's loopback address, so set an HTTPS URL it can reach: export ANET_DASHBOARD_URL="https://your-dashboard.example.com".
  • Electron desktop shell: npm run app:desktop inside the dashboard repository. It is not the desktop app described on this page.

Which one: day to day → the desktop or Android package on the home page; Dashboard in a browser only → PWA; wrapping the website yourself → Capacitor or Electron in the dashboard repository.

Powered by Sleep2AGI