Chief
A native Mac workspace for coordinating AI agents.
Get started · Product guide · Development · Apache 2.0
Apple silicon · macOS 26+ · Invited alpha
Chief brings Codex, Claude, Pi Agent, and OpenCode into one workspace. Talk to the Chief assistant to coordinate work, then open each task's conversation to follow the work and give it more direction.
- Ask once, coordinate across agents. Give Chief a task, attach files, and include the full path of any project folder Chief should use. Chief can answer directly or assign work to the agents you've enabled. Working with Chief →
- See what needs you. Overview puts task status, questions, and permission requests on cards. Filter by folder or tag, then open a conversation to step in. Overview →
- Read results and keep going. Read completed replies, revisit earlier runs, send a follow-up, or branch from an earlier run when the agent supports it. Agent conversations →
- Connect the work. Optional Tag Agent groups conversations within each project folder. Super Thread Agent prepares Super Threads with links back to source conversations. Git task cards can show branch and change summaries. Tags, Super Threads, and file changes →
- Give feedback beside the work. Open a web page in a sidecard, annotate an element or area, and send the screenshot and comment to the current agent conversation. Sidecards →
Get started
Chief is available as an invited alpha for Macs with Apple silicon and macOS 26 or later. Get the Chief Alpha disk image and installation guide from your inviter.
- Drag Chief Alpha.app from the disk image into Applications, then open it. The alpha is not notarized; a trusted download may need the per-app Open Anyway exception in System Settings → Privacy & Security.
- Install and configure at least one supported agent on your Mac: Codex, Claude, Pi Agent, or OpenCode. Chief checks which are ready during setup. Each service determines model access and costs.
- Choose the agent that will serve as Chief and the agents it can assign work to. Finish setting up Tag Agent and Super Thread Agent, then click Start using Chief.
- Describe your task in Type a message…. If the task uses a project folder, include its full path. Send the request and open its task card when Chief creates one.
Full installation and first-request guide →
Product guide
Working with Chief · Overview · Agent conversations · Tags, Super Threads, and file changes · Sidecards · Settings
Development
You'll need Apple silicon, macOS 26+, Xcode with the macOS 26 SDK and command-line
tools, and Git. scripts/go.sh locates or downloads the pinned Go toolchain and
verifies the official archive checksum. SQLite uses the system C library through
cgo. Chief development, builds, and packaging do not require Node; external
agent tools manage their own runtime dependencies.
git clone https://github.com/hupao-creator/Chief.git
cd Chief
make build # build the Go runtime and Swift application
make build checks compilation without installing an app. To build, sign, and
open the isolated development app:
make dev
Development and production packaging require a valid Apple Development identity with its private key; there is no automatic ad-hoc fallback. The explicit alpha command needs no Apple account or certificate:
make alpha ARGS='--build-number 1'
This creates a local DMG, installation guide, and checksums under
app/macos/dist/alpha/. Chief Alpha.app uses a separate app identity and data
directory; project folders and external agent sign-ins are shared. The command
does not upload a release. See native build and packaging
for signing, output paths, and distribution constraints.
More build, installation, and runtime commands
Run these commands individually from the repository root as needed:
make runtime # .build/go/chief-runtime
make dev ARGS=--fresh # rotate development data to <profile>.previous and launch
make check # static checks, Go/Swift builds, and routine PBT
make install-hooks # repository-local pre-commit hook
make pack # signed production bundle
make dist # signed production bundle and zip
make install # build/sign and install the production app
make open # open the installed application
make smoke ARGS='--app "/absolute/path/to/Chief.app"'
make install refuses to replace a running installation and requires the signing
identity described above. smoke checks packaged metadata, signatures, linkage,
and resources; it does not launch the app or verify interactions.
The service owns its profile independently of the client connection. A
client disconnect does not cancel accepted work; explicitly quitting the native
app requests a coordinated runtime shutdown. After make runtime, manage an
isolated profile directly:
.build/go/chief-runtime start --data-dir /absolute/profile
.build/go/chief-runtime status --data-dir /absolute/profile
.build/go/chief-runtime stop --data-dir /absolute/profile
Use ./scripts/go.sh run ./cmd/chief-dev --help for development and installation
options. Native OpenCode allowance-data maintenance lives in cmd/chief-maintain.
Find your way around
| Area | Start here | | --- | --- | | Go runtime, services, and plugins | Module map, plugin contracts | | Native application and shared UI | Native module map, build and packaging | | Domain language and state transitions | Domain terms, state machine inventory | | Interaction previews and visual experiments | Demo inventory |
Before changing code, read AGENTS.md and the owning module's README.
Contributor checks and CI define
validation commands and their scope. PBT owns runtime invariants, e2e owns
interactions, and benchmarks own user-experience measurements. make check
runs static/build checks and routine PBT;
it does not run the separate product e2e or
performance measurements. There are no ordinary
example/table unit-test suites.
The fact index connects module contracts to their implementation and verification boundaries; the coverage map records evidence limits. Measurements for another revision do not certify the current build; before/after comparisons need the named baseline available locally.
License
Chief is licensed under the Apache License 2.0. Copyright 2026 hupao-creator.
Third-party materials retain their licenses and attribution notices, including agent skills, fonts and icons, and Unicode data.