Eigenwise Toolshed

Claude Code can use a project well and still make you re-teach it the repository, lose a side issue, or repeat the same setup work in every new session.

The same thing happens around model choice and measurement. Expensive models get routine jobs, parallel changes need ownership and verification, and usage stays invisible until a bill or a slow week makes it obvious. Then a plugin install or update has its own friction: what scope did it change, which session needs a reload, and what is safe to turn on?

Toolshed packages those jobs as six independent Claude Code plugins. Use one, a few, or all six. Quartermaster is the guided starting path when you want help choosing, installing, and checking the pieces that fit a project, and it draws on whatever plugins are available on the machine, not only these six.

Sidequest makes it easy for every task recorded as a ticket to survive context compaction and new sessions. The task, instructions, status, and recorded discussion live on a local board, so Claude can pick the work up again after the chat context shrinks. Record decisions, progress, and next actions on the ticket to give the next session a useful starting point.

The six plugins

Problem	Plugin	What it does
A fresh session keeps exploring the same repository	Codebase Mapper	Builds a small project map, loads it at session start, and refreshes the parts touched by changes.
Project rules get forgotten or fill every context	Live Rules	Re-injects matching rules when they apply, so conditional guidance stays out of unrelated work.
Tasks get lost when context compacts or a new session starts	Sidequest	Keeps every recorded task on a local board across context compaction and sessions, assigns ownership, dispatches independent work, and gates results on verification before integration.
You want the models and subscriptions you already have in Claude Code	Model Gateway	Adds supported ChatGPT/Codex and Grok subscription models to Claude Code's /model picker through a local gateway.
You cannot tell where time and tokens go	Observability	Records selected session and tool metadata locally, with per-project opt-in and optional sinks.
Setup, updates, and missing capabilities keep pushing back	Quartermaster	Recommends and installs plugins from any marketplace on the machine for setup, keeps active Toolshed installs current, checks health, and uses bounded session summaries to suggest one approved improvement at a time.

Each plugin has its own install path and guide. None requires the others. Sidequest can route across Claude models on its own; Model Gateway is only needed for its non-Claude routes. Observability is separate from the other plugins and remains opt-in per project.

Start with Quartermaster

Use Quartermaster when you want Claude to look at a project and recommend what fits from the plugins available on the machine, Toolshed and otherwise, installing only what you approve. Before it names a plugin, it can check current sources for whether that plugin is still maintained, whether its cached description is stale, and whether something better fits, including from a marketplace you have not added yet. Searches use generic capability terms, so your project names and file paths stay out of the search engine's logs. Install a plugin directly when you already know which job you want.

From the project directory:

1. Add the marketplace.

   /plugin marketplace add Eigenwise/eigenwise-toolshed
   

2. Install Quartermaster for this project. Project scope is the default example because the choice stays with the repository.

   /plugin install quartermaster@eigenwise-toolshed --scope project
   

3. Activate the installed plugin by reloading plugins or starting a new Claude Code session.

   /reload-plugins
   

4. Run setup and approve the plan item by item.

   /quartermaster:setup
   

5. Setup installs the selected plugins and writes the approved workspace files. When it pauses at the reload boundary, reload plugins or restart Claude Code if the change affects the process environment, then tell Claude continue.
6. Let setup verify the installed plugins and workspace after that boundary. Try one real request in the project before adding more pieces.

Quartermaster's setup uses project scope by default, but Claude Code also supports user and local scopes. Setup can recommend and install plugins from any marketplace. The updater is scoped to Toolshed only: it follows the recorded scope and project path for every active Toolshed install, so a request from one project can update Toolshed installs in other recorded projects too, and it never touches plugins from other marketplaces. Read the update and reload notes before running it.

Install a plugin directly

Use the same marketplace with the scope you want:

/plugin marketplace add Eigenwise/eigenwise-toolshed
/plugin install @eigenwise-toolshed --scope project

Replace `` with sidequest, model-gateway, observability, codebase-mapper, live-rules, or quartermaster. Use --scope user for a plugin you want in every project, or --scope local when it should stay out of shared settings. Reload plugins or start a new session after an install. The plugin guides cover the first workflow for each one.

Updates and reloads

/quartermaster:update-toolshed is the requested updater. It refreshes the Eigenwise Toolshed marketplace and updates all active Toolshed registry installs at their recorded user, project, or local scope and project path. It leaves third-party marketplaces alone. Freshness hooks only report cached availability or loaded-version mismat