ctx — The memory your LLM pretends to have.

Knowledge store with weighted 4-way RRF retrieval, multi-tenant scope isolation, multi-dimensional cyclic temporal gravity, and autonomous cross-referencing. Built for AI workflows that need to remember.

What it does

ctx gives your LLM a persistent, searchable memory. Store knowledge blocks, query them with hybrid retrieval (semantic + bilingual fulltext + trigram), then rerank with multi-dimensional cyclic gravity — each temporal cycle (weekday, month, quarter, week, monthday, seasonal, daily) scored as its own Gaussian field. Queries like "immer dienstags" or "Weihnachten" activate specific dimensions.

Every block carries anchors from both its content (dates mentioned in text) AND its created_at timestamp, so a note about "Meeting am Dienstag" is findable by the day it discusses and the day it was written. Dream Mode runs as a continuous background loop — autonomously discovering relationships between blocks, marking outdated information, and promoting high-quality content. Your knowledge base grows, self-organizes, and stays current.

It speaks MCP, a CLI, and a plain HTTP API, ships an embedded web UI, and isolates multiple tenants down to the individual block. Optionally it passes its models on as an OpenAI-compatible API (/v1) to other programs and other ctx instances, with keys, quotas and its own traffic first (enabling it).

Features

Capability	What it is
4-way RRF retrieval	Reciprocal-rank fusion of semantic + EN/DE fulltext + trigram, type-policy-parameterised — architecture
Cyclic temporal gravity	7 cyclic dimensions with per-dimension Gaussian decay + forward telescoping — architecture
Dream Mode	Continuous autonomous cross-referencing, supersedes detection, parallel race-safe workers — architecture
Block-type registry	Declarative per-type behaviour (retrieval, guard, dream, digest), hot-reloadable — architecture
Multi-tenancy	Three-level tenant/scope/block isolation, grants, quotas, self-service onboarding — multi-tenancy
Issues & forge sync	Per-project issue/comment corpus (own scope = own repo), kanban board, policy-validated workflow-status transitions, and GitHub pull/push sync — api · cli
Sealed secrets	AES-256-GCM provider credentials + trust×sensitivity egress gating — security
Web UI	Embedded Svelte 5 admin SPA: settings, graph, corpus, status, chat, issues, type-registry admin, model API consumers (create with a reveal-once key, revoke) — development
MCP / CLI / HTTP	Three access paths to the same store, OAuth 2.1 for remote MCP — api

Quick install

# Binary (Linux/macOS/Windows): download to a temp dir, verify the signed build
# provenance (GitHub CLI — fails unless this repo's release workflow built the
# file), and only then install
f=ctx-$(uname -s | tr A-Z a-z)-$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')
tmp=$(mktemp -d)
curl -fsSL "https://github.com/GottZ/ctx/releases/latest/download/$f" -o "$tmp/$f" \
  && gh attestation verify "$tmp/$f" -R GottZ/ctx \
  && install -m 0755 "$tmp/$f" /usr/local/bin/ctx

# Or with Go
go install github.com/GottZ/ctx/cmd/ctx@latest

Point the CLI at your ctx host:

ctx init      # config, server + key check, backend pool, Claude Code hooks, statusline

ctx init asks for base URL and API key, writes ~/.config/ctx/config — a mistyped key or one the server rejects is named and asked again, never saved — and checks the server. With a server-admin key it also seeds the backend pool — the chat and embedding backend ctx serves from — when no backend serves those roles yet, and probes the ones it finds; with any other key it skips that step and says so. Re-running it changes only what is missing.

mkdir -p ~/.config/ctx
cat > ~/.config/ctx/config << 'EOF'
CTX_BASE_URL=https://your-ctx-host.example
CTX_KEY=your-api-key-here
EOF
ctx health                                  # DB + backend connectivity
ctx backends seed --host http://gpu:11434 \
  --model qwen3 --embed-model qwen3-embedding   # first backends, non-interactive

Running the server (Go daemon + PostgreSQL 18 + pgvector) is docker compose up -d ctx. Full setup, env vars and Claude Code integration are in operations; building from source in development.

This is the beginning of the README. Read the rest at the original. Read the full README ↗