perry-workspaces

Create and manage isolated Docker workspaces on a tailnet.

Updated Jan 22, 2026

Search Tags:#Claude Code #CLI #workspace #docker #OpenCode #development-environments #tailnet

Ready to run

npx skills add https://github.com/gricha/clawdbot-skills --skill perry-workspaces

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: perry-workspaces
Source: https://github.com/gricha/clawdbot-skills/tree/main/perry-workspaces
Command: npx skills add https://github.com/gricha/clawdbot-skills --skill perry-workspaces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perry addresses the challenge of provisioning isolated development environments quickly by spinning up Docker workspaces on your tailnet with Claude Code and OpenCode pre-installed. This reduces project conflicts and enables remote collaboration.

Core Features & Use Cases

Create and manage isolated Docker workspaces on the tailnet with pre-installed coding agents.
Access workspaces via CLI, web UI, or SSH for flexible development workflows.
Use cases include onboarding new developers, remote coding sessions, and reproducible environments for testing.

Quick Start

Install Perry: curl -fsSL https://raw.githubusercontent.com/gricha/perry/main/install.sh | bash
Run the agent: perry agent run
Point your CLI at the agent: perry config agent <hostname>
Create a workspace: perry start my-proj --clone [email protected]:user/repo.git
Shell into it: perry shell my-proj

Frequently Asked Questions about perry-workspaces

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

FAQPage Schema

How do I create isolated Docker workspaces with Claude Code pre-installed?▼

To create isolated Docker workspaces with Claude Code pre-installed, you can run the Perry agent and use the command 'perry start <project-name> --clone <repository-url>' to automatically provision the environment on your tailnet.

What is the best way to manage reproducible remote development environments across devices?▼

Managing reproducible remote development environments across devices is done by orchestrating a local agent on your tailnet to spin up isolated Docker workspaces, ensuring project conflicts are reduced and team consistency is maintained.

Does Perry work with OpenCode and CLI workflows inside Docker containers?▼

Yes, Perry integrates with OpenCode and Claude Code workflows inside each Docker container, allowing you to access the isolated workspaces via CLI, web UI, or SSH for flexible remote coding sessions.

How do I shell into a Docker workspace on my tailnet after creation?▼

To shell into a Docker workspace on your tailnet after creation, run the command 'perry shell <project-name>' from your CLI to directly access the pre-configured development environment.

Can I use Perry for onboarding new developers with consistent remote environments?▼

Yes, you can use Perry for onboarding new developers because it provides consistent, reproducible Docker workspaces on a tailnet, reducing project conflicts and enabling immediate remote coding sessions.

What are the limitations of using Docker workspaces on a tailnet for development?▼

Docker workspaces on a tailnet require a running local agent and network connectivity to your tailnet, meaning offline development is limited and you must manage the workspace lifecycle commands like start, stop, and remove manually.