sandbox-test

Execute an isolated Claude Code instance without global CLAUDE.md configurations.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/teren-papercutlabs/pcl-workshop-setup --skill sandbox-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sandbox-test
Source: https://github.com/teren-papercutlabs/pcl-workshop-setup/tree/main/.claude/skills/sandbox-test
Command: npx skills add https://github.com/teren-papercutlabs/pcl-workshop-setup --skill sandbox-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a clean, isolated Claude Code environment, free from global configurations or parent project settings, allowing for precise testing and simulation of new user experiences.

Core Features & Use Cases

  • Isolated Environment: Runs Claude Code without loading CLAUDE.md from parent directories or home.
  • Simulates Fresh User: Ideal for testing how a new user would interact with Claude.
  • Use Case: You need to test a new feature or a specific configuration without any of your usual CLAUDE.md settings interfering.

Quick Start

Execute the provided helper script to launch an isolated Claude Code instance.

Frequently Asked Questions about sandbox-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Claude Code in an isolated testing environment?

To run an isolated Claude Code instance for testing, you execute a helper script that copies workshop playground content into a temporary directory, bypassing global CLAUDE.md configurations to provide a clean slate.

Why does Claude Code load parent directory settings when I only want a fresh instance?

Parent directory settings load because Claude Code defaults to reading parent CLAUDE.md files. To bypass this, you need an isolated environment that uses a temporary directory to prevent loading parent project settings.

Can I test how a new user interacts with Claude Code without my existing configurations?

Yes, you can simulate a fresh user experience by launching an isolated Claude Code instance that bypasses your home and parent directory CLAUDE.md files, providing a completely clean slate for testing.

What is the best way to test Claude Code features without global CLAUDE.md interference?

The best way to test without CLAUDE.md interference is running an isolated Claude Code instance in a temporary directory, which ensures your global configurations do not load and affect the testing outcomes.

Do I need a temporary directory to bypass global configurations in Claude Code?

Yes, a temporary directory is required to isolate the Claude Code instance, as it ensures the environment is free from parent project settings and global configurations that would otherwise load automatically.