josegarridodigio/sluice

Verify each git tree once.
A stack-agnostic verification queue and cache for parallel coding agents.
Six requests for the same tree: one run, five coalesced, and a repeat served from the cache.
Sluice runs each gate (tests, linters, type checks) once per git tree, under a
global concurrency budget, and caches the result. Git hooks call sluice run;
coding agents call the MCP server started by sluice mcp.
## Why
You run four coding agents on the same project, each in its own git worktree,
and every one of them triggers the same pre-commit and pre-push checks.
Four copies of the full suite run at once and the machine stops answering.
Most of those runs verify a tree that already passed: the agent ran it, then
pre-commit, then pre-push, then again after a no-op rebase. Hooks live in
the shared .git/hooks, so nothing coordinates the worktrees. And an agent's
shell tool has a timeout, so a hook that waits in a queue inside git commit
makes the agent move on without the result. Sluice bounds the concurrency,
removes the redundancy and never leaves an agent hanging.
## Features
Per-tree cache. The key is the exact content of the working tree plus the
gate definition, shared by every worktree. Hits return in milliseconds and
never need the daemon.
Daemon with budget and coalescing. A per-user daemon runs gates under a
weighted budget; identical simultaneous requests share one run.
PSI admission. New work is held while the machine is under real pressure
(Linux PSI).
Git hooks for Husky, lefthook, pre-commit/prek and plain .githooks/,
failing fast inside agents instead of hanging.
MCP tools and an agent plugin. sluice mcp gives agents a blocking
verify tool; the agent plugin adds a skill, a guard hook and a session
hook that puts shell shims in the agent's PATH and hands it the rules.
Install it and nothing else.
sluice exec and queue-only gates put any command (docker build,
make) under the same budget, without cache.
Path-scoped gates key on part of the tree, so unrelated changes keep the
cached pass.
Local merge queue. Agents enqueue committed branches; a human approves
one atomic landing.
sluice doctor and sluice update check the installation (with a
redacted bug-report bundle) and upgrade in place.
## Install
Linux only, with git 2.31 or newer in PATH. Prebuilt static binaries for
x8664 and aarch64 are on the
releases page.
sh
curl -fsSL https://raw.githubusercontent.com/josegarridodigio/sluice/main/scripts/install.sh | sh
This installs the latest release into ~/.local/bin (SLUICEVERSION pins a
tag, SLUICEINSTALLDIR relocates). Later, sluice update upgrades in place,
checksum-verified. From source, with a stable Rust toolchain:
sh
cargo install --path crates/sluice-gate
The crate is sluice-gate because sluice is taken on crates.io; the binary
is sluice.
## Quick start
1. Install the binary (above).
2. Install the agent plugin, in Claude Code (with sluice in your PATH):
/plugin marketplace add josegarridodigio/sluice
/plugin install sluice@sluice
3. Run sluice init in each repository (or let the agent propose it):
sh
sluice init --dry-run # detects the stack and your hooks; shows, writes nothing
sluice init # writes .sluice.toml, rewires your hooks