The health score and the activity heat map are the reason this is more than a list: they surface the repo you stopped touching three weeks ago, which is exactly the thing conversation memory loses. Everything stays on disk, so there is no account to create and nothing to send anywhere.
A macOS server that stores a JSON record per project — path, status, notes, tasks, detected tech — and answers questions about the portfolio from those records.
- add_project registers a folder, validates the path, and tags what it finds: Package.swift, .xcodeproj, .xcworkspace, or import SwiftUI
- list_projects and get_project_status — the whole roster, or full detail on one entry
- update_project_status keeps status and notes current without a separate app
- search_code_patterns searches tracked projects and the local KnowledgeBase markdown together
- get_project_timeline shows how long a project sat in each status
- get_activity_heatmap answers which projects were hot over the last N days
- get_technology_trends and get_project_health — framework usage across the portfolio, and a 0–100 score with recommendations
macOS 13+ and Swift 6.0+ to build; the host then launches .build/release/project-coordinator. No account and no network calls — records live in KnowledgeBase/projects as JSON, and CPC_KNOWLEDGE_BASE moves that directory somewhere outside the clone. Paths are restricted to a compiled-in allowlist of roots such as ~/Developer and ~/Projects.