Flightwake

AI coding agents that span multiple sessions have no built-in memory of what they decided, what traps they hit, or what sensitive information passed through the session. Flightwake addresses this by acting as a flight recorder: it installs into the working repository and creates structured Markdown records that the agent writes as work progresses. The command surface is minimal — `npx flightwake init` sets it up, `npx flightwake update` upgrades without clobbering existing configuration. Everything lands in git, so the record history is as durable and auditable as the code itself.

The core differentiating design principle, stated in the README as ‘records follow work, they don’t lead it,’ means the agent is not filling out a ticket before starting — it is generating a contrail as it moves. The framework includes session state tracking, decision and trap logging, multi-session handoff structures, and a sensitive-information self-check at session end. All of this runs in pure Markdown with no runtime dependencies, which means the entire observability layer is inspectable and diffable in any code review.

Flightwake fits teams running strong coding agents in git-centric workflows who need minimal-overhead session continuity and a human-readable audit trail without standing up infrastructure. It breaks for teams who need structured queries across sessions — finding all sessions where a particular file was modified, or alerting when an agent logs a specific decision class — because Markdown files in a directory are the only query surface on offer. Teams with those requirements typically wire Flightwake records into a log aggregator or abandon it for an observability tool that emits structured events natively.

The project ships with MIT license, supports English, Traditional Chinese, Simplified Chinese, and Japanese via the `–lang` flag at init, and the repository includes hooks, skills, snippets, and templates directories that the docs describe as supporting agent workflow obligations. The `CLAUDE.md` file in the repository root indicates the framework is built with Claude Code’s conventions in mind.