reference
Skill0 starsChanged 36 days agoMITView on GitHub
Quick reference for the windvane tools (checkpoint, compact_now, memory, log, mine, deps) and what the hooks already do for you; use when banking state, storing a discovery, managing rules or searching past sessions.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- ku5ic/claude-kittheir own version, first seen Nov 4, 2026
- ajitta/know-your-unknownstheir own version, first seen Oct 27, 2026
- yacb2/aidextheir own version, first seen Oct 9, 2026
- open-telemetry/semantic-conventions-genaitheir own version, first seen Oct 8, 2026
- modelstudioai/clitheir own version, first seen Jul 21, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- open-telemetry/semantic-conventions-genai★ 528same name
- modelstudioai/cli★ 369same name
- DeepVista-AI/deepvista-cli★ 9same name
- ajitta/know-your-unknowns★ 2same name
- ku5ic/claude-kit★ 2same name
- yacb2/aidex★ 2same name
- yuri-xyz/skills★ 2same name
- seshachalam-yv/etcd-druid-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
Files
windvane
windvane records the session state itself. Most of what you would otherwise write down is already captured by hooks, so call a tool only for the cases below. The tools are mcp__windvane__<name>.
Checkpoint
The recorder drafts the whole checkpoint: the task, the current step, completed and pending steps, files, warnings and the handoff note. It reads your task list, your edits, your git commits and the closing paragraph of your last reply.
checkpoint(operation="save")with no other argument accepts the draft. This is the normal call; a barecheckpoint()means the same.- A field you pass amends that field and keeps the rest of the draft:
task_description,current_step,completed_steps,pending_steps,files_involved,handoff_summary,handoff_warnings,handoff_context_needed. checkpoint(operation="restore")reads one back.indexpicks an older record, 0 is the newest.checkpoint(operation="list")shows the ring, newest first.
Save when a unit of work has closed. A save never compacts, so save at every step end. The save's reply gives the fill as a percent of the compaction point and, past the person's early mark, puts the compaction to you: call compact_now now and end the turn, and carry on only if the next step needs something only this context holds, such as an edit half made or a result not yet written down. Decide there; if the turn ends without a compact_now, the next turn opens with the same question once. The context notes say where the fill stands, as a percent of the compaction point, three times per cycle: COMPACT AT A STEP END (the person's early mark: no hurry; finish the step, save, and call compact_now if the phase has closed, else carry on), Context pressure (the heads-up: finish the step, start nothing long, compact at its end) and CHECKPOINT NOW (the last call: finish the step in hand, save, call compact_now and end the turn, since auto-compaction is next). A compaction keeps only what was banked.
Compacting
compact_now banks the draft and compacts as soon as the turn ends. It is the only way a compaction starts before Claude Code's own trigger: nothing compacts on a save, and windvane never compacts on its own. Call it when a phase is done and the context is filling, then end your turn at once. After the compaction windvane sends one prompt that resumes the work; the rules and the checkpoint arrive with it in the session-start brief. Left alone, the session runs to the trigger, where Claude Code compacts and the draft is banked as it stands.
Memory
memory(operation="remember", content=...)when something genuinely surprised you about this codebase, a tool or a failure. The recorder captures what it can detect, not surprise. Do not userememberin place of a checkpoint. A fact and the resume state are two records.memory(operation="recall")lists the project memory.searchwithqueryfinds entries.memory(operation="add_rule", content=..., reason=...)stores a permanent rule.list_rulesshows rules with ids.memory(operation="set_detector", memory_id=..., detector={...})makes a rule watch tool calls. A detector holdstools,command(a regex),paths(globs),input(a regex),note, andunattended: "deny"to refuse the call in autonomy mode.{}clears it.modify,delete,promote(to a rule),archive,restoreandacknowledge_mistakeact on one entry bymemory_id, the id shown in brackets.list_mistakesshows the tracked mistakes.
Log
log(operation="mistake", description=..., how_to_avoid=...) records an error the hooks missed. log(operation="decision", decision=..., reason=..., alternatives=[...]) records a choice and why. Failed tools and typed decisions are already captured, so log only what they did not catch.
Mine and deps
mine(operation="search", query=...)finds past conversation on this project.kindnarrows the hits to decision, next-step, error or narration.minealso takesdecisions(when and why something was decided),errors,struggles,replay(withfile_path),timeline,run_report,run_statusandstatus.deps(operation="map", symbol=...)says where a symbol is defined and what imports it.deps(operation="impact", file_path=...)lists what depends on a file before you change it.
Keep the draft accurate
The draft reads your task list and your last reply. Keep the task list current with TaskCreate and TaskUpdate: the open tasks become the pending steps, finished ones the completed steps, and the task in progress the current step. End each reply with a short paragraph that says what is done and what is next. That paragraph becomes the handoff note. Say a step is done only when it is.
Do not call what the hooks already do
windvane does these on its own, so a tool call for them wastes context: the session-start banner with the rules and the restored checkpoint, the pre-edit check of past mistakes, the import and impact checks before an edit, logging failed commands and tests, capturing decisions from the person's prompts, tracking test runs, banking a draft before a compaction, and the background mining of past sessions.
When the run is halted
In autonomy mode a halt denies every tool except checkpoint, a push notification and a few messaging tools. Save a checkpoint that says what was blocking and what a person must decide, send the one-line notification, and stop.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

