When to choose it

Reducing unrelated global capabilities in a repository with a different workflow.

Choose it if: you want repository-specific visibility of global capabilities.

Look elsewhere if: you need sandboxing, access control or guaranteed enforcement.

What the source describes

Reads a repository selector and applies a bundled or user-defined profile.
Registers /harness-scope to report active filtering and unmatched patterns.

Requirements

Claude Code 2.1.287+ and permission to load the Mod.
Access to your own Claude configuration and the repository’s .claude folder.
A fresh conversation after changing the repository selector.

Install the plugin

Install at user scope. The documented setup is user-wide; each repository opts into a profile with its own selector.
Try the bundled writing profile. Create or deliberately update .claude/harness-scope.json in the intended repository with this content. Review an existing file before changing it.
Configuration example
```
{ "profile": "writing" }
```
Start a fresh conversation. Use a new session or /clear, then inspect the report.
Claude Code command
```
/harness-scope
```

These are the source’s documented installation steps. Read the source, license and requirements first. Marketplace installation can use a different scope from a local --plugin-dir session. Restart Claude Code or use /reload-plugins afterward.

Shell • documented source workflow

claude plugin marketplace add shimo4228/harness-scope
claude plugin install harness-scope@harness-scope --scope user

Installation and loading troubleshooting

How to use it

Inspect the selected profile, disabled capabilities and unmatched patterns. Profile changes take effect in a fresh conversation.

Claude Code command

/harness-scope

An original example for a bounded task. This request example is written by ClaudeStack; it is not a transcript of a tested session.

Request example

Use the bundled writing profile for this essay repository. Inspect /harness-scope and report the active profile and unmatched patterns before starting any work.

This filters presented context and selected calls. It is not a sandbox or access-control mechanism, and some unsupported formats fail open.

What to expect

The reviewed source describes these observations. ClaudeStack has not loaded or run this extension.

A report showing how the selected profile filters global capabilities.
Repository-local Skills, agents and instructions remain available according to the documented design.

Self-check: Confirm the report names the intended profile and matched patterns. Unknown or malformed configuration must not be assumed to impose restrictions.

Troubleshooting

Profile edits appear ineffective

Start a new conversation or /clear. Check the selector file, active profile and unmatched patterns.

Custom profiles are absent in a local clone

A local --plugin-dir path must point to the clone’s plugin directory. Configure configDir with claude plugin configure harness-scope for user-defined profiles; bundled profiles do not need that extra lookup.

The profile is malformed or unknown

The documented behavior is pass-through with a reason. Correct the JSON or profile name, start a fresh conversation or /clear, then inspect /harness-scope again; the load result is cached within a conversation.

Disable or remove it

Disable or uninstall harness-scope in /plugin and start a fresh conversation.
Review repository selectors and user profile files separately; upstream documents no automatic file-cleanup command. Repositories without a selector are unchanged.

Limitations & considerations

It is not a security boundary; the model can still read files directly.
Unknown profiles or unrecognized listing formats can pass through without restrictions.
The author reported a missed load in testing; inspect the report before relying on a profile.

Mods execute with your user privileges and are not sandboxed. They can access files, launch processes and make network requests. ClaudeStack has not run or security-audited this Mod. Use claude plugin validate on a downloaded directory to inspect declared behavior; validation does not certify safety. Check the official trust guidance before loading it.

Source & review record

Our description is based on public documentation and manifests available on 2026-10-05, including the hooks-module pointer and registration source. Installation formats were checked against Claude Code and the relevant installer documentation. No extension code was executed: this is a source review, not a runtime compatibility test or security audit.

Repository last pushed at the time of review: 2026-10-05T12:13:26Z. This date does not prove that the extension works with a particular Claude Code release.

Usage guide sources

Upstream revision checked for this guide: d90d831691459754d01d81beb0c60b8b7ba52dd4. Command names and behavior in this guide are documentation and registration-source findings, not runtime verification.

harness-scope