How Peacae PM works

Pieces

Diagram

SVGPNG

Piece	Required?	Purpose
Agent-ready project setup	Yes (per repo)	Agent contract + work record in that codebase
Peacae Desktop	Yes	Watch, store, visualize, sync — supports multi-project
Coding agent	Yes	Write plans and status onto that repo’s project board
Peacae Cloud	No	Team accounts, mirrored work, invites, org-wide activity

Working process

This is the daily session order, not first-time setup. Data moves one way: the agent writes the board in the repo, Desktop watches it, Desktop syncs to Cloud. Start the pieces in that same order so you see work as it happens.

Diagram

SVGPNG

1. Launch the local desktop app

Peacae Desktop is the local control plane. It watches the project board, stores it, and shows Board / Tasks / Activity. Launch it first so the watcher is already running when the agent starts writing.

Confirm the project is under Watched projects, the watcher is on, and (if you have several repos) the right one is focused.

If Desktop is not running, the agent can still update the board in the repo — you just will not see it in Peacae until Desktop launches and catches up.

2. Launch or open your IDE

The IDE is where you and the coding agent actually work. Peacae does not replace the IDE. Open the same repo Desktop is watching, then tell the agent to follow the agent instructions.

The agent writes plans and status onto that repo’s project board. Desktop picks those writes up. You stay in the IDE to direct, review, and unblock.

3. Connect with Cloud for sync

Cloud is optional. Connect when you want the team — or another device — to see the same board.

Connect means: sign in on Desktop, link that watched folder to one cloud project, and leave sync on. Desktop — not the agent — pushes board changes. Agents never call Cloud.

Skip this step for solo or offline work. Local Desktop and the board still work. Teammates will not see updates until you connect and sync.

If you…	What happens
Open the IDE first	The agent can write; Desktop catches up when it launches. You miss a live board until then.
Skip Cloud	Local work continues. No shared team view.
Sign in with Desktop closed	Nothing to sync — Desktop is the sync client.

First-time setup (kit, watch path, first prompt) is the happy path below.

Happy path

First-time setup. After that, each session follows the working process (Desktop → IDE → Cloud).

1. Add agent-ready project setup to the project
2. Point Desktop at the project (Settings → Watched projects; add more repos anytime)
3. Tell the agent: Follow the agent instructions and plan X
4. Agent merges features/tasks onto the board
5. Desktop refreshes Board / Tasks / Activity
6. If signed in and linked, work syncs to that folder’s cloud project

Multi-project (IDE ↔ Desktop ↔ Cloud)

Layer	Behavior
IDE / agent	One repo → one project board. No special multi-project IDE protocol.
Desktop	You add each path under Watched projects; optional focus for the board.
Cloud	Each path links to one cloud project. Org Orchestrator shows chronological activity across projects.

Cross-project commands: if you tell the agent to change another repo, it must still create a clear task on the current board (path, why, done criteria), and preferably write real work onto the other repo’s board when that project has agent-ready setup. See Working with coding agents.

Loop

Diagram

SVGPNG

Titles and notes stay short board signals (see Tasks, status & identity) — not full chat, PRs, or logs.

Three stores

Store	Who writes	Why
Project board	Agent	Portable agent write surface (don’t commit the live board; sync via Desktop/Cloud)
Local store	Desktop	Fast UI, works offline, multi-project safe
Cloud	Desktop sync	Team + multi-device

Agents only need the board. Peacae owns the rest.

Agents must never

• Call Peacae APIs or Cloud databases
• Edit Desktop-owned sync bookkeeping
• Replace the board wholesale (always merge)
• Delete rows (cancel / defer instead)
• Clear historical timestamps