Board, tasks, agent, sync, settings
The desktop UI centers the five working surfaces in the repo: Kanban board, task table, agent activity, sync status, and configuration.
Products
Peacae PM
Local desktop PM for agents, with cloud visibility when the team needs it.
Peacae Desktop watches `.peacae/tasks.json`, normalizes agent-created features and tasks, and stores them locally by default so the builder can keep working without an account.
Peacae PM Cloud is the browser layer: Supabase auth, organizations, projects, team invites, read-only dashboards, reports, and task tables after Desktop syncs the local work rows.
Peacae Desktop
A local app that watches the work file.
Peacae Desktop is the Electron app for daily PM work. Agents write `.peacae/tasks.json`; the desktop app watches that file, normalizes features and tasks, and persists them to the selected backend.
Local operational storage
Local mode runs without account setup and keeps project data on the machine with an embedded database.
File watcher and sync engine
The app uses a file watcher plus a sync engine with retry behavior so task changes can move from local work to shared visibility.
Peacae Cloud
A browser layer for team visibility.
Peacae PM Cloud is a separate Next.js app for account auth and read-only project-management visibility after Desktop syncs local rows to Supabase.
Read-only dashboards
Cloud shows synced tasks, recent activity, feature progress, metrics, charts, reports, and task tables in the browser.
Organizations and projects
The cloud app includes organizations, project workspaces, team members, pending invites, and email invite acceptance.
RLS-scoped Supabase model
Server API routes use Supabase Auth and row-level security so users see only projects and organizations they belong to.
Agent contract
Agents never need Peacae API access.
The shared contract stays simple: agents read `.peacae/config.json`, write `.peacae/tasks.json`, and let Peacae ingest the file into local or cloud-backed views.
Features plus tasks
The JSON shape supports grouped features with nested tasks and standalone tasks discovered during execution.
Timestamp-led status
Planning, start, review, done, blocked, deferred, and cancelled states are expressed through timestamps rather than status theater.
Portable across modes
The same agent workflow works for local desktop, shared team-hosted ideas, and managed cloud visibility.
Product rhythm
One focused path, not a pile of pages.
- 1Point Desktop at .peacae/tasks.json
- 2Let the agent update features and tasks
- 3Review board, task table, activity, and sync status
- 4Use Cloud when the team needs browser visibility
Planned releases
Installers will appear when ready
No placeholder downloads. Real files will include clear versioning and release notes.
Release news will appear in the changelog and docs when downloads go live.
Ship with visibility, not theater
Let the agent task file feed Desktop, then sync to Cloud when the team needs browser visibility.