Apx

Meet your crew.

APX is an open-source home for your own team of AI agents, running on your machine.
A super-agent that answers you anywhere, project agents that work with your tools, and a browser they drive
while you watch. On your desktop, your phone, your messaging apps and your own server.

Website → · Install · Docs · From v1 · Español · Discord

This is APX v2. It takes over v1's apx command and brings your v1 projects, agents and chats in when you ask; v1's files stay where they were. APX v1 is no longer maintained and stays on the v1 branch.

_{The real app, with a demo office (Acme Store). Every screenshot here is in the theme you are reading in.}

What you can do

• Talk to one super-agent, everywhere. It answers you in the app, on your phone, on Telegram, WhatsApp, Discord, Slack or iMessage, does the work itself or hands it to the right agent, and tells you what happened.
• Keep a crew per project. Agents with a role, an area and their own notes, in a project that can be a business, a side project or a codebase. They delegate to each other and you follow every step.
• Hand off tasks and commitments. A task board with who does what and by when; an agent works it in its own chat and you approve what matters.
• Put work on a schedule. Routines run on their own and only speak up when there is something to say.
• Let them use the web and your computer. The desktop app carries a real browser your agents drive in tabs you can watch, and, when you turn it on, they can use your own apps on macOS and Windows. Passwords and payments stay yours.
• Get widgets and small apps. Ask for a chart or a checklist; an agent builds it and you pin it to the board.
• Bring your models. Your ChatGPT plan, Claude, Gemini, OpenAI-compatible APIs or local models; Claude Code and Codex sessions sit beside your chats.

A project's crew, by area and role

Tasks and commitments from every project

_{One ask: Roby hands the research to Scout, opens the source page in the browser beside the chat and builds a launch board.}

Works today · Foundations in place · On the roadmap

Foundations are not finished services. Exporting an artifact is not a marketplace, and connecting to your own server is not signing into an APX cloud account. Roadmap items describe direction, not availability or release dates.

APX Enterprise (planned)

A separate Enterprise edition is planned. Its scope, licensing, pricing and availability are not announced yet. APX's current open-source edition remains available under the MIT license.

Install

Desktop app (macOS, Windows, Linux): download it from the website or the latest v2 release, open it and follow the setup. The apps are not signed yet: the install guide shows the one extra click macOS and Windows ask for.

From a terminal (detects your system; no root, data in ~/.apx/v2):

curl -fsSL https://apxagent.app/install.sh | bash

irm https://apxagent.app/install.ps1 | iex

On a new graphical computer this installs and opens desktop setup: choose server or client before a core starts. That path does not register a background service. Existing server installations keep updating as servers. apx desktop also installs and opens the app; apx open opens the web panel. Local web users without the app see Install and open, with download progress and their existing setup. It updates itself: the app offers each new version, for the app and for the server it talks to, with one button.

On a server (a VPS, a homelab, no screen): use bash -s -- --server after the pipe (PowerShell: -Server), then apx setup --headless --expose tailscale (or --expose lan) and apx pair to connect your desktop and phone. The desktop app can also install APX on a server for you over SSH. Guide: Run APX on a server.

On your phone: the Android app is in each v2 release (APX-<version>-android.apk); pair it with the code the desktop shows. It installs beside v1's app. Phone guide.

Coming from APX v1

Install v2 and the setup finds your v1 install: it brings your projects, agents, skills, chats and channels in, and leaves v1's files where they were. The install script stops a v1 daemon and takes over the apx command. What carries over.

Documentation and community

• Website and documentation, in English and Spanish
• Discord community
• Report a bug or suggest an improvement

APX runs on your machine. The cloud models and services you connect receive what each request needs; running locally does not mean every model runs offline.

apps/core          the daemon: owns all state; HTTP + WS protocol, agents, threads, browser, channels
apps/terminal      apx, the CLI (speaks only the protocol)
apps/web           the panel (served by the core; also the desktop window)
apps/desktop       Electron: the panel plus the embedded browser the agents drive
apps/mobile        the Expo phone app
apps/docs          the website and documentation
packages/protocol  the single contract: methods, events and client
packages/ui        the design system

pnpm install
pnpm app        # starts the core on 127.0.0.1:7440 and opens the desktop app
pnpm preflight  # privacy + schema checks, lint, typecheck, tests
pnpm verify     # preflight, then end to end (web and desktop) and the lightness budgets
pnpm package    # this OS's desktop installer and server bundle, in out/ (also package:mac, :linux, :win)