Get started

Run from source

Run the One Connect engine and dashboard from a checkout with the acc command line, try the zero-usage demo, or build the Mac app yourself.

The Mac app isn't released yet. Running from source gives you the same engine and dashboard in a browser, on macOS or Linux, driven by the acc command line and a control-center.yaml file.

Requirements#

macOS or Linux.
Node 24 or later. It runs the TypeScript sources directly, so there is no build step except for the web UI.
pnpm and git 2.38 or later.
The official CLIs of the vendors you want to use, each signed in. See Agents and subscriptions.
Optional: gh for the GitHub tracker, an Obsidian vault, Graphify (uv tool install graphifyy) and Docker for project checks.

Try the demo first#

The demo runs scripted fake agents against a sample repository, with a local tracker, a vault and a code graph. It spends no subscription usage.

pnpm install
pnpm build          # the web UI the daemon serves
pnpm demo           # prints a one-time sign-in link
pnpm demo --reset   # start the demo over

Markers in an issue's description make the fake agents misbehave on purpose, so you can watch the guards work:

Marker	What the fake agent does
`[fake:network-fail]`	Fails with a network error on every attempt
`[fake:network-fail-once]`	Fails once, then succeeds when retried
`[fake:usage-limit]`	Hits a usage limit
`[fake:ask-human]`	Calls `ask_human` and waits for your answer
`[fake:hang]`	Stops producing events, so a stall alert fires
`[fake:no-handoff]`	Finishes without a handoff
`[fake:out-of-scope]`	Edits files outside its allowed paths
`[fake:overage]`	Reports paid overage in use, so the run is stopped

Warning

The demo prints HOST FIXTURE (unsandboxed; disposable tests/demo only). Its checks run directly on the host against the disposable sample repository, which carries an explicit opt-in marker. Never mark a real project as a fixture.

Set up a real project#

Install and build:

git clone https://github.com/krishsah01/One-connect.git && cd One-connect
pnpm install
pnpm build

Find your vendor CLIs. onboard lists every copy it finds on PATH and inside app bundles, with versions and login commands:
```
pnpm acc onboard
```
Copy the example configuration next to your project, or anywhere you like, and edit it:
```
cp examples/control-center.yaml ./control-center.yaml
```
Set at least project.repo, project.checks, project.check_runtime, your agents and the tracker. The configuration reference covers every field.
Check the setup without starting anything:
```
pnpm acc doctor
```
Start the daemon. It prints a one-time sign-in link for your browser:
```
pnpm acc daemon --config path/to/control-center.yaml
```

The dashboard is served at http://127.0.0.1:7317 by default; set server.port or pass --port to change it. To sign a browser in again later, run pnpm acc open.

Everyday commands#

pnpm acc status      # agents, Now/Next and open alerts
pnpm acc open        # one-time sign-in link for a browser
pnpm acc kill-all    # stop every run now, even if the daemon is down
pnpm acc release     # release the kill switch

Agent runs keep going if you stop the daemon, and are reattached on the next start. The full list is in the CLI reference.

Configuration lookup#

acc uses the first configuration it finds: the --config flag, then the ACC_CONFIG environment variable, then control-center.yaml or control-center.yml in the current folder.

Development mode#

ACC_DATA_DIR=/tmp/acc-dev ACC_ALLOW_TEMP_DATA_DIR=1 pnpm acc daemon --config …
pnpm dev:web      # Vite on :5173, proxied to the daemon (set ACC_DAEMON_URL if it is not on :7317)
pnpm test

ACC_ALLOW_TEMP_DATA_DIR=1 is for development only. Normally the daemon refuses data folders inside a temp directory, because the OS wipes them and run evidence would be lost.

Build the Mac app#

Prerequisites: Node 24+, pnpm, Rust, git and Apple's developer tools. You accept Apple's tool license yourself. The build pins Node 24.21.0 for the bundled engine and verifies its checksum against the official release.

pnpm install --frozen-lockfile
cargo fetch --manifest-path packages/desktop/src-tauri/Cargo.toml --locked
pnpm license:check
pnpm desktop:prepare
pnpm desktop:dev      # run the app in development
pnpm desktop:build    # build the .app
pnpm desktop:dmg      # build the .app and a DMG installer

The packaged app is written to packages/desktop/src-tauri/target/release/bundle/. Building a DMG asks once to let the terminal control Finder, which lays out the DMG window.

Tip

If a full Xcode installation has an unaccepted license but the standalone Command Line Tools work, prefix the Cargo and Tauri commands with DEVELOPER_DIR=/Library/Developer/CommandLineTools. This selects those tools; it does not accept any agreement for you.

To publish signed releases, see Releasing the Mac app.