SignetAI | Local-First Memory & Secrets for AI Agents
MEMORY + SECRETS, OUTSIDE THE HARNESS

Own your agent. Bring it anywhere.

Signet is a local-first memory and context layer for AI agents. It keeps the two layers you should not lock inside a harness under your control: memory you can inspect and carry, and credentials models can use without seeing.

$curl -fsSL https://signetai.sh/install.sh | bash
PORTABLE CONTEXT ACROSS THE ECOSYSTEM
01 / 07

A live graph console for your local context

Every memory, source, and claim is inspectable in the dashboard — graph traversal, recall, and repair without a black box.

02 / 07

Memory that maintains itself

When sessions end or go idle, the dreaming loop runs: it distills transcripts into structured memory, extracts entities and claims, supersedes stale context, and keeps the graph current — all without manual saves.

  • Auto-distills idle session transcripts into structured memory
  • Supersedes stale claims with provenance instead of stacking duplicates
  • Runs entirely on your own model and embedding stack
signet — dreaming
Raw SessionDistillationStructured Memoryextract → supersede → propose (evidence-backed)idle consolidation pulse
03 / 07

One command. Your machine.

A single static binary installs the full stack — SQLite workspace, daemon, dashboard — with no cloud account and no vendor lock-in. Your memory is files you can inspect, back up, and move.

  • One-line install, zero cloud dependencies
  • SQLite workspace you can read, back up, and port
  • Local embeddings and recall stay on-device
signet — install
$ curl -fsSL https://signetai.sh/install.sh | bash
✓ binary linked · workspace initialized · daemon started
$ signet status
● daemon running · memory pipeline healthy
04 / 07

Installs under your harness, not instead of it

Hooks, MCP, plugins, and first-party connectors wire Signet into every major agent shell. The same memory and secrets follow your agent from one tool to the next.

  • Claude Code, OpenCode, OpenClaw, Codex, Hermes Agent, Pi, Oh My Pi, Gemini CLI
  • Hooks + MCP + runtime plugins + AGENTS.md / CLAUDE.md sync
  • Memory survives tool churn — switch harnesses, keep context
signet — harnesses
Claude CodeOpenCodeOpenClawCodexHermes AgentPiOh My Pi
05 / 07

Recall with receipts

Transcripts, notes, repos, and documents ingest as ground truth. Every memory points back to the artifact it came from, so recall is inspectable and repairable — never a black box.

  • Ingest transcripts, docs, and repos as durable sources
  • Every memory links back to the evidence that justifies it
  • Purge by source — derived context goes, evidence stays
signet — sources
RecallMemoryTranscriptSrcprovenanceraw evidenceevery memory carries a path back to the artifact that justifies it
06 / 07

Signet's latest tracked MemoryBench run averages 97.6% LongMemEval answer accuracy under the rules profile — one of the only local-first memory systems with SOTA recall on a shared, verifiable eval harness.

97.6%LongMemEval Answer AccuracyMemoryBench LongMemEval under the rules profile — averaged across the tracked local and canary score set.
LOCALNo LLM at Search TimeRetrieval and ranking run entirely on-device; search never calls a model.
RECEIPTVerified on a Shared HarnessScores come from the MemoryBench eval harness with methodology attached — not self-invented numbers.

The rules profile keeps the contract strict: memories are ingested through /api/memory/remember, recalled through /api/memory/recall, and answered from bounded daemon recall results.

Methodology and full results →
07 / 07

Persistent memory in five minutes.

Install the binary, run the wizard, start working. No cloud account, no migration.

$ curl -fsSL https://signetai.sh/install.sh | bash
✓ binary linked · workspace initialized · daemon started
$ signet status
● daemon running · memory pipeline healthy
$ signet setup
agent name [atlas]: signet setup --identity-mode off
✓ harness detected: claude-code · hooks installed
✓ embedding provider: built-in (on-device)
$ signet remember "prefers bun over npm"
✓ memory saved · source-backed
$ signet recall "package manager preference"
→ prefers bun over npm (source: transcript 2026-08-07)