Local-first · cross-provider · evidence-addressable

Know what the agents actually did.

Polylogue turns AI chats, coding-agent sessions, tool calls, results, forks, costs, and reviewed notes into one local evidence system—so work can be searched, audited, and resumed without trusting a transcript summary.

nix run github:Sinity/polylogue -- demo receipts --compact

Evidence pipeline

From provider-shaped artifacts to defensible answers

Raw evidence remains durable. Normalized views and analytics are rebuildable. Human judgment is explicit rather than blended into machine inference.

01 · AcquirePreserve source evidence

Exports, agent files, hooks, browser capture, and telemetry.

02 · NormalizeRecover work structure

Sessions, messages, actions, results, lineage, and authoredness.

03 · DeriveBuild replaceable views

Search, costs, phases, profiles, claims, and optional vectors.

04 · UseSearch, audit, resume

CLI, Python, MCP, daemon API, and local web reader.

What changes

A work archive, not another transcript folder

CLAIMS → OUTCOMES

Audit the work behind the prose

Resolve “tests pass” to the tool call, exit status, duration, and raw result instead of treating an assistant sentence as evidence.

PHYSICAL → LOGICAL

Keep lineage without double-counting

Preserve forks, resumptions, copied prefixes, and subagents while composing the logical work they represent.

HISTORY → HANDOFF

Resume from bounded context

Compile reviewed evidence, omissions, caveats, and user judgments into a reproducible context package for the next agent.

USAGE → ACCOUNTING

Keep cost semantics honest

Separate provider-reported usage, cache lanes, reasoning tokens, catalog estimates, and subscription-credit views.

One archive, several interfaces

Meet the workflow where it already lives

Polylogue ingests provider-specific evidence, but its query and reading model is provider-independent.

Claude CodeCodexChatGPTClaude.aiGeminiHermesAntigravityHooksBrowser captureOTLP-shaped events
CLIPython APIMCPLocal daemonWeb readerMarkdown and JSON exports

See the project as it evolves

The committed Beads graph is rendered as a searchable roadmap with designs, acceptance criteria, dependencies, and closure records.

Open roadmap