This repository provides workflow utilities for AI agents, addressing the challenge of isolating agent tasks and managing their output within Git repositories. It offers wrappers for Git worktrees to streamline the process of creating isolated environments for agents, committing changes, and integrating them back into the main codebase via pull requests. The tools are designed for developers and researchers leveraging AI agents for coding, refactoring, and debugging tasks.

How It Works

The core approach utilizes Git worktrees to isolate AI agent operations in separate directories, preventing interference with the main codebase. Two primary wrappers are provided: git-wt for basic worktree management and worktrunk for a more integrated create-commit-PR-merge-cleanup cycle, including LLM-assisted commit generation. The project also facilitates providing code context to LLMs using git archive or git bundle and supports modern Git features like relative worktree paths for enhanced DevContainer compatibility.

Quick Start & Requirements

• git-wt Installation: brew install k1LoW/tap/git-wt
• worktrunk Configuration: Via ~/.config/worktrunk/config.toml (example provided).
• DevContainer: Requires Docker (OrbStack recommended). Run with ./devcontainer/install.sh self-install and devc /path/to/repo.
• LLM Context: Use git archive HEAD -o code.zip or git bundle create repo.bundle --all.
• Notifications: uv tool install takopi.
• Prerequisites: Git >= 2.48 recommended for relative worktree paths.

Highlighted Details

• Streamlined Git worktree management via git-wt and worktrunk wrappers.
• worktrunk supports LLM-generated commits and a full PR/merge cycle.
• Methods for packaging repository code (git archive, git bundle) for LLM context.
• takopi for Telegram notifications and resumable agent sessions.
• DevContainer integration for isolated, unattended agent execution.
• Support for relative Git worktree paths (Git 2.48+).

Maintenance & Community

No specific details regarding maintainers, community channels (like Discord/Slack), or roadmap were found in the provided README.

Licensing & Compatibility

The license type and compatibility for commercial use are not specified in the provided README text.

Limitations & Caveats

Support for relative worktree paths requires Git version 2.48 or newer. The project implicitly contrasts its workflow with tools like beads, highlighting the complexity of removing the latter as a potential advantage of its own simpler management approach.