FAQ
Product Basics
Section titled “Product Basics”What does MergeLoom do?
Section titled “What does MergeLoom do?”MergeLoom turns approved tickets or issues into branches and PRs/MRs with validation and audit evidence.
Does MergeLoom merge code automatically?
Section titled “Does MergeLoom merge code automatically?”No. MergeLoom creates or updates review requests. Your team keeps normal human review and merge control in the code host.
Which tools can MergeLoom read work from?
Section titled “Which tools can MergeLoom read work from?”Current customer docs cover Jira, GitHub Issues, GitLab Issues, Azure Boards, monday.dev, and Linear.
Which code hosts can MergeLoom publish to?
Section titled “Which code hosts can MergeLoom publish to?”GitHub, GitLab, and Azure Repos.
Which UI should I use?
Section titled “Which UI should I use?”Use the customer controller for workspace setup, integrations, repository catalog, workflow, access, billing, Cloud Hosted runtime, and controller audit. Use the Local Worker UI only for Self Hosted provider setup, live execution, Ticket Audit, Code Audit, runs, and health.
Why can I not find provider keys in the controller?
Section titled “Why can I not find provider keys in the controller?”Self Hosted provider credentials are worker-local or provisioned through your deployment. Cloud Hosted provider access is managed by MergeLoom and shown as cloud runtime/model policy instead of raw provider keys.
Ticket Intake
Section titled “Ticket Intake”What label starts a run?
Section titled “What label starts a run?”The default managed intake label is mergeloom.
What label chooses a repository?
Section titled “What label chooses a repository?”Use repo-<alias>, for example repo-api. The alias comes from the Repository Catalog.
Why was my ticket skipped?
Section titled “Why was my ticket skipped?”Check the managed label, ready state, assignment, repository routing label, Scheduled intake, and controller-side audit.
Does the ticket need to be assigned?
Section titled “Does the ticket need to be assigned?”Yes where the provider exposes assignment. The assignee should be a MergeLoom workspace user.
Why was my assigned ticket denied?
Section titled “Why was my assigned ticket denied?”The assignment identity may not match an active MergeLoom workspace user. Check the provider username, email, or display identity in Account & Access, then resync or move the ticket back to ready.
Can MergeLoom pick a repository automatically?
Section titled “Can MergeLoom pick a repository automatically?”Only when the workspace has one enabled work repository. If more than one work
repository is enabled, use the repo-<alias> label or a work_repos directive.
Comments and Recovery
Section titled “Comments and Recovery”Does MergeLoom read ticket comments on retry?
Section titled “Does MergeLoom read ticket comments on retry?”For continuation attempts, MergeLoom looks for a new comment starting with MergeLoom -, MergeLoom:, or MergeLoom -> after the previous actionable comment. Move the ticket back to the ready state after adding the comment.
What is Retry Publish?
Section titled “What is Retry Publish?”Retry Publish re-attempts PR/MR creation for eligible failed standalone jobs that already have stored branch artifacts. It does not rerun the AI coding step.
Is there a customer Rerun Job button?
Section titled “Is there a customer Rerun Job button?”No. Use continuation comments for another code pass and Retry Publish for publish-stage recovery.
Cloud Hosted and Self Hosted
Section titled “Cloud Hosted and Self Hosted”When should I use Cloud Hosted?
Section titled “When should I use Cloud Hosted?”Use Cloud Hosted when you want MergeLoom to operate the worker runtime and managed AI provider path.
When should I use Self Hosted?
Section titled “When should I use Self Hosted?”Use Self Hosted when repository checkout, provider calls, validation commands, and deep run traces need to stay inside your environment.
Where does Self Hosted audit live?
Section titled “Where does Self Hosted audit live?”Controller Audit stays in the customer controller. Ticket Audit, Code Audit, live streams, and deep worker traces live in the Local Worker UI.
Providers and Validation
Section titled “Providers and Validation”Which providers can Self Hosted workers use?
Section titled “Which providers can Self Hosted workers use?”Current docs cover Codex CLI, Codex API, Claude Code CLI, Claude API, OpenAI-compatible endpoints, Vertex AI, AWS Bedrock, and Azure Foundry where configured.
Why does validation fail immediately?
Section titled “Why does validation fail immediately?”The command may not be installed in the worker image, may not be allowed by JCA_WORKER_ALLOWED_COMMANDS, or may be configured incorrectly for the repository.
Can I use a private OpenAI-compatible model?
Section titled “Can I use a private OpenAI-compatible model?”Yes, if the endpoint supports the tool-calling behavior MergeLoom needs. Simple prompt/response chat completion is not enough.
Why is my job stuck pending even though the worker is running?
Section titled “Why is my job stuck pending even though the worker is running?”Check worker status, executor status, provider readiness, plan concurrency, deployment mode, and any stale active jobs. A gateway without a ready executor or ready provider will not complete normal execution.
Audit and Security
Section titled “Audit and Security”What can reviewers see?
Section titled “What can reviewers see?”Depending on deployment mode and plan, reviewers can see run state, stage timeline, validation output, repair/review stages, PR/MR links, token/cost estimates, files touched, and Code Audit line evidence.
Does Code Audit replace Git history?
Section titled “Does Code Audit replace Git history?”No. Use your code host for review, approval, blame, and merge history. Use Code Audit to connect MergeLoom-written lines back to tickets and runs.
Where should I look first for an audit question?
Section titled “Where should I look first for an audit question?”Start with Controller Audit if the ticket did not start or route. Use Ticket Audit if a worker executed the run. Use Code Audit when the question is about changed files, line evidence, or PR/MR attribution.
Why did Context Engine not affect my run?
Section titled “Why did Context Engine not affect my run?”Context Engine must be enabled, indexed, authorized for the repository, and available at execution time. Runs can continue with recorded evidence when Context Engine is unavailable.
Is SOC 2 available?
Section titled “Is SOC 2 available?”MergeLoom is working toward SOC 2 readiness. Ask MergeLoom support for the current security materials during vendor review.
Billing
Section titled “Billing”What is the difference between run credits and Cloud AI credits?
Section titled “What is the difference between run credits and Cloud AI credits?”Run credits cover PR/MR outcome allocation. Cloud AI credits cover managed AI usage in Cloud Hosted mode.
Does Self Hosted use Cloud AI credits?
Section titled “Does Self Hosted use Cloud AI credits?”Normally no. Self Hosted workers use your provider account, while MergeLoom run credits still apply to product usage.