Welcome to Overcut

Overcut is the control plane for a software factory: a delivery system where an event in your Git, tickets, or CI triggers a workflow, agents do the work, humans hold the approval gates, and the outcome writes back to the tools you already use. Retrospectives review completed runs and feed what they learned into the next ones, so the factory improves on its own. Pick a pillar below to read about that capability, or jump straight to the Quick Start guides to build your first workflow.

​

What you can build

Overcut lets you build any agent that works inside your Git, tickets, or CI, connected to the rest of your ecosystem (logs, metrics, data warehouses, internal APIs). Every workflow runs with sandboxed execution, runtime governance, monitoring, and self-improvement built in.

• Automated SRE: triage alerts, correlate logs and metrics, and open incident tickets with root cause analysis and a proposed fix.
• Always-current documentation: keep docs, API references, and changelogs aligned with the code as PRs merge.
• Engineering standards enforcement: hold every change to your framework versions, naming conventions, and architectural patterns.
• Security and performance governance: scan PRs for vulnerabilities, regressions, and policy violations before they reach main.
• Codebase modernization: run large-scale migrations across services, from framework upgrades to library swaps and deprecations.

Browse the Overcut Playbooks repository for ready-to-use examples you can fork into your workspace. This is what makes the factory self-improving. As runs accumulate, Overcut runs a retrospective that reviews them and writes workflow memories back to the agent, so it stops repeating mistakes and picks up the patterns specific to your team. Procedures your team wants every agent to follow live in skills, versioned with the code they describe.

​

Get started