Initialize the Clawly master agent environment. Run this once per machine or workspace to bootstrap CLAUDE.md, create .clawly/sessions/, and verify dependencies (tmux). Use when setting up a new VM, a new project workspace, or when the user says "init", "setup clawly", or "bootstrap".
Run tasks in tmux sessions when acting as the Clawly master agent. Use when starting a non-trivial task that benefits from a persistent background shell, when a task has long-running sub-processes (dev servers, watchers, REPLs), or when the user references prior sessions in `.clawly/sessions`. Each task gets one `clawly-<name>` session; sub-tasks are windows (complex / long-running) or panes (simple / one-shot).
A Claude Code plugin that turns Claude into a master agent capable of juggling many tasks in parallel through tmux sessions.
Clawly runs every non-trivial task inside a dedicated tmux session so work is inspectable, resumable, and independent from the main conversation shell. Long-running processes (dev servers, watchers, REPLs) live in their own windows; one-shot commands go into panes. Task state persists across conversations via .clawly/sessions/.
clawly-* tmux session, observable via capture-pane without attaching..clawly/sessions/<name>.md snapshots survive across conversations, so a new session can cold-start with full context./clawly:init verifies tmux, creates .clawly/sessions/, and writes a CLAUDE.md wired up to the master-agent workflow.Add the plugin marketplace and install Clawly:
/plugin marketplace add cross-entropy-ai/claude-plugins
/plugin install clawly@cross-entropy-ai
Then initialize the workspace:
/clawly:init
All Clawly skills are namespaced under clawly: — so the init skill is invoked as /clawly:init, the tmux skill as /clawly:tmux, and so on. This avoids collisions with other plugins or your own commands.
This will:
tmux is installed (and install it via your system package manager if not)..clawly/sessions/ in the current workspace.CLAUDE.md that wires Claude to the master-agent workflow.Once initialized, just give Claude a task. It will:
.clawly/sessions/ and tmux list-sessions for relevant prior or live work.clawly-<task> session.Ask things like:
.clawly/sessions/ and reports live status.Clawly ships with two skills. They are auto-discovered by Claude from their descriptions — you rarely need to invoke them by name — but the explicit slash forms are listed for reference.
| Skill | Purpose |
|---|---|
/clawly:init | Bootstrap a workspace: check tmux, create .clawly/sessions/, write CLAUDE.md |
/clawly:tmux | Create, list, send, capture, and kill clawly-* tmux sessions |
tmux (installed automatically by /clawly:init on supported package managers)bun install
bun run check # biome format + lint + organize imports
See LICENSE.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub cross-entropy-ai/claude-plugins --plugin clawlyLaunch, control, and monitor other Claude Code sessions as workers via tmux
Task orchestrator for Claude Code — spawn and manage multiple task sessions
MCP server for spawning and orchestrating multiple Claude Code sessions via iTerm2
Provides tmux-cli skill, to allow Claude-Code to interact with CLI scripts or other code-agents in tmux panes, using the `tmux-cli` command
TMUX session awareness and process management for running services in dedicated panes
Display Claude agent status in tmux window names via workmux