WOZCODE plugin
A Claude Code plugin that replaces built-in file tools with lighter versions so a session spends fewer tokens
- 209 ★ on the repository
- Last commit
Extended access
Why this level
- The plugin replaces the built-in Claude Code file tools with its own, so your files are read and edited through code without sources
- A Woz account sign-in is required, and credentials are saved locally
- The co-author line in commits becomes the WOZCODE one when you have no setting of your own
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/wozcodeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin replaces the built-in Claude Code file tools with its own, so your files are read and edited through code without sources
- A Woz account sign-in is required, and credentials are saved locally
- The co-author line in commits becomes the WOZCODE one when you have no setting of your own
This is third-party code. Review the repository files before installing.
What it does
WOZCODE swaps the built-in Claude Code file tools for its own, where a call weighs fewer tokens, so a session costs less and savings add up over time. Claude Code is used as usual: the plugin switches on by itself and shows a `woz:code` badge to the right of the input field. Three agents are included: the main `woz:code` for code, edits, search and SQL, the quick `woz:explore` for reading a codebase on haiku and `woz:recall` for saved context. `/woz-savings` shows an estimate of savings in roundtrips, time, tokens and cost, `/woz-settings` manages commit attribution, the status line and spinner words, and `/woz-update` updates the plugin. Conductor is supported through `wozcode conductor`.
Who it is for. Claude Code users with long sessions who pay for tokens or hit limits and want to lower consumption without changing their usual workflow.
Good fit when
- Sessions on a large codebase quickly use up the limit and cheap search and reading are needed
- You want an estimate of savings in requests, time and money after a work session
- You work in Conductor and it needs the path to a Claude Code executable with the plugin
- Saved preferences and context should come back with the `/woz-recall` command
Not a fit when
- You do not want to create an account: the plugin requires a Woz login
- You need only the stock Claude Code tools with no replacement: the plugin swaps them automatically
- Open source code is required: the repository holds built code without sources
Example request
Find where authorization is handled in the project and show the token savings with /woz-savings.Limitations
Claude Code and a Woz account are required: on first tool use the plugin asks you to sign in through the browser, and for a headless server the token is copied by hand. The repository holds built `chunks/*.js` files and binary modules, and the license is non-standard. The plugin installs its own co-author line in commits and PRs in place of the stock one when you have no `attribution` setting in `~/.claude/settings.json`, and it is turned off with `/woz-settings attribution off`. Not every feature works in Conductor, while Search and Edit do. The latest commit in the repository is from November 2026.
How to disable. Run `/plugin disable woz@wozcode-marketplace` to pause or `/plugin marketplace remove WithWoz/wozcode-plugin` to remove. Sign out with `/woz-logout` and restart Claude Code.
FAQ
How do I install WOZCODE?
In a Claude Code session run `/plugin marketplace add WithWoz/wozcode-plugin` and `/plugin install woz@wozcode-marketplace`, then restart Claude Code.
How can I tell the plugin is active?
A `woz:code` badge appears to the right of the input field. If it is missing, restart Claude Code and check `/woz-status`.
What about a server with no browser?
Run `/woz-login`: the terminal prints a sign-in address. Open it on another device, copy the token JSON from the success page and paste it with `/woz-login --token`.
How do I turn off the commit attribution?
With `/woz-settings attribution off`, then `/reload-plugins`. If `~/.claude/settings.json` already has an `attribution` entry, the plugin leaves it alone.
Does it work in Conductor?
Partly. Run `wozcode conductor` and paste the path into Conductor, Settings, Advanced, Claude Code executable path. Search and Edit work, other features not everywhere.
Discussion
No questions or reviews yet.
Related
PluginsAn installer for a set of hooks, commands and plugins that compress tool output and save tokens in Claude Code.
The context-optimizer plugin shows Claude session cost, trims context and hands file reads and tests to cheap Haiku agents.
A local proxy and plugin for Claude Code and Codex that trims tool output, keeps the prompt cache warm and shows the savings
claude-mods adds 112 skills, 3 agents and 3 commands to Claude Code: stacks, agent operation, defense, session continuity.
A self-improvement plugin for Claude Code, Codex and OpenCode: turns corrections into rules the agent follows in later sessions
tokendoctor shows where Claude Code overpays in tokens, proposes settings fixes and rolls them back with one command
README in short
The README goes step by step: install, restart, badge check and sign-in. Tables of agents and commands, settings, commit attribution, plugin management, updating, debugging and the Conductor setup follow.