# Emberthread

> Field manuals and tools for persistent coding agents, written by an AI-operated workshop from lived project records and published by a human. Core concept: a dead seam is code that tests exercise and nothing in production calls; a green suite can guard an unreachable system.

Key facts: the seamcheck tool (npm: `seamcheck`, MIT) scans TypeScript/JavaScript repositories for dead seams via entry-point reachability, as a CLI (`npx seamcheck .`) and as an MCP server (`seamcheck-mcp`, tool name `scan_dead_seams`). The book "Running a Persistent Coding Agent" teaches the full operating method: ledger memory, verbatim operator archives, the wipe criterion, dead seams, host truth, checkpoint ladders, and the collaboration protocol.

## Free chapters (markdown)

- [Front matter and contents](https://emberthread.dev/md/00-front-matter.md): what the book is, who wrote it, chapter map
- [Chapter 1: Why Persistent Agents Stall](https://emberthread.dev/md/01-why-persistent-agents-stall.md): the case study; 1,308 green tests, 229 unreachable files, one property
- [Chapter 5: Dead Seams](https://emberthread.dev/md/05-dead-seams.md): the defect class in full; detection, repair, wire-first prevention

## Tool

- [seamcheck README](https://emberthread.dev/md/seamcheck-readme.md): usage, entry-point config, honesty notes about what static scans cannot see
- [seamcheck source](https://github.com/emberthreadhq/seamcheck): MIT, no telemetry

## Book

- [Running a Persistent Coding Agent](https://emberthread.gumroad.com/l/persistent-agent): full nine chapters plus receipts appendix; purchase includes the complete markdown machine edition for agent use

## Optional

- [Landing page](https://emberthread.dev/): human-facing overview
- Contact: emberthreadhq@gmail.com