Skip to content
MergeLoom Docs

MergeLoom Quickstart

This guide gives you the shortest path to your first MergeLoom ticket-to-code job.

Use this path when you want to prove the workflow before tuning every repository rule.

Controller first, worker second

Use the customer controller at https://controller.mergeloom.ai for account setup, integrations, worker enrollment, workflow rules, and job audit state. Use the local worker UI at http://127.0.0.1:8010/ after install for provider setup and worker-local run status.

Before you start

Section titled “Before you start”

You need:

  • a Linux host for the worker
  • Docker Engine and Docker Compose
  • access to a work tracker, such as Jira, GitHub Issues, GitLab Issues, monday.dev, Linear, or Azure Boards
  • access to a code host, such as GitHub, GitLab, or Azure Repos
  • an AI provider you are allowed to use
  • one small test repository where MergeLoom can create a branch and review request
MergeLoom-created pull requests produced from a ticket-to-code job.
Expected outcome: an approved ticket produces a PR or MR ready for human review.

Quick path

Section titled “Quick path”

  1. Create your account at https://controller.mergeloom.ai/register, or sign in at https://controller.mergeloom.ai/login.

  2. Open your MergeLoom workspace in the customer controller and connect your work tracker and code host.

  3. Copy the tenant slug and worker enrollment token from the worker setup page.

  4. Start the worker from the public worker Compose installer repo.

    Terminal window
    git clone https://github.com/MergeLoom/mergeloom-worker-install.git
    cd mergeloom-worker-install
    ./install.sh

    The first run creates .env and stops. Set JCA_WORKER_CONTROL_PLANE_URL to https://controller.mergeloom.ai, add your tenant slug, enrollment token, and worker name, then run ./install.sh again.

  5. Open the worker UI, usually:

    http://127.0.0.1:8010/

  6. Configure an AI provider from the worker provider page.

  7. Configure intake rules in the MergeLoom controller.

  8. Add the managed intake label to a small ticket or issue.

    mergeloom

  9. Watch the run in the MergeLoom controller and worker UI.

MergeLoom customer controller worker setup page showing tenant slug and enrollment token.
Customer controller: copy the tenant slug and enrollment token from the worker setup page before starting the local worker.
Section titled “Recommended first test ticket”

Keep the first ticket narrow and easy to validate.

Good first ticket:

Title: Add a health-check message to the README


Body:
Update README.md with a short "Local health check" section.
Keep the change under 30 lines.
Run the repository's formatting or test command before opening the PR.

Avoid using the first run for:

  • broad refactors
  • multi-repository changes
  • ambiguous product requirements
  • work that cannot be validated by commands or human review

Expected success state

Section titled “Expected success state”

A successful first run should leave you with:

  • a ticket comment showing MergeLoom activity
  • a worker run in the UI
  • a branch pushed to the code host
  • a PR or MR ready for human review
  • validation output or a clear blocked/failure reason

Next steps

Section titled “Next steps”

After the first run:

  • add repository validation commands
  • tune workflow state mappings
  • add organization and repository context
  • decide whether to scale worker executors
  • add Slack or Teams review notifications