Peacae PM Cloud & sync

Optional team layer: accounts, shared visibility, orgs, and invites. Desktop stays local-first. In the working process, Cloud is step 3: launch Desktop, open your IDE, then connect with Cloud for sync.

Connect means sign in on Desktop, link that watched folder to one cloud project, and leave sync on. Skip it for solo or offline work — local Desktop and the board still work; the team just will not see updates.

Agents never talk to Cloud. They update the project board; Desktop is the sync client.

What you get

Need	Cloud provides
Accounts	Sign up / sign in / password reset
Shared board	Work Desktop syncs shows in the web app
Workspace	Organizations, projects, invites
Org Orchestrator	Chronological activity feed across projects (newest first); Open project for deep work. Pulse strip shows active counts (in progress / in review / blocked)
Public site	Marketing pages, docs, FAQ, blog, changelog, and contact — same Cloud product surface

Public Cloud site

Before and after sign-in, the Cloud site helps people learn and reach the team:

Page	Purpose
FAQ	One searchable list with topic filters (Getting started, Agents & Desktop, Cloud & sync, Account & support)
Contact	Message form for support, billing, partnerships, and general questions
Blog	Short product notes for Cloud and Desktop
Changelog	Release notes, filterable by Cloud / Desktop
Docs	Project setup, agents, Desktop, sync, and workflows — same blue Cloud visual language as the marketing site, with sticky chrome, search, and sidebar navigation

The signed-in dashboard uses the same blue accent language as the public site for primary actions, focus rings, and active chrome. Status greens stay reserved for done / healthy signals.

Sync

Runs when you are signed in, the watched folder is linked to a cloud project, and there are changes. Sync screen shows synced / pending / failed. Offline agents keep updating the board; sync catches up later.

Pending sync is Desktop-local. Cloud badges for “active” projects reflect live task status, not the Desktop push queue.

Workspace

Diagram

SVGPNG

Link each local project to one cloud project. Orgs can have many teams and many projects — create them in Cloud (Organization) or Desktop Settings, then pick the active ones in the workspace switcher. Desktop may watch many folders; each keeps its own link. Invite teammates from Cloud; they sign in, add their checkout under Watched projects, and link the same project.

What Cloud is not

• Not required for local Desktop + agent work
• Not a place agents write directly
• Not a substitute for agent-ready project setup in your repo