Squash

Squash is a local tool that autonomously fixes bugs. Paste a GitHub or Linear issue URL, and an AI agent takes it from there — reading the issue, assessing whether it can handle it, making the fix, and opening a draft PR for your review. Multiple issues run in parallel without interfering with each other.

• Node 20+
• Claude Code CLI installed and authenticated (claude command available)
• GitHub CLI installed and authenticated (gh auth status should pass)

If you have Claude Code installed, paste this prompt to have it set everything up for you:

Clone https://github.com/davemart-in/squash.git, install dependencies (including inside src/ui), then walk me through creating the .env file. I'll need help getting my ANTHROPIC_API_KEY, GITHUB_TOKEN, and LINEAR_API_KEY. Skip REPO_PATH — leave it blank, the app handles repo setup through the UI. Once .env is ready, start the dev server.

Claude Code will clone the repo, run the installs, ask you for each API key one at a time, create the .env file, and start Squash. No terminal knowledge required.

git clone https://github.com/davemart-in/squash.git
cd squash
npm install
cd src/ui && npm install && cd ../..
cp .env.example .env

Fill in your .env values:

npm run dev

This starts both the API server (with hot reload) and the Vite dev server concurrently. The UI is available at http://localhost:5173 and proxies API requests to port 3001.

npm run build
npm start

The build command compiles the React frontend into src/api/public/. The start command runs the server, which serves both the API and the static frontend on a single port.

npm run db:reset

This deletes squash.db and re-creates the schema.

Each agent runs in an isolated git worktree under ./worktrees/{issueId} on a branch named fix/{issueId}. This means agents can work in parallel without interfering with each other or your main working directory.

If an agent errors out mid-run, the worktree and branch will still exist. Clean them up manually:

# List active worktrees
git worktree list

# Remove a specific worktree
git worktree remove ./worktrees/{issueId}

# Delete the branch
git branch -D fix/{issueId}

# Or remove all worktrees at once
rm -rf ./worktrees
git worktree prune

• No skip override. If the assessor rejects an issue (complexity score 7+), there's no way to force it through yet.
• Draft PRs only. The agent never opens a ready-for-review PR — you decide when to promote it.