Max Sixty Worktrunk
max-sixty-worktrunk is a Claude Code plugin for the Build phase that connects Worktrunk—a Git worktree CLI—for parallel AI agent coding sessions.
by max-sixty · github.com/max-sixty/worktrunk
Add Worktrunk when you run multiple AI coding agents on one repo and need Git worktrees, hooks, and session visibility without manual branch gymnastics.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install max-sixty-worktrunk@max-sixty/worktrunkBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:max-sixty/worktrunk") and the paste-ready config with skillselion.get_install_config("plugin:max-sixty/worktrunk").
What it does
max-sixty-worktrunk is a Claude Code plugin that documents and integrates Worktrunk, a CLI built for Git worktree management when you are running parallel AI agent sessions on one project. Solo builders often hit a wall when Cursor, Claude Code, or Codex each want their own branch: conflicts, lost context, and messy working directories slow you down. Worktrunk gives you a disciplined way to isolate agent work per tree, wire project configuration and hooks, and track which session is touching which path. It is especially useful when you are building a SaaS or CLI while letting agents tackle backend, frontend, and test fixes concurrently. You still merge and review like normal Git workflow—the plugin helps Claude understand how to use Worktrunk commands and project conventions so you spend less time recovering from overlapping edits. Expect intermediate Git comfort; the payoff is calmer multi-agent Build and Ship cycles.
Highlights
- CLI-first Git worktree management tuned for parallel AI agent workflows
- Project-level configuration, hooks, and path guidance for multi-tree setups
- Session and activity indicators so you can see which agent/worktree is active
- Automatic commit messaging and workflow hooks aligned with agent-driven edits
- Single-plugin bundle focused purely on worktree orchestration—not hosting or CI
Why builders use it
Running several coding agents on one repository without worktrees leads to branch collisions, confused working trees, and painful merges.
After installing the plugin, you can standardize isolated worktrees per agent session with hooks and visibility so parallel Claude workflows stay mergeable.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 4.2k stars, 0 votes.
FAQ
Who is max-sixty-worktrunk for?
It is for developers using Claude Code who manage Git repos and want Worktrunk-style worktree workflows for parallel AI coding sessions.
When should I use max-sixty-worktrunk?
Use it when you are splitting features or experiments across multiple agents and need separate worktrees, clear active-session tracking, and consistent project hooks.
How do I add max-sixty-worktrunk to my agent?
Install the Worktrunk CLI on your machine, enable the max-sixty/worktrunk Claude Code plugin from Skillselion, and follow the plugin’s project configuration so Claude invokes the correct worktree commands in your repo.
Comments
Share how you use max-sixty-worktrunk, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.