What is memorythreads CLAUDE.md?

Development instructions for a memory server that stores project information in SQLite, a local database. They cover schema changes, database migrations, and full-text search, which finds words across stored content.

Use them when changing the memory server’s schema, writing data migrations, updating full-text search, or working with project identifiers and names.

They help prevent database changes from breaking existing data or leaving the search index out of sync.

How v3velev/memorythreads configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to v3velev/memorythreads. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/v3velev/memorythreads/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/v3velev/memorythreads

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/v3velev/memorythreads/claude-md/github.svg)](https://agentmods.dev/instructions/v3velev/memorythreads/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/v3velev/memorythreads/claude-md"><img src="https://agentmods.dev/badge/instructions/v3velev/memorythreads/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/v3velev/memorythreads/claude-md"><img src="https://agentmods.dev/badge/instructions/v3velev/memorythreads/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 614 This file is loaded in full into every session.

When invoked 614 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00614	$0.00614
Opus 5.5	$0.00246	$0.00246
Sonnet 5.5	$0.00123	$0.00123
Haiku 4.5	$0.00061	$0.00061

Measured 2mo ago against content hash 6df65f9cf5c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memorythreads CLAUDE.md scanned grade A with 0 findings 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 42 lines

How it starts

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

Memory Server - Development Rules

Schema

The live schema is defined by ensureCanonicalSchema() in memory-schema.js and created automatically on first server/worker start. Update it there, and keep SCHEMA.md in sync.
SQLite cannot ALTER a CHECK constraint - rebuild the table (rename old, create new, copy, drop old) with PRAGMA foreign_keys = OFF around it.
After a schema change: verify with PRAGMA table_info, test INSERTs, and test FTS queries.

Schema Changes / Migrations

There is no auto-run migration system; ensureCanonicalSchema() is the source of truth. Any one-off data migration should be a standalone .cjs script (package.json has "type": "module"), run manually, with a DB backup taken first.
FTS content-sync rebuild must happen OUTSIDE the table-rebuild transaction: INSERT INTO <fts>(<fts>) VALUES('rebuild').

FTS

Triggers must include ALL columns of the FTS virtual table (content AND tags)
After virtual table schema changes: INSERT INTO <fts>(<fts>) VALUES('rebuild')

Project vs ProjectName

project is always a hash - used as DB key
projectName is human-readable - used for semantic search/embeddings
Never embed the project hash for semantic search (garbage similarity scores)

Incremental Sync

incremental-sync.js runs via launchd WatchPaths (30s throttle) on ~/.claude/projects/
Sync state persisted in data/sync-state.json
Turns inserted with embed_status='pending' - worker handles embedding
FTS auto-populated by existing turns_fts_ai trigger on INSERT
Dedup via INSERT OR IGNORE with UNIQUE(thread_id, turn_number)
When modifying turn parsing logic, keep transcript-parser.js, incremental-sync.js, and worker.js in sync

Canonical MemoryThreads

threads.source_kind identifies claude, codex, snapshot, or unknown
threads.source_session_id stores the native session id for that source
threads.canonical_thread_id connects multiple native source streams to one MemoryThread
active_memory_threads stores the selected canonical MemoryThread per app and cwd
Codex Desktop continuation is memory based. It activates a canonical thread, then hooks inject context on each prompt
Do not make Codex and Claude Code share native session files
User prompt and compaction hooks must never emit recovery headers without actual recovered content

Read the full file on GitHub · 42 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.

2mo ago First seen · 42 lines · 614 tokens per session scan A 6df65f9cf5c6

Subscribe to this mod's changes

memorythreads CLAUDE.md is an instructions file published in the GitHub repository v3velev/memorythreads (3 stars, last pushed 4mo ago), licensed MIT. It adds 614 tokens to every session, about $0.0025 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Databases Memory and context

memorythreads CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memorythreads CLAUDE.mdv3velev/memorythreads	Instructions file	3	4mo ago	MIT	A	614	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

memorythreads: Instructions file for Claude Code