floppy

Русская версия

floppy is a plugin for Claude Code and Cursor. It gives a coding agent two things: a memory that stays in your repository, and two procedures that use that memory.

• The start procedure tells the agent where the last session stopped.
• The wrap procedure saves what this session learned.
• Three checks keep the procedures correct: a file-list check, a memory linter, and a session lock.

The memory is a set of markdown files. Git holds them with your code. A second machine gets the memory with one clone.

Install

claude plugin marketplace add spscream/ai-floppy
claude plugin install floppy@floppy

Cursor, a local checkout, and what to do when an update copies nothing: Install and init.

Then

Run init once in each repository. It writes .floppy/config, creates the memory index and the state file, and points your AGENTS.md at the conventions. It puts no code in your repository: the commands are run from the plugin.

Six skills: init, agent-memory, start, workstatus, wrap, consolidate. What each one does: The six skills.

Documentation

• Install and init — both harnesses, and the two stale copies that cause no error message
• Config reference — every .floppy/config key, the checkout layout, memory in a separate repository, quota.lock
• The six skills
• The memory model — two namespaces, two axes
• Lessons — what this plugin learned the expensive way
• Among memory systems — floppy against eight other memory systems: what they do well, what was taken, what is deliberately not taken
• The knowledge base — findings about the harness itself, true whether or not you use floppy

The memory model

docs/memory-model.md — the design the paths are moving towards: two namespaces (who may read it), and two independent axes below them (what it is about, where it is true). It is a design, not the current state. Read it before changing any path in the scripts. It exists because the layout was renamed three times in one day, and each rename corrected a model that nobody had written down.

docs/lessons.md — what those renames cost, and why the external layout is derived from the filesystem instead of a config flag. These are lessons about floppy.

The knowledge base

knowledge/README.md — findings about the coding harness itself, true whether or not you use floppy: why a linter walked an empty tree and stayed green, why a suite hangs on an open stdin, where the ban on subagents actually comes from, what /rewind does not restore.

It is separate from docs/lessons.md by audience, and it carries a contract that file does not: every note names the date and environment it was verified against and a command to re-check it, because nobody re-reads a note about somebody else's tool until it has already burned them. python3 scripts/knowledge-rot-check.py lists the ones that have aged out — it reports, it does not gate.

Releases

See CHANGELOG.md. Up to 0.26.0 each release answered one question you could not answer without it: does this update also need a new copy of the shim file in your repository? Since 0.26.0 there is no copy, and the answer is always no.

License

MIT. See LICENSE.