Everything on your machine, the way engineers actually work.
The Mac app is the native multi-tab workbench, with a bundled daemon that turns your laptop into a runtime. Use it when you want agents to call your locally-installed Claude Code, Cursor Agent, or Codex — same accounts, same auth, same model contracts you already have.
Why the Mac app
- Multi-workspace tabs. One window, one workspace per tab — switching is instant and each tab keeps its own scroll, selection, and modal state.
- Local CLI runtimes. Your already-authed
claude,cursor-agent,codex,gemini,copilot(and 6 more) become agent runtimes for Concierto. No additional model bills. - Filesystem access. Agents can read and write inside repos on disk, not just in cloud workspaces.
- Offline-tolerant.The workbench keeps working if your daemon is connected, even if the platform’s backend is briefly unreachable.
1 · Install the DMG
Download from concierto.nstack.ai/download. The build is universal (Apple Silicon + Intel). Drag it to Applications, open it, click through the Gatekeeper warning the first time (we’re signed and notarized — it’s the “downloaded from the internet” one-time prompt, not the unsigned dialog).
2 · Sign in
Use the same account as the web app. If you don’t have one yet, the in-app sign-in flow will create it — the underlying platform is the same.
First sign-in shows the same onboarding wizard as the web app with one difference: the plan choice defaults to local runtime, not a paid Stripe plan. You can upgrade to Pro / Connect later from Settings → Billing.
3 · Start the daemon
The Mac app ships with the daemon binary embedded. It starts automatically on first launch and registers itself as a runtime on whichever workspace you create or join. You’ll see a green dot under Settings → Runtimes within a few seconds of launch.
If the daemon doesn’t come up, open Settings → Daemonin the app. The tab shows the daemon’s PID, log tail, and a one-click restart button. The log usually tells you what’s wrong (a port conflict on 8080 is the most common cause).
4 · Pick a local runtime
The daemon auto-detects which of the 11 supported CLIs you have installed. When you create an agent, the runtime dropdown shows them with their detected versions:
claude(Claude Code) — Anthropiccodex— OpenAIcursor-agent— Cursorcopilot— GitHub Copilot CLIgemini— Google Gemini CLIhermes,kimi,kiro,opencode,openclaw,pi
Whichever CLI you pick, Concierto invokes it the same way you would manually — with your existing login session. No model keys to copy around.
If a CLI isn’t detected, the runtimes page shows it greyed out with an Installlink pointing at the vendor’s install instructions. Install it, click Rescan, and it’ll show up.
Multi-workspace tabs
The Mac app gives every workspace its own tab strip. Open as many tabs as you want; cross-workspace navigation is just a click. The CLI guide for tab keybindings lives at Help → Shortcuts (⌘ /) — the common ones:
⌘ T new tab in current workspace
⌘ ⇧ T re-open closed tab
⌘ 1…9 jump to tab N
⌘ \ toggle sidebar
⌘ K command paletteMixing local + hosted
You can run the Mac app andhave a Hosted Pro plan on the same workspace. Concierto’s scheduler then picks the runtime per agent — local daemon for agents bound to one of your CLIs, hosted pool for everything else. Useful when the team has both engineers (laptops always on) and PMs / designers (need cloud agents that don’t depend on their laptop being open).