Skip to Content
MergeLoom MergeLoom Docs

MergeLoom Docs for Ticket-to-Code Automation

Operator docs

Use these docs to get from a clean environment to your first PR or MR with validation evidence from MergeLoom ticket-to-code automation.

Use the MergeLoom controller at https://controller.mergeloom.ai to create your account, choose Cloud Hosted or Self Hosted execution, connect integrations, configure workflow rules, and watch runs.

Know Which UI You Are Using

The customer controller is at https://controller.mergeloom.ai. Use it for accounts, integrations, execution mode, workflow rules, repository settings, Cloud Hosted audit, and controller audit. For Self Hosted, the local worker UI is available only after you install the worker, usually at http://127.0.0.1:8010/ or through an SSH tunnel to that port. Cloud Hosted audit lives in the customer controller. Self Hosted ticket and code audit live in the local worker UI.

The fastest Cloud Hosted route is:

  1. Create a workspace.
  2. Connect your work tracker and code host.
  3. Configure intake labels and workflow states.
  4. Add the label to a ticket and watch MergeLoom create the review request.

For Self Hosted, install the worker and configure your approved provider before running the first ticket.

MergeLoom customer controller worker setup page showing workspace slug and worker enrollment token.
Self Hosted setup: copy the workspace slug and enrollment token before installing the local worker.

Start Here

Section titled “Start Here”

What These Docs Cover

Section titled “What These Docs Cover”

These docs are written for engineering leads, platform engineers, and workspace admins who need to prove MergeLoom safely in a real workflow.

They focus on what customers need to operate MergeLoom:

  • Cloud Hosted execution with MergeLoom-managed workers
  • Self Hosted worker execution
  • Docker Compose and Kubernetes worker deployment paths for Self Hosted
  • worker-local provider setup for Self Hosted
  • Jira, GitHub Issues, GitLab Issues, monday.dev, Linear, and Azure Boards intake
  • GitHub, GitLab, and Azure Repos review output
  • labels, comments, and workflow state changes
  • repository rules, validation commands, and Quality Agent controls
  • Cloud Hosted versus Self Hosted audit access
  • Ticket Audit and Code Audit evidence

Choose the Right Path

Section titled “Choose the Right Path”
If you wantStart with
The fastest hosted pathCloud Hosted execution
Execution inside your own boundarySelf Hosted worker execution
Labels, statuses, comments, and routingWorkflow states and intake
Clarity scoring, investigation, repair, review, and diff guardWorkflow and Quality Agents
Run evidence and line attributionWhere to find audits
MergeLoom-created pull requests linked from the ticket-to-code workflow.
Expected outcome: MergeLoom creates a PR or MR from an approved ticket while your team keeps review and merge control.

Public Installer Sources

Section titled “Public Installer Sources”

The public worker install sources are available here:

For production Kubernetes installs, the Helm chart supports secret.existingSecretName so enrollment tokens and provider API keys can come from your cluster secret workflow instead of Helm values.