Building the persistent, observable, and collaborative context infrastructure that coexists with agents' self-managed memory.
Warning
Work in progress. This is still a very early system. Expect rough edges, missing flows, broken corners, and backward-incompatible changes.
AI coding agents are changing the control plane of software development.
Organizations used to manage only code. Now they also need to manage the rules, constraints, and project context that shape how agents write code.
But an agent's memory lives inside its own runtime — it is not an organizational asset. When context pressure hits, rules get silently dropped, and no one can tell what actually happened.
You own the rules. The agent loads them on demand. Every interaction is traced at rule level. The human stays in control.
- Persistent context at scale. Agents load rules on demand instead of stuffing everything into one context window. Large projects with dozens of rule files do not silently lose instructions under context pressure.
- Organization-owned library. Update a rule once, sync everywhere. No more copying
.cursorrulesbetween repos or hoping everyone has the latest version. - Built-in observability. Every agent interaction is recorded as an attestation event — which constraints were loaded, which were applied, and the agent's self-assessment. The event lifecycle (
user_prompt→discover/load/refer→agent_report) gives you data-driven insight into which rules work and which get ignored. Agent adapters enforce turn closure: the stop hook ensures the agent submits a summary before finishing. - Agent-agnostic adapters. An adapter layer sits between your rules and the agent runtime. Claude Code, Codex, Cursor — same rules, same attestations, no vendor lock-in.
- Self-hosted, zero vendor lock-in. Runs entirely in your infrastructure with PostgreSQL and Zig.
Dashboard view:
Library view:
Analysis view:
Watch a short recording:
tui_dashboard.mp4
For the full documentation site content, start here:
Build from source (requires Zig 0.15+; add zig-out/bin to your PATH for convenience):
git clone https://github.com/lilhammerfun/clumsies.git
cd clumsies
zig build -Doptimize=ReleaseFast
export PATH="$PWD/zig-out/bin:$PATH"Start local PostgreSQL:
docker compose up -dStart the Hub:
clumsies-hubLog in:
clumsies login --hub-url http://127.0.0.1:8400 --username adminBind the current directory to a workspace:
clumsies init --create my-workspaceSync local cache:
clumsies syncInstall the Codex adapter in workspace scope:
clumsies adapt --agent codex --scope workspace --yesLaunch the TUI:
clumsiesTip
For iterative development, just dev spins up the Hub, seeds representative
data, and launches the TUI in one command — no need to run the steps above
manually. Requires just.
MIT


