Overcut connects seamlessly to the tools your team already uses. Today, integrations fall into two categories:
  1. Git Integrations – provide Overcut read/write access to your source code so agents can review, generate, and commit changes directly in your repositories.
  2. Ticket Integrations – allow Overcut to read, create, and update issues so agents can respond to bugs, feature requests, or tasks in the systems where you plan work.
More integrations are on the roadmap—let us know which systems you’d like to see next!

Git Integrations

Overcut can connect to the following Git providers:
  • GitHub - Connect to GitHub repositories and issues
  • GitLab - Connect to GitLab repositories and issues
  • Bitbucket - Connect to Bitbucket repositories and issues
  • Azure DevOps - Connect to Azure DevOps repositories and work items
Once connected, agents gain secure, permission-scoped access to clone repositories, create branches, open pull requests, and leave code review comments—without leaving your existing workflows.

Repository Configuration

Each connected repository now exposes a Configuration panel where workspace admins can override agent behaviour for that specific codebase.
#SettingDefaultPurpose
Agent image(workspace default)Override the Docker image used to run agents.
Enable cachefalsePersist build artefacts to speed up subsequent runs.
Cache dependenciesfalseInclude dependency directories (e.g., node_modules).
Tools[]Define repo-specific commands like lint, test, install.
Custom instructionsnullInject additional workflow steps (YAML/Markdown).
Changes are applied immediately and reflected in the audit logs of subsequent automation runs.

Ticket Integrations

To keep your planning and tracking in sync, Overcut also integrates with popular issue-tracking systems:
  • GitHub Issues - Integrated with GitHub repositories
  • Jira - Connect to Jira Cloud workspaces
  • GitLab Issues - Integrated with GitLab repositories
  • **Azure DevOps Work ** - Integrated with Azure DevOps repositories
Agents can automatically open or update tickets, generate specs, and post status updates—all while maintaining a single source of truth in your ticketing tool.

What’s next?

We’re continually expanding our integration surface area. Expect support for additional Git and ticket systems, as well as CI/CD, chat, and observability platforms in future releases.