Local-first encrypted activity recall system with explicit capture controls, pluggable metadata sources, and optional remote AI providers.
- Python 99.4%
- Nix 0.5%
| .github | ||
| docs | ||
| examples | ||
| nix | ||
| rage | ||
| scripts | ||
| src/local_recall | ||
| tests | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .secrets.baseline | ||
| flake.lock | ||
| flake.nix | ||
| HANDOFF.md | ||
| pyproject.toml | ||
| README.md | ||
| requirements.lock | ||
Local Recall
Local-first, encrypted desktop activity recall with explicit capture controls and optional remote AI providers.
Design documents
- v0.1 product requirements
- Threat model and privacy invariants
- System architecture
- Architecture decision records
- Domain models and strategy contracts
- Configuration and privacy profiles
- Capture lifecycle and hard gate
- Bounded in-memory capture pipeline
- Xorg screenshot capture backend
- Local OCR and deterministic redaction
- Authenticated encryption and key providers
- Encrypted storage, catalog, and migrations
- Sanitized audit logging and operational hardening
- Desktop session and metadata strategy resolution
- Local embeddings and encrypted semantic index
- Time-scoped retrieval and record provenance
- Activity clustering and evidence-grounded summaries
- Cited question answering
- Explicit remote provider routing and egress
- CLI controls and query contract
- Recording status indicator
- Authenticated local daemon IPC
- Testing policy
- Installation and first run
- Troubleshooting and safe diagnostics
- Nix packaging
- Local timeline UI
- Zara visual-context integration
- End-to-end scenarios and budgets
- v0.1 release report
Development
Requirements: CPython 3.14.x and uv, or Nix with flakes enabled.
./scripts/check
The canonical command syncs the exact requirements.lock environment and runs formatting, linting, shell linting, strict type checking, all populated test layers, direct failure-propagation checks, repository policy checks, secret scanning, and source security scanning.
nix develop -c ./scripts/check
Development follows red → green → refactor. Required tests may not be skipped or marked expected-failure.
Development is tracked through GitHub issues.