v6.7.7 · local-first · open source

Capture context.
Compound knowledge.

CarpeOS captures agent sessions with provenance, compounds verified meaning through a post-capture agentic layer (quality-filtered, multi-host), and returns promoted knowledge — with status explicit and the trail intact.

Install CarpeOS Explore the source

Public code. Private knowledge. Not hosted SaaS.

A crystalline knowledge core connected to a network of smaller nodes
promoted Decision with provenance
retrievable Context for the next agent
Append-only events Adjudicated meaning Promoted-only default Rebuildable projections
Why CarpeOS

Your most valuable context should not disappear with the session.

A real decision, a rejected approach, or a bug path often ends up split across chat history, terminal scrollback, and notes. CarpeOS keeps the trail without treating every statement as “memory.”

01

History without trust

Agent transcripts mix facts, guesses, drafts, and abandoned paths.

Keep evidence, claims, acceptance, and supersession as separate records.
02

Session noise floods memory

Not every lifecycle event should become searchable meaning.

Adjudicate first: promote, hold, or reject — default search is promoted only.
03

Knowledge in silos

Each coding tool starts with a different memory of the work.

Capture into a provider-neutral event trail and retrieve through shared interfaces.
04

Notes become authority

Generated documents drift until no one knows what was canonical.

Treat notes, indexes, and context packs as rebuildable projections.
How it fits

Capture once. Adjudicate. Reuse with the trail attached.

Provider hooks feed a private event store. A precision-first adjudicator assigns promote, hold, or reject. Default retrieval returns promoted meaning; MCP, CLI, and projections remain interfaces — not the source of truth.

CarpeOS flow from agent hooks through capture, store, and MCP, CLI, and Obsidian interfaces
  1. 1

    Capture

    Selected lifecycle events enter an encrypted outbox and local store. Host hooks stay fail-open and fast.

  2. 2

    Adjudicate

    Rules and the post-capture agentic plane assign promote, hold, or reject. Verified decision, constraint, and preference meaning can promote without load-bearing HITL; nothing auto-accepts a claim.

  3. 3

    Retrieve

    Default search is promoted and active only. Local hybrid ranking boosts typed promoted units; results stay bounded with provenance rechecked.

  4. 4

    Use

    People and agents work through CLI (including carpeos agentic), local MCP, Obsidian notes, and OKF export projections.

Local interfaces

The same knowledge trail, available where work happens.

Interfaces are local and share the same underlying model. Projections can be deleted and rebuilt; they never become the canonical store.

CLI

Capture, compound, search, and pack context.

Install hooks across hosts, flush the agentic feed, retract with human confirmation, rebuild retrieval indexes, and build bounded context packs from promoted meaning.

carpeos agentic flush · memory search · okf export
MCP · stdio

Nine local tools for agents.

Search, trace, timeline, related records, graph neighborhood, capture, and propose claims through a local stdio server.

memory_search · memory_neighborhood
Agentic layer

Post-capture compound knowledge.

Fail-open feed after capture. Promote when verified for decision, constraint, and preference; near-duplicate promote holds; denser multi-host signal extract. Timer or flush; never auto-creates AcceptanceDecision.

carpeos agentic timer|flush|retract
OKF export

Portable promoted knowledge bundles.

Export a trust-zone-scoped, promoted-by-default OKF v0.2 bundle. Export only — not an import path or canonical store.

carpeos okf export|rebuild
Trust model

A model suggestion is not automatically a fact.

CarpeOS preserves the difference between what was observed, what was proposed, what was promoted into active meaning, and what was later replaced.

  • Default search is promoted and active only; held drafts require opt-in.
  • Capture never calls an LLM; the agentic plane runs after commit, fail-open, with redacted operator JSON by default.
  • Verified decision, constraint, and preference can promote without load-bearing HITL; near-dup promotes hold; AcceptanceDecision is never automatic.
  • Dispositions and events are append-only by policy version; retract uses human-confirmed supersession.
  • Sensitive plaintext stays outside the event body; trust zones stay isolation boundaries.
Evidencewhat can be inspected
Adjudicatepromote · hold · reject
Promotedactive observation
Helddraft for review
Claim · Acceptanceproposed, then decided
Promoted meaning first, with provenance
Get started

Install locally. See the plan before applying it.

CarpeOS requires Node.js 22.22 or newer. The setup flow shows resolved paths and actions before it changes anything. Pin @innocarpe/carpeos@6.7.7 when you want a fixed release.

Open the docs hub Full install guide
terminal 
# install the published package
npm install -g @innocarpe/carpeos

# inspect actions first
carpeos setup plan

# apply runtime + MCP registration
carpeos setup run --apply

# install merge-safe capture hooks
carpeos setup hooks install --apply

Local-first. Interfaces ship on your machine; no hosted Worker, hosted MCP, or SaaS deployment is claimed.

Documentation

Start with the model. Go deeper when you need to.

The website stays intentionally small. Detailed contracts, guides, ADRs, and implementation status live with the public source.

Website guide

Documentation hub

A focused map of architecture, installation, capture, adjudication, retrieval, and MCP references.

Open locally System design

Architecture overview

Follow the event model, trust boundaries, storage layers, and projection rules.

Read on GitHub Agent interface

MCP tool contract

Review the local stdio tools and the contracts agents can rely on.

Read on GitHub
Keep the trail

Give the next session more than a transcript.

Install CarpeOS View source