sync-containers

Propagate skill and agent configuration files to claude-sandbox Docker containers.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/erichugy/agentic.skills --skill sync-containers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-containers
Source: https://github.com/erichugy/agentic.skills/tree/main/sync-containers
Command: npx skills add https://github.com/erichugy/agentic.skills --skill sync-containers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents configuration and skill drift between your host environment and claude-sandbox Docker containers by propagating local changes so containerized agents run the same code and settings as the host.

Core Features & Use Cases

  • Discover claude-sandbox containers whether running or stopped and let the user confirm targets.
  • Copy host files (skills, commands, CLAUDE.md, settings, agents, hooks), rewrite internal paths, and set correct ownership and permissions inside each container.
  • Optionally start stopped containers to perform the sync and then restore their prior running state; useful after manual edits to ~/.claude or ~/.agents, after automated skill updates, or as a post-deployment step in CI workflows.

Quick Start

Invoke the skill by running /sync-containers to synchronize host skills, CLAUDE.md, AGENTS.md, settings, and agent files into all selected claude-sandbox Docker containers.

Frequently Asked Questions about sync-containers

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

FAQPage Schema
How do I sync local claude-sandbox configuration files to Docker containers?

You can sync claude-sandbox configuration files by running /sync-containers, which discovers target Docker containers, copies host files using docker cp, rewrites internal paths, and adjusts ownership and permissions inside each container.

Does sync-containers work on stopped Docker containers?

Yes, sync-containers works on stopped Docker containers by optionally starting them to perform the file synchronization, then restoring their prior running state to ensure configuration drift is resolved without altering container lifecycle.

What Docker files are propagated to keep claude-sandbox containers in sync?

The files propagated to keep claude-sandbox containers in sync include skills, CLAUDE.md, AGENTS.md, hooks, and local agent settings, ensuring containerized agents run the same code and settings as the host environment.

Do I need Docker CLI access to sync skills and settings into containers?

Yes, you need Docker CLI access and host filesystem permissions to sync skills and settings into containers, as the process relies on docker cp to copy files and adjust ownership and permissions inside each container.

Why does my containerized agent have configuration drift after updating skills on the host?

Configuration drift occurs because manual edits or automated updates to ~/.claude or ~/.agents on the host are not automatically reflected in Docker containers, requiring a sync operation to propagate the changed files and maintain consistency.