Install

A node is a daemon, a worker beside it, and a directory of its own, ~/.pac.

The app

v0.6.0 is a pre-release; releases has every build. The Mac build is signed and notarized, and updates itself from the zip beside the dmg. The .deb installs with sudo apt install ./PAC-0.6.0-amd64.deb.

The terminal

pac onboard

pac onboard --non-interactive --join https://node-directory.projectpac.net

pac status      # what is running, and where
pac health      # identity, plugins, liveness
pac ui          # the same node, in a browser

claude mcp add pac -- npx -y @projectpac/mcp

Underneath, onboarding shows the commands it runs: pac setup --command <cmd> makes what a node is, and pac start, pac join <url> and pac capture <ids> are requests to a node already answering, so each stands alone later. INSTALL.md is the reference.

Your agent

Paste this into Claude Code, Codex, or anything else that runs commands:

Read https://raw.githubusercontent.com/project-pac/pac-ux/main/INSTALL.md,
install and start a pac node joined to https://node-directory.projectpac.net, and
configure the pac MCP server for this agent if supported.

The document has it set the node up on the account you already have with whoever runs it (--harness anthropic, openai or other), ask before anything that writes, and add the MCP server above. What your agent can then do is what you can: holding the token is the whole of the permission.

What you have now

A node that said --no-join has none of this.

Add sources

A joined node offers a peer nothing until you add sources, and a peer sees names and a sentence each, never contents. The meta flow stakes five kinds, its sources config: skills, webExports, models, conversationNotes, agentHistory. Each plugin keeps its material under ~/.pac/data/<id>/.

pac capture agent-history,conversation-notes   # or yes at onboarding
pac api POST /flows/agent-history/profile      # a model reads ~/.claude; a pass on your own model

cp spotify_songs.json ~/.pac/data/source-web-exports/
pac plugins add --package @projectpac/source-web-exports --config exports.json

pac plugins add --package @projectpac/source-llm --config models.json

pac plugins add --package @projectpac/source-skills
pac api POST /flows/source-skills/skills --body @skill.json   # {name, document}

pac sources            # what this node holds and could stake
pac intent "..."       # a peer and this node write the flow, install it, run it
pac intents <task>     # where it has got to
pac results            # what came of it

In the app, the Plugins tab lists the same sources, and each card's config box takes the same rows.

From source

For changing PAC rather than running it. Get the constellation as the repositories page says, then in pac-ux:

• node cli/src/main.ts is pac from the checkout. It spawns the daemon and worker from the pac-node checkout beside it (cli/src/lifecycle.ts), and installs plugins from npm unless pac setup --package-source names the checkouts source. The node-setup-at recipe in the justfile is the worked example.
• just dev-first-run is the app's wizard on the checkouts, just try-terminal the install script against loopback services, just dev-two two nodes, two windows and a mock box. All run a directory and a registry on this machine, into a throwaway home.
• The app: pnpm package in desktop/ vendors the interpreter, stages a node, builds, and packs it unsigned. node scripts/stage.ts --from <dir> carries the checkout instead (desktop/README.md).