⚡ Autonomous Issue Resolution
Meet Slop
Your AI Dev Loop
Slop watches your GitHub issues, dispatches an AI agent to implement each one, waits for CI to pass, and auto-merges the PR. You queue an issue; Slop ships the fix.
3
AI harnesses
22
docs pages
Full
auto-merge pipeline
Zero
cloud dependency
Where do you want to start?
Pick the path that matches where you are right now.
New to Slop
Install & First Run
Step-by-step from cloning the repo to watching your first issue auto-merge. Takes 15 minutes.
Getting Started →
Active Operator
Day-to-Day Operations
Queue issues, monitor workers, manage multiple repos, configure automation and cost controls.
Operator Guide →
Developer / Contributor
Understand the Codebase
Architecture, data models, API contracts, module boundaries, and testing conventions.
Architecture →
How Slop works
Five phases, fully automatic. Read the full Issue Lifecycle for every API call, file, and skill invocation.
🎯
1. Queue
Set an issue Ready on the board
🤖
2. Implement
AI agent codes the fix in a worktree
🧪
3. Verify
Lint, typecheck, and test suite run
✅
4. CI
Waits for GitHub CI to pass
📦
5. Merge
PR auto-merged to main
Slop operates on "watched repos" - repositories you add on the Config page
(a
Repo row with slug + local path). One GITHUB_TOKEN
authenticates all watched repos. Worktrees nest at WORKTREES_ROOT/<repoId>/<issueNumber>.
See Multi-Repo & Auth.
All documentation
Every page in the Slop docs portal.
Start Here
Using Slop
Configuration
Under the Hood
Development
Technology stack
Everything Slop is built on. See Dev Guide for setup.
Next.js 16
React 19
TypeScript 6
Tailwind CSS 4
SQLite + Prisma 7
SSE (no WebSockets)
Claude (Anthropic SDK)
Codex (OpenAI)
GitHub Copilot SDK
Biome 2.4
Vitest 4.1
Playwright 1.60
pnpm 11.3.0