# presence
[](https://github.com/sara-star-quant/presence/actions/workflows/ci.yml)
[](https://github.com/sara-star-quant/presence/releases)
[](LICENSE)
[](.github/workflows/ci.yml)
[](pyproject.toml)
[](docs/security.md)
**Every Claude Code session starts cold. presence makes the next one start where the last one left off.**
A Claude Code plugin with read-only projections (MCP server, AGENTS.md adapter) so MCP-aware clients (Cursor, Claude Desktop, Continue) and AGENTS.md-aware tools (Codex, Gemini CLI, Windsurf, GitHub Copilot) can also read its accumulated context. Turns every session into part of a continuum.
`presence` adds four things to Claude Code, globally, with one install and zero per-project setup:
1. **Living project model.** Claude builds and reuses notes about each repo it touches. No more re-deriving the same architecture every session.
2. **Outcome telemetry.** Tracks what Claude committed, then watches for reverts, amends, and PR closes. Future sessions see
*(truncated)*
π Trend Scout: sara-star-quant/presence
π What problem it solves
Per-repo memory, outcome telemetry, and a calibrated-confidence gate for Claude Code, with MCP and AGENTS.md projections so other AI coding tools can read its context. Notes survive sessions; success claims need test evidence; your reverts are remembered. Local-only, stdlib runtime.
π Timeline
β Strengths
π‘ What this repo can learn
claude-adapter.py's JSONL parsing β e.g., handling new session event types or extracting richer metadata from Claude Code tool-use blocksmemory-tool add/search/dream) could streamline the UX ofquery-session.pyandlearn.py, making them easier to invoke from hooks or scriptshooks/enforcement chain (e.g., auto-briefing, commit guards, learn reminders)query-session.pyandbriefing.pyas directly callable MCP tools β e.g., a Copilot agent could invoke the briefing lookup in-process rather than shelling out to a subprocess, reducing latency in hook-driven workflowsREADME excerpt
Scouted on 2026-06-03 Β· View on GitHub