Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt

Use this file to discover all available pages before exploring further.

Overcut connects to the tools your team already uses. Integrations fall into three categories:
  1. Git Integrations: provide Overcut read and 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.
  3. Chat Integrations: bring Overcut into team conversations so you can trigger workflows from the channels where work happens.
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.com or self-hosted GitLab repositories and issues.
  • Azure DevOps - Connect to Azure DevOps repositories and work items
  • Bitbucket - Connect to Bitbucket repositories and pull requests
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.
Learn more about our security architecture, data handling, and privacy practices in our Privacy and Security documentation.

​
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 Items - Integrated with Azure DevOps repositories
  • Linear - Connect to Linear workspaces and teams
  • ClickUp - Connect to ClickUp workspaces and Spaces for task operations
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.

​
Chat Integrations

Chat integrations let your team start workflows from the conversations where work already happens.
  • Slack: connect Slack at the workspace level, register channels inside each project, and trigger workflows from registered channels.
See the Slack guide for how workspace connections, project channel registration, and channel routing modes work together.

​
Custom Events (generic webhooks)

For any third-party system Overcut does not have a native integration for, Custom Events let a workspace admin define an event type, get a public webhook URL, and pick an authentication mode. Any tool that can send an HTTP request (CI servers like Jenkins, monitoring tools like Datadog or Grafana, internal scripts, low-code platforms) can then fire workflows in the projects you authorize.
  • Custom Events: setup, authentication, project scoping, and ready-to-paste recipes for curl, Jenkins, Datadog, and Grafana.

​
What’s next?

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