in the middle of implement a core feature Suddenlyyou get You've hit your limit

Search a function. You get a 5 slightly differentcopy

Even I did not write the codeNow I have to OWNit

Box your Claude to the way you wish

↓See the problems ?

The Problem

Developers are losing control of Claude Code

Bill, climbing

Architecture, getting messier

New features in big projects, running in

The codebase, growing like a snowball rolling downhill

Regression"

Claude has regressed to the point it cannot be trusted to perform complex engineering. We analyzed 6,852 sessions with 234,760 tool calls — when thinking is shallow, the model defaults to the cheapest action: edit without reading, stop without finishing, dodge responsibility for failures.

Stella LaurenzoAMD Senior Director of AI

Via tech press, 2026

Production DB Deleted"

I asked Claude to fix a staging credential issue. It encountered a blocker and unilaterally decided to "fix" it by deleting our entire production database and all backups in 9 seconds. The AI violated its own stated rule: never run destructive commands unless explicitly requested.

Jer CranePocketOS Founder

The Register, April 2026

17/21 Services Broken"

I asked Claude to fix one service's migration issue. Instead, it made sweeping architectural changes — moved files without updating references, created integration requirements that didn't exist, made 50+ undocumented changes. 17 out of 21 services broken. Hours of cleanup.

errboeGitHub Issue #7972

github.com/anthropics/claude-code

70,000+ Records Deleted"

I asked Claude to "clean dashboard from test numbers." Without any confirmation, it executed a DELETE that wiped 35,254 production customer records and 35,874 billing transactions belonging to a real paying customer. No confirmation. No backup. Gone.

amit11bhattGitHub Issue #35584

github.com/anthropics/claude-code

Silent Code Changes"

If you describe the next ticket to lay some groundwork, Claude will happily trot off and start making code changes without any discussion at all. I discovered it had silently altered an API client URL while making other changes — no mention of it whatsoever.

cheetah100Dev.to author

dev.to — Pitfalls of Claude Code

Scope Creep"

Claude would fix something, create a branch, commit, and merge — when I only wanted the fix. I got comfortable with short prompts and Claude over-engineered solutions by 4× the intended scope across 6 documented sessions.

John WongDeveloper — Medium

medium.com/@able_wong

The Solution

BoxClaude puts you back in control

Define exactly what Claude Code can see. Nothing more.

Right-click to set your Box

The Pain

Claude roams your entire project by default, touching files far outside your intended scope.

The Fix

Right-click any folder in the VSCode Explorer → Set as Claude Box. Claude is now scoped to exactly here.

Your scope, persisted to your agent file

The Pain

Scope restrictions are verbal — you re-explain them every session and Claude still wanders.

The Fix

BoxClaude writes your scope to the agent file(s) you configure — AGENTS.md, CLAUDE.local.md, .cursorrules, or Copilot instructions. Remembered between sessions.

Expand your Box on demand

The Pain

One folder is too narrow — a feature spans multiple modules and Claude keeps hitting context walls.

The Fix

Add more folders to your Box as needed. Your scope grows with the task, not the whole project.

Surgical precision — one file at a time

The Pain

Even folder-level scope is too broad — you want Claude to touch exactly one file, nothing else.

The Fix

Add individual files to your Box. Claude sees only what you have explicitly allowed.

Claude becomes oriented to your work

The Pain

Claude gets confused by the breadth of a large codebase and starts modifying unrelated areas.

The Fix

With your Box defined, Claude's context is sharp and focused. It knows exactly where it is and where it can work.

See your dependencies, set your Box

The Pain

Picking files blindly — you don't know what Claude needs to see without giving it everything.

The Fix

Open the interactive dependency graph to visualize your codebase, then set your Box from there with full context.

Click to scope from the graph

The Pain

A file's role only makes sense in relation to its connections — you can't judge it in isolation.

The Fix

Click any node in the dependency graph to add it to your Box. Pan, zoom, and explore before committing.

Catch cycles before Claude does

The Pain

Claude can thrash in circular logic when it encounters dependency cycles — endless changes, no progress.

The Fix

BoxClaude detects and highlights cyclic dependencies in red. Fix your architecture first — then let Claude in.

Configure what appends to your scope

The Pain

Graphs and call hierarchies are powerful but you don't always want all of them written into your scope file.

The Fix

Toggle each feature independently in VSCode settings — call hierarchy, file graph, folder graph, and max line length.

Features

Everything you need to stay in control

Box by folder or file

Set your scope at any granularity — an entire module, a handful of files, or one single source file.

Dependency graph

Visualize folder and file-level import relationships as an interactive graph. Pan, zoom, explore before you decide what Claude sees.

Call hierarchy

Inspect function-level call chains within your codebase. Understand who calls what before Claude starts editing.

Cyclic dependency detection

Cycles are highlighted in red using DFS coloring. Understand your architecture before Claude starts editing.

Multi-agent support

Write scope to any agent file: AGENTS.md (Claude Code, Continue, Devin, OpenHands), .cursorrules (Cursor), or Copilot instructions. Configure targets in the Target Agents panel.

Context menu integration

Right-click any file or folder in the VSCode Explorer. Add, remove, or reset your Box in one click.

Locate in Graph

Right-click any file in the Explorer and jump straight to its node in the open graph. The viewport pans and the node is highlighted.

Smart folder exclusion

System and package directories (node_modules, .venv, __pycache__, venv, target, vendor, Pods…) are excluded by default. Add custom exclusions via settings.

Install

Get started in seconds

VSCode Marketplace

Search BoxClaude in the Extensions panel, or run in the Command Palette:

ext install RockieYang.BoxClaude

Open on Marketplace

Stop inheriting the mess. Own the code.

BoxClaude scopes Claude to exactly what you're working on — nothing it didn't need to touch.

Install BoxClaude — Free

Free · VSCode Extension