More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Worktree Control: Dev Servers & Tests for AI Agents

    1

    Help your coding agent use the right Git worktree, keep the dev server on a stable port, and run checks through a shared test queue. Requires a local Worktree Control installation and MCP connection.

    Free

    Security scanned
    Worktree Control: Dev Servers & Tests for AI Agents

    Worktree Control: Dev Servers & Tests for AI Agents

    Example session with this skill installed

    Check whether the django-testing development server is available to start. Report its current state and any capacity limits. Do not start or stop any servers or acquire a claim.

    • Read your context and instructions
    • Compiled the worktree control

    The project is unclaimed, but there is currently no capacity to start its development server.

    Current state

    CheckResult
    Projectdjango-testing
    Development serverStopped
    Configured port3005
    Project claimNone
    Managed server capacity2 of 2 slots occupied
    Available server slots0

    What this means

    The project has no active claim, but project availability and server capacity are separate checks. Reserving this project would not create an additional server slot.

    Starting it now would exceed the controller's configured limit. I have not attempted to start it, acquired a claim, stopped another server or changed the capacity limit.

    Next step

    Once a server slot becomes available, I can check the current state again, reserve the intended worktree and request startup through Worktree Control. I would then verify the runtime's worktree, port and ready state before reporting that the server is running.

    No runtime changes were made during this check.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Requires a local Worktree Control installation and its MCP connection configured in your coding agent.

    When you work across Git worktrees, your agent needs to know which checkout is running, whether someone else is using the server, and which code a test actually checked.

    This skill gives your agent a repeatable workflow for those decisions.

    Keep your agent on the right worktree

    • Check the active worktree and existing server claims before making changes.
    • Reserve the development server for the intended checkout.
    • Start or switch the managed server while keeping the project's configured port.
    • Run available test, lint, typecheck or build presets through the shared queue.
    • Inspect the result and source attribution, then release the claim when finished.

    Releasing a claim leaves the server running. The skill teaches the agent to handle server ownership and shutdown separately.

    Built for developers using Git worktrees

    Use it when you move between branches, share a development machine with other agents, or need verification tied to a specific checkout.

    Worktree Control runs locally and is MIT licensed. This free skill provides the operating instructions; the controller provides the server management and test queue.

    Setup

    For a new installation:

    1. Install Node.js 22+ and Git.
    2. Run npm install --global worktree-control@0.2.0.
    3. In an interactive terminal, run worktree-control service install --host 127.0.0.1. Save the installation token privately.
    4. Run worktree-control config mcp and add the connection to your agent's private MCP settings. Replace the token placeholder privately.
    5. Register your repository in the dashboard, install its dependencies and confirm that the required test presets are available.

    Loading this skill does not install the controller or configure MCP. Never paste authentication tokens into chat, source files or issues.

    Already running Worktree Control? Reuse your existing controller and authentication settings. Upgrading from 0.1.1 requires the migration procedure. The optional Better Auth provider is not required for the token-mode setup above.

    Compatibility and validation

    The included skill matches the official npm 0.2.0 release. Public-package installation, CLI and MCP smoke checks passed on Linux x64. Full end-to-end validation of this skill remains incomplete; delivery through Agensi, macOS and Windows are unverified.

    Documentation and feedback

    When reporting a problem, include your OS, framework and MCP client. Leave out credentials and private configuration.

    Requires a running local Worktree Control controller and a separately configured MCP connection. Loading the skill does not install or configure either.

    Does not create, delete or prune Git worktrees. Cannot force-release another session's claim or bypass project permissions and server capacity limits. Releasing a claim does not stop the server.

    Queued checks require available presets and installed project dependencies.

    Full end-to-end skill validation remains incomplete. macOS, Windows and delivery through Agensi are unverified.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Requires

    Node.js 22+
    Git
    Worktree Control 0.2.0
    macOS
    Node.js
    For Coding Agents MCP

    Permissions

    Read Files
    Terminal / Shell
    Network Access

    Reads repository instructions and uses the configured Worktree Control MCP endpoint to inspect projects, manage server claims and queue checks. Terminal access supports CLI diagnostics. The skill does not directly edit project files; controller-managed commands may produce build and test artifacts.

    Listed7 days ago

    What's inside

    Frequently Asked Questions

    You need Node.js 22+, Git, a running local Worktree Control controller, and a coding agent connected to its MCP endpoint. Register your repository in Worktree Control first. Queued checks also require available test presets and installed project dependencies. Loading the skill does not perform this setup.

    The skill instructs your agent to inspect the project and existing claims before starting or switching its managed server. Worktree Control enforces claims and configured capacity limits. Each project keeps its configured port when switching worktrees. This coordination applies to controller-managed servers; it does not control unrelated processes started outside Worktree Control.

    The agent must be able to load the skill instructions and connect to Worktree Control through Streamable HTTP MCP with the required authentication. Local checks used Codex in T3, but full end-to-end skill validation remains incomplete. Other clients and delivery through Agensi have not been verified. MCP support alone does not guarantee compatibility with every client configuration.

    The skill is free and MIT licensed. The submitted package contains the official Worktree Control SKILL.md, a setup reference and the MIT license. Minimum setup instructions are also included in this listing. The controller is installed separately; no hosted service or automatic configuration is included.

    It works with existing Git worktrees and does not create, delete or prune them. Releasing a claim ends the agent's reservation but leaves the development server running. Stopping the server is a separate operation that requires authorization and an active claim owned by the agent's session.

    A lost response does not prove that the operation failed. The agent should inspect the current state before acting again. When retrying an identical request within the same valid session, it reuses the original idempotency key. A new session cannot adopt the old session's claim; the agent must wait for expiry or ask the owner to review it. Claim expiry does not stop the server.

    New in Agents & Orchestration