ClawUI CLAUDE.md

A project instruction file for ClawUI, an application that displays Claude Code conversations as timelines and lets users continue them. It documents the project’s commands, architecture, data model, and planning system.

In plain words
What is it for?
Use it when developing or maintaining ClawUI, including starting its backend and frontend, building it, running tests, or understanding how session data is organized.
Why use it?
It gives a coding assistant the project context needed to work consistently in this repository. It also records how to build, run, lint, and test the application.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/ccchow/clawui/claude-md
Clone the repo
git clone --depth 1 https://github.com/ccchow/ClawUI
Per session 3,682 This file is loaded in full into every session.
When invoked 3,682 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.03682 $0.03682
Opus 5 $0.01841 $0.01841
Sonnet 5 $0.00736 $0.00736
Haiku 4.5 $0.00368 $0.00368

Measured 2d ago against content hash 1a78f5d39ca9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ClawUI CLAUDE.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **User Agent calls REST API, not internal functions**: The User Agent runs a Claude CLI session that calls the same HTTP endpoints as the frontend via bash/curl. It does NOT import or call internal functions like `crea
CLAUDE.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. It's also a useful reference for contributors — see CONTRIBUTING.md for the full contributor guide.

Project Overview

ClawUI reads Claude Code session JSONL files from ~/.claude/projects/, visualizes them as vertical timelines, and provides interactive continuation via claude --resume -p. Uses a four-layer data model (see docs/DATA-MODEL.md). Also includes a Plan/Blueprint system for structured task decomposition and execution (see docs/PLAN-SYSTEM.md).

Commands

npm run dev              # Start backend + frontend together (concurrently)
npm run dev:backend      # Express on port 3001 (tsx watch)
npm run dev:frontend     # Next.js on port 3000 (binds 127.0.0.1)
npm run build            # Build all
npm run build:backend    # TypeScript → dist/
npm run build:frontend   # Next.js production build
npm run start:backend    # Run compiled backend (node dist/index.js)
npm run lint             # ESLint (backend only)

Tests use Vitest in both backend and frontend:

cd backend && npx vitest run     # Backend tests
cd frontend && npx vitest run    # Frontend tests
cd backend && npx tsc --noEmit   # Type-check backend
cd frontend && npx tsc --noEmit  # Type-check frontend

Architecture

Monorepo with npm workspaces: backend/ (Express) + frontend/ (Next.js).

Four-Layer Data Model

Layer 1 — Raw:        ~/.claude/projects/**/*.jsonl (read-only source of truth)
Layer 2 — Index:      .clawui/index.db (SQLite, incremental sync by mtime+size)
                      + plans, plan_nodes tables (Plan system extension)
Layer 3 — Enrichment: .clawui/enrichments.json (stars, tags, notes, bookmarks)
Layer 4 — App State:  .clawui/app-state.json (UI preferences, recent sessions)

Backend (backend/)

Express server on port 3001. ESM ("type": "module"), uses tsx watch for dev. See docs/BACKEND-ARCHITECTURE.md for detailed file descriptions and security patterns.

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 132 lines · 3,682 tokens per session scan A 1a78f5d39ca9

Subscribe to this mod's changes

ClawUI CLAUDE.md is an instructions file published in the GitHub repository ccchow/ClawUI (3 stars, last pushed 5mo ago), licensed MIT. It adds 3,682 tokens to every session, about $0.0184 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.