Keep task context, project maps and known fixes in one local folder. OpenWolf helps Claude Code, Codex and OpenCode continue work, find relevant code and report recorded token usage.
Lifecycle hooks Claude CodeHooks or plugin Codex CLI, OpenCodeCompatible hooks Grok Build
A coding session can end with useful information still inside the conversation: what changed, which test failed and what to do next. A new session may need that information before it can continue.
OpenWolf stores selected task context beside the project. Agents can recover a checkpoint, search earlier evidence and use the same project map. You can review the saved files instead of relying only on conversation history.
Save the failing test, the files already changed and the next action in a checkpoint. In the receiving Claude or Codex session, inspect and import the handover packet. OpenWolf checks the project and source records and reports changes that may affect the saved context.
This site describes the 2.5.2 release candidate. Check the published npm version before installation. See release checks and limits.
Use your coding agent as usual. OpenWolf runs through the events that your agent supports. Explicit commands are available for handover, review and recovery.
Keep the task objective, open problems and next action in a checkpoint. Supported Claude and Codex hooks can restore saved context at the next session boundary.
Search a project map with file descriptions, symbols and line ranges. Read the relevant part of a file before adding more code to the session.
Identify repeated reads of unchanged files. Supported Claude hooks can shorten selected large command results and keep the full output in a local cache.
Save known fixes and project notes. Archive eligible old sessions with restore pointers. Keep active, latest and pinned notes available.
View available input, cache and output counters by agent and model. Costs use the relevant provider rates. Missing data and pricing assumptions remain visible.
Short notices report useful actions, such as restored context or archived notes. The dashboard keeps activity history, hook health and update status.
Run init from the project directory. It creates .wolf/, connects selected agents and scans eligible source files.
Complete any project or hook trust review required by your agent. OpenWolf can then observe supported session and tool events. Features vary by agent and version.
Open the local dashboard to inspect project memory, handover records, usage coverage and hook health. Costs are API list-price estimates, not subscription charges.
.wolf/ directoryOpenWolf stores project notes, indexes and local runtime data in .wolf/. Review the generated ignore rules and file contents before sharing them.
File descriptions, symbols, line ranges and import relationships. The readable map is stored in anatomy.md.
Session notes and current project status. Keep decisions and unfinished work available for the next session.
Saved task checkpoints and explicit handover packets with source references and project checks.
Known problems, causes and fixes that an agent can search before making a related edit.
Older eligible session notes with verified restore pointers. Active, latest and pinned sessions are retained.
Local usage records and completed OpenWolf actions. The dashboard reads this data and shows its coverage.
Claude Code and Codex use project hooks. OpenCode uses a native plugin. Grok uses enabled Claude-compatible hooks. Cursor, Gemini CLI and Antigravity receive project instructions only.
Memory and indexing run locally without extra model calls. The optional updater contacts npm in the background. A running session keeps its selected runtime.
Install OpenWolf, inspect the project map and check the next session in the dashboard.
Protected durable instructions require independent administrator setup. Regular checkpoints, project maps and activity reporting work without it.