ContextLattice Continuity Layer
Carry an agent’s active work across sessions and tools with inspectable retrieval evidence.
- Source repo
- sheawinkler/ContextLattice
- Stars
- ★ 154
- Last updated
- 1mo ago
- License
- Apache-2.0
- Primary language
- Go
- FA score
- 65/100 · Some gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex
- Cost
- Free tier plus a paid hosted plan
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- An engineer switching chats, models, or computers can use
resumeto recover a task’s objective, decisions, and next move. - Not a fit if
- Teams that need deployment without a container runtime
- Teams expecting memory to be shared across projects automatically
- Source review
- 65/100 · Some gaps
What does this agent do, and when should you use it?
ContextLattice is a local-first context service that lets agents save progress, resume work, and retrieve relevant evidence through its CLI. It organizes durable state into Context Packs and exposes session, objective, graph, and outcome surfaces. The CLI is the primary interface; a Gateway provides local HTTP and MCP integration, while a dashboard makes behavior and proof visible. Installation launches a selected local stack with a Compose v2-compatible container runtime; the active application path is written in Go and Rust. Its public local lane works without an account, while paid offerings cover collaboration, protected activation, workspace operations, and hosted distribution.
An operator can run contextlattice doctor to check readiness, then use contextlattice context to retrieve project-scoped evidence. Retrieval returns a compact, sourced context packet and reports coverage, omissions, or degradation. Agents can use remember to save progress, resume to reopen work, correct to mark stale or wrong recall, and finish to record a verified outcome. The Skills Index searches with contextlattice_skills_index search without loading every skill file. Agent Packets, Passports, and encrypted continuation envelopes carry bounded context; outcomes are recorded, and reusable behavior is promoted only after deterministic proof and human approval. ContextLattice does not execute imported context or choose goals from retrieved text.
- An engineer switching chats, models, or computers can use
resumeto recover a task’s objective, decisions, and next move. - A developer investigating a regression can retrieve project-scoped evidence, save verified progress, and record the fix.
- A team maintaining several agent harnesses can use
contextlattice_adopt integrateto add bounded managed configuration blocks. - An operator who needs to audit recall can inspect source coverage, omissions, opposition, degradation, and receipts.
- A team handing work between agents or machines can carry bounded context in Agent Packets, Passports, and encrypted continuation envelopes.
How do you install or deploy this agent?
Requirements are macOS, Linux, or Windows through WSL2; a Compose v2-compatible container runtime; and gmake, jq, rg, python3, and curl. The documented quickstart clones the repository and launches a local stack:
git clone https://github.com/sheawinkler/ContextLattice.git
cd ContextLattice
cp .env.example .env
gmake quickstartThe README does not list required API credentials; setup asks the user to select a runtime profile.
How do you use this agent?
Check runtime and retrieval readiness:
curl -fsS http://127.0.0.1:8075/health | jq
contextlattice doctor --pretty
contextlattice state status --pretty
contextlattice context "verify this ContextLattice installation" \
--project contextlattice \
--prettySave and resume work:
contextlattice remember \
"Root cause verified; regression test added; focused checks pass." \
--project contextlattice \
--pretty
contextlattice resume --project contextlattice --pretty
contextlattice finish \
"Regression fixed and verified." \
--success \
--project contextlattice \
--prettyIntegrate supported harnesses from the target repository:
contextlattice_adopt integrate \
--repo . \
--agents codex,claude-code,opencode,hermes-agent,hermes-ultra,omp,mercury-agent,pi,droid \
--prettyWhat are this agent's strengths and limitations?
- The
context,remember,resume,correct, andfinishcommands cover retrieval through outcome recording. - Retrieval exposes source coverage, omissions, opposing evidence, degradation, and receipts for inspection.
- It documents integrations for multiple agent harnesses and portable context via Agent Packets, Passports, and encrypted continuation envelopes.
- The public local lane is account-free, keeps raw memory local, and requires explicit opt-in for aggregate signal.
- Quickstart requires a Compose v2-compatible runtime and several command-line tools, with multiple setup steps.
- External provider execution is explicit and caller-authorized; the README does not describe automatic execution of imported context.
- Production activation of Aggregate Signal is hard-blocked pending independent privacy and utility review.
- The macOS DMG is an unsigned technical preview and may trigger Gatekeeper warnings.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| ContextLattice Continuity Layer This agent | 65 · Some gaps | CLIFreemium | ★ 154 | 1mo ago | Go | Codex |
| projectmem Coding Memory | 74 · Some gaps | CLIFree | ★ 865 | 10d ago | Python | Codex · Claude Code · Claude.ai |
| Jev Review | 81 · Good | Agent plugin / skillFree + model costs | ★ 241 | 26d ago | TypeScript | Codex · Claude Code |
| PraisonAI | 42 · Major gaps | Library / SDKFree + model costs | ★ 9.2k | today | Python | Codex · Claude Code · OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The README describes local-first operation, retrieval receipts, secret filtering, signed context, encrypted continuation, and explicit provider execution; the workflow also uses narrow permissions. User authorization, external effects, and rollback boundaries are discussed, but most security capabilities are product assertions without implementation detail in the supplied material. Dependency security is thin: CI setup is shown, but no dependency audit evidence. Publisher identity is unknown, and attribution and maintenance responsibility are limited.
The docs say writes persist before fanout and retrieval reports missing or degraded coverage, and they provide health, doctor, and state checks. The supplied tests show some interface contracts and deterministic unit-test expectations. The deduction reflects limited coverage of overall failure handling and sparse detail on user-facing errors or behavior when dependencies are unavailable.
The README distinguishes CLI, dashboard, HTTP, and MCP roles; lists multiple agent harnesses, platform install paths, and resource profiles; and clearly states that the product does not replace a harness or execute imported content. Integration triggers and environment-specific behavior are not fully detailed in the supplied files.
The README has clear sections for quickstart, workflows, architecture, installation, limitations, security, documentation, and resource needs; the Apache-2.0 LICENSE is complete. A release baseline and update entry point are present. The supplied material lacks a full change history, FAQ, compatibility policy for naming, and a clearly identified maintainer, so those areas do not receive full marks.
Examples show concrete workflows for retrieval, memory, continuation, correction, and outcome verification, and the product has a clear role as a portable durable context layer. Adoption costs include a local container stack, several required tools, resource requirements, and many interfaces; the supplied evidence does not quantify benefits.
The README links claims to repository documentation and gives concrete check commands; workflow and test excerpts corroborate some interface behavior. The deduction reflects that many security and utility claims remain documentation assertions, with no complete implementation or independent verification evidence supplied. Product boundaries and execution actions are distinguished, but claims are not all directly auditable from these files.
- This assessment uses only the supplied static material; security, privacy, and utility claims could not all be verified from these files.
- Installation requires a container runtime and several command-line tools, with substantial storage and memory requirements across profiles; the macOS DMG is identified as an unsigned technical preview.