The pcx CLI

One binary for the daemon and for its clients. pcx –help lists the commands; pcx help <command> explains one.

The daemon

Command	What it does
pcx start	Start the daemon
pcx status	Say whether it runs
pcx stop	Stop it
pcx init	Write a daemon.toml to start from
pcx connect	Connect this daemon to an organization of the cloud (how)
pcx export, pcx import	Archive the memory, or bring an archive in (backup)
pcx migrate	Move the data between RocksDB and SurrealDB
pcx vectorize-all	Embed every session again and repair the message vectors

Clients

Command	What it does
pcx login	Store an API key for a profile (the active one by default)
pcx logout	Forget it
pcx setup	Set up your coding agents, for every project or with --project for this one (how)
pcx mcp-config <client>	Print a client’s MCP entry, to paste
pcx mcp	The stdio MCP bridge to a profile, which client configs run
pcx	With no command: the stdio bridge to the local daemon, started if needed
pcx session, pcx workspace	List and manage sessions and workspaces
pcx card show, pcx card edit	Read or edit the project card or the user card (--user) in $EDITOR
pcx agent "<question>"	Ask the daemon’s agent: one turn, its answer printed as it comes

Profiles

A profile is a backend: a URL and its key. Two always exist:

Profile	Backend
cloud	https://api.pcx.is, the default
self	the daemon of your daemon.toml

pcx login --token <key>             # store the key of the active profile
pcx profile list
pcx profile use self                # switch every client to your daemon
pcx profile add team --url https://pcx.example.com
pcx setup --profile team --client cursor

Profiles are in ~/.post-cortex/config.json and keys in ~/.post-cortex/credentials.json (mode 0600). The profile in use is --profile, else PC_PROFILE, else the active one. PC_URL overrides its URL and PC_AUTH_TOKEN its key; PC_CONFIG_DIR moves both files.

No key is ever written into a client’s config: clients run pcx mcp --profile <name>, which adds the key itself.