Get started

Install the Mac app

One Connect for Mac isn't available to download yet. Here is what you will need, and what to expect when the first release ships.

Important

Not available to download yet. One Connect is being built, and it will be free and open source. Follow along on GitHub.

Requirements#

NeedDetails
macOS12 (Monterey) or later
MacApple silicon. Intel and universal builds are not published yet.
gitRequired. It ships with Apple's Command Line Tools (xcode-select --install).
AgentsThe official CLI of each vendor you want to use, signed in with your own account. Setup shows each vendor's install command; you run it yourself.
OptionalDocker Desktop for project checks, containers and local databases; an Obsidian vault; Graphify; Ollama; Tailscale for phone access.

The app bundles its own engine and a checksum-verified Node.js runtime, so you do not need Node installed to use it. It bundles no vendor agent tools and no account credentials.

Download and install#

There is no download yet. When the first release ships, installing works like any Mac app:

  1. Download the DMG from oneconnect.dev.
  2. Open it and drag One Connect into Applications.
  3. Open One Connect from Applications.

Open it the first time#

Until a release is signed and notarized, macOS blocks the first launch:

  1. Open One Connect once and dismiss the warning.
  2. Open System Settings → Privacy & Security.
  3. Under Security, choose Open Anyway next to One Connect, then confirm.

You only do this once. Releases built with the project's Apple Developer ID are notarized and open without a warning, even offline.

What happens on first launch#

  • The app unpacks its engine into a versioned runtime folder and starts it on 127.0.0.1. The window signs in to it automatically over native IPC; you never paste a sign-in link.
  • Without a project, it opens an offline demo: a sample repository with scripted fake agents and GitHub and Linear import fixtures. The demo spends no subscription usage and connects to no tracker. It stays available from the project switcher.
  • First-run setup walks you through appearance, agents, downloads, sign-in, your project and your phone. Nothing is installed on your behalf: setup asks before preparing any vendor download, and you run each command yourself in the built-in terminal.

Updates#

Installed copies check a signed update feed every six hours. When a new release is available, a banner offers Restart to update.

  • Nothing downloads until you press the button.
  • The app stops every project engine gracefully before it relaunches. Detached agent runs keep going and are reattached.
  • After the relaunch, a one-time note confirms the new version.
  • The app accepts only update bundles signed with the project's updater key.
  • Pre-releases are never offered as updates.

Quitting#

  • Closing the window hides it. Engines and agent runs keep working.
  • Quit asks every project's engine to shut down gracefully and closes the native terminals. Agent runs are detached processes: they keep going and are reattached on the next launch. Engines that were running at Quit restart automatically.
  • Stop all in the top bar engages the kill switch for the current project. Projects also has a kill switch for every project at once.

Where your data lives#

WhatWhere
App state~/Library/Application Support/dev.agentcontrolcenter.desktop/
Project registryprojects.json in that folder, readable only by you
Each projectprojects/<id>/state: event database, agent worktrees, Dictionary index, generated database files and secrets
Offline demodemo/
Engine runtimeruntimes/, one folder per version
Startup failuresdaemon.log
API and connector keysmacOS Keychain, service agent-control-center

Your repositories stay where they are. One Connect writes nothing into a repository unless you approve it, and agent work happens in separate worktrees inside the app's data folder.

Uninstall#

  1. Quit One Connect (closing the window is not enough).
  2. Delete One Connect from Applications.
  3. To remove its data too, delete ~/Library/Application Support/dev.agentcontrolcenter.desktop/. This deletes the event logs, run evidence and agent worktrees of every project.
  4. In each repository you used, run git worktree prune to forget the deleted agent worktrees. Agent branches stay until you delete them.
  5. Optionally, remove keys from Keychain Access by searching for agent-control-center.

Vendor CLIs you installed stay installed; remove them with each vendor's own instructions.

Build it yourself#

To build the app from source, see Build the Mac app.

Edit this page on GitHub