Worktrunk Bot
6237f5b6eb
The README's intro blockquote still opened with **August 2026**; today is 2026-09-01, so the stamp is a month stale. This bumps it to **September 2026** — the same monthly refresh as #3686 (August), #3347 (July), and #2972 (June). Line 16 sits above the first `<!-- AUTO-GENERATED -->` marker (line 28), so it is a hand-edited primary rather than generated content. It has two mirrors, which behave differently: `skills/worktrunk/reference/README.md` is a symlink to the root `README.md` and picks the change up for free, while `plugins/worktrunk/skills/worktrunk/reference/README.md` is a generated *file copy* and needs its own sync — that second commit is here because `test_docs_are_in_sync` caught the stale copy on the first push. No regression test: the stamp is prose with no behavioral surface, and its correctness is time-dependent rather than assertable. <details><summary>Nightly sweep context</summary> Found by the rolling survey (bucket 5/28) together with the README date check in the repo's `running-tend` skill. The rest of the sweep was clean: - **tend config** — `tend check` all PASS; bot PAT carries every required scope. - **Conflicts** — #3129 (bot) and #3966/#3967/#3978 (Dependabot) all test-merge clean against `main` via `git merge-tree`; no deferral comments to clear. - **Workflow regen** — `uvx tend@latest init` produced no diff; the committed workflows are already at tend 0.1.24. - **Recent commits** — the 7 commits in the last 24h reviewed; no findings. The `for_action_branchless` → `for_action_loading_config` rename in #3970 left no stale references, and #3976's `append_call_line` change carries its own regression test. - **Survey** — `src/cache.rs`, `src/config/user/path.rs`, `src/config/user/sections.rs`, `src/styling/line.rs`, `docs/src/content/docs/claude-code.md`, the two `.config/clawpatch/features/*.json` files (every referenced path still resolves), and the skill/plugin pages. No findings. </details> --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
Worktrunk Plugin for Claude Code
Git worktree management CLI integration with activity tracking.
Requires the wt CLI (worktrunk.dev) and jq (used
by the worktree-lifecycle hooks).
Features
- Configuration skill — Guides LLM-powered commit message setup, project hooks (pre-start, pre-merge), and worktree path customization
- Activity tracking — Shows which branches have active Claude sessions via indicators in
wt list /wt-switch-createcommand — Creates a worktrunk worktree and moves the current Claude session into it
Examples
Activity tracking across worktrees
The plugin installs Claude Code hooks that track session activity per branch. When a prompt is submitted, the hook sets 🤖 on that branch. When Claude finishes and waits for input, it switches to 💬. When the session ends, the marker clears.
These markers appear in wt list output, making it easy to see which worktrees have active Claude sessions — useful when running multiple instances in parallel.
Set up LLM commit message generation
The configuration skill guides through configuring an AI tool (Claude Code, Codex, llm, or aichat) and adding [commit.generation] to the user config so wt merge can auto-generate commit messages.
Add pre-start hooks to run npm install automatically
The skill configures .config/wt.toml with project hooks. Pre-start hooks run when creating worktrees, pre-merge hooks validate before merging.
Start work in a fresh worktree
/wt-switch-create fix-auth Investigate the 5-minute session timeout creates a fix-auth worktree in worktrunk's normal sibling layout (<repo>.fix-auth/), switches the session into it, and starts the task there. The branch name is optional (/wt-switch-create -- <task>). The worktree persists after the session — merge or remove it with wt merge / wt remove like any other.