Projects

Lightweight registry of active multi-session work.

Status legend

Status: active
Goal: keep the local OpenClaw setup stable, safe, and low-friction for daily use
Current threads:
- improve subagent / ACP reliability
- maintain memory hygiene and retrieval quality
- keep backups, search, and messaging paths healthy
Related memory:
- memory/incidents/
- memory/ops/
- memory/tasks.json

Status: watch
Goal: build a useful low-noise daily brief flow, likely calendar-first
Current state:
- direction chosen on 2026-03-10
- no calendar backend configured yet
- next decision depends on which calendar backend Will actually uses
- follow-up task added on 2026-03-11 to set up calendar access/backend
Related memory:
- memory/2026-03-10.md
- memory/tasks.json

Status: watch
Goal: gradually fill the most useful remaining LAN/local capability gaps without adding junk infra
Candidate additions:
- calendar access/backend
- email/inbox access
- broader personal document/search corpus
- more homelab observability/status endpoints
- stronger GitHub tooling
- Google Workspace access
- local OCR / PDF extraction
- notes-system connector
- carefully scoped secret-manager integration
- Home Assistant / smart-home integration
- structured data connectors where useful
Related memory:
- memory/tasks.json

Status: active
Goal: get Flynn's council pipeline working against real models, then make it delegable from zap
Current state:
- tracked as a task in memory/tasks.json
- implementation notes live in memory/plans/flynn-council-fix.md
Related memory:
- memory/plans/flynn-council-fix.md
- memory/tasks.json

Use this file for cross-session project state humans may want to skim quickly.
Keep detailed steps/checklists in memory/plans/ or memory/tasks.json.
Don’t create a project entry for every tiny task; this is the bigger-picture map.