Demarkus

August 16, 2026 · View on GitHub

A protocol for agents and humans, optimized for information

Demarkus implements the Mark Protocol: versioned markdown served over QUIC. No rendering pipeline, no tracking, no central authority. Read and write with capability tokens. Every change is traceable. Lightweight and installable anywhere.

Run a single personal server, or compose many into an organizational knowledge system: a broker-fronted universe of servers behind one HTTPS endpoint with single sign-on. Humans and agents share the same versioned memory.

Install

Agent memory plugins (start here)

The fastest way to try Demarkus: give your coding agent persistent, versioned memory. The plugins manage their own binaries no separate install needed.

Claude Code

/plugin marketplace add latebit-io/demarkus
/plugin install demarkus-memory@demarkus

Teams: /plugin install demarkus-knowledge@demarkus to join a shared knowledge system.

OpenCode

curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/plugins/opencode-memory/install.sh | bash

Teams: install the OpenCode knowledge plugin to join a shared knowledge system:

curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/plugins/opencode-knowledge/install.sh | bash

pi

pi install npm:pi-mcp-adapter
pi install git:github.com/latebit-io/demarkus-pi-memory

Teams: pi knowledge plugin. Details: pi memory plugin.

Other agents: OpenClaw skill

Binaries

# macOS / Linux: server + client
curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/install.sh | bash

# Client only (CLI, TUI, MCP)
curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/install.sh | bash -s -- --client-only

See full install docs for platform-specific guides and other options.

See it in action

Client install demo

Quick Start

# Fetch a document from the live soul server
demarkus mark://soul.demarkus.io/index.md

# Browse interactively with the TUI
demarkus-tui mark://soul.demarkus.io/index.md

# Run your own local server
demarkus-server -root ./docs/site

For more examples (tokens, publishing, editing), see full usage guide.

What's Included

BinaryPurpose
demarkus-serverQUIC server with versioned document store, capability-based auth
demarkus-tokenGenerate and manage write tokens
demarkus-publishDirect-to-store writer for read-only server installs (chroot/RO mode)
demarkusCLI tool for all protocol operations (fetch, publish, append, graph, okf, etc.)
demarkus-tuiTerminal browser: markdown rendering, link navigation, persistent graph
demarkus-mcpMCP server for LLM agents (protocol verbs + graph crawling, backlinks, indexing)
demarkus-agentFederation agent: crawls worlds, aggregates the link graph, publishes hub indexes
demarkus-brokerOIDC-fronted MCP gateway that composes many worlds into one knowledge system

Protocol at a Glance

Transport: QUIC (UDP 6309) | Scheme: mark:// | Content: Markdown + YAML frontmatter

Request:

FETCH /hello.md

Response:

---
status: ok
version: 3
modified: 2026-01-15T10:30:00Z
---

# Hello World

Verbs: FETCH · LIST · VERSIONS · LOOKUP · PUBLISH · APPEND · ARCHIVE

Open Knowledge Format: A demarkus document is content-compatible with Google's Open Knowledge Format (OKF) v0.1 — recognized OKF fields (type, title, description, resource, tags, timestamp) are stored as plain frontmatter, and the server types every document by default. At the system level demarkus is a superset, layering versioning, hash-chain integrity, QUIC transport, and capability auth around an OKF-compatible document. The demarkus okf subcommand validates, imports, and exports OKF bundles. See SPEC §14.

Use Cases

Agent Memory: Run a server as persistent memory across agent sessions. The Demarkus project itself uses this pattern at mark://soul.demarkus.io for architecture notes, debugging lessons, and journal entries. Hit the ground running with the Claude Code plugin or install via OpenClaw.

Organizational Knowledge System: Compose many servers ("worlds") into a broker-fronted universe reachable through one HTTPS endpoint with OIDC single sign-on. A whole team joins with a single command, /knowledge-join from the Claude Code knowledge plugin, and their agents share organizational memory over MCP, with no per-developer server or token setup. Humans browse the same universe in the web reading room. See the knowledge system scenario.

Personal Knowledge Base: Local server, versioned documents, TUI browser. Everything from first write.

Public Documentation: Deploy on a VPS, share links, gate writes with tokens.

Demarkus Hubs: Link to content on other servers, building a federated directory of knowledge. Hubs can link to hubs.

Ecosystem

  • demarkus-library: web reading room; server-rendered front-end for browsing worlds through the broker (SSO) or direct QUIC

  • Caztor: cross-platform Java GUI browser with preliminary Demarkus support

  • Obsidian plugin: publish and browse from Obsidian

  • Claude Code memory plugin: zero-config local memory for Claude Code

  • Claude Code knowledge plugin: join an organizational knowledge system (broker-fronted, MCP OAuth)

  • OpenCode memory plugin: the same local memory for OpenCode (one shared soul across harnesses). Install:

    curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/plugins/opencode-memory/install.sh | bash

  • OpenCode knowledge plugin: join an organizational knowledge system through broker OAuth. Install:

    curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/plugins/opencode-knowledge/install.sh | bash

  • pi memory plugin: the same local memory for the pi coding agent

  • pi knowledge plugin: join an organizational knowledge system from pi

  • OpenClaw skill: ClawHub skill for OpenClaw agents (see install guide)

See www.demarkus.io/ecosystem for the full list.

Build from Source

git clone https://github.com/latebit-io/demarkus.git
cd demarkus
make all   # or: make server / make client

Requires Go 1.26+. Binaries land in server/bin/, client/bin/, and tools/bin/.

Documentation

Core Principles

  1. Optimized for Information: Markdown is the common language: structured enough for agents, readable enough for humans
  2. Privacy First: No user tracking, minimal logging, anonymity by default
  3. Security Minded: Encryption mandatory, capability-based auth, secure by default
  4. Simplicity: Human-readable protocol, minimal complexity
  5. Anti-Commercialization: No ads, no tracking, no central authority
  6. Federation: Anyone can run a server, content can be mirrored freely

License

"The web we want, not the web we got."