Skip to Content

Glossary

TermMeaning
Controller UIThe customer-facing MergeLoom web app at https://controller.mergeloom.ai.
Local Worker UIThe Self Hosted worker gateway UI, usually http://127.0.0.1:8010/.
Cloud HostedExecution mode where MergeLoom operates the worker runtime and managed provider path.
Self HostedExecution mode where the customer operates the worker gateway and executors.
Work trackerThe system that supplies work, such as Jira, GitHub Issues, GitLab Issues, Azure Boards, monday.dev, or Linear.
Code hostThe system that hosts repositories and receives PR/MR output, such as GitHub, GitLab, or Azure Repos.
Repository CatalogController UI page where repositories, aliases, roles, branches, context, and validation are configured.
Routing labelA work item label such as repo-api that selects the target repository alias.
RunOne MergeLoom execution attempt for a ticket, issue, campaign node, or manual smoke job.
Retry PublishA publish-stage recovery action that reattempts PR/MR creation from stored branch artifacts without rerunning AI.
Continuation commentA ticket comment starting MergeLoom -, MergeLoom:, or MergeLoom -> that asks for another AI pass.
Run creditProduct usage credit tied to PR/MR outcome allocation and plan enforcement.
Cloud AI creditCredit used for managed AI provider usage in Cloud Hosted mode.
Ticket AuditRun-stage evidence for a specific ticket execution.
Code AuditLine/file evidence that links MergeLoom-written changes back to tickets and runs.
Controller AuditController-side activity for intake, routing, integration, queue, and publish coordination.
Quality AgentsMergeLoom workflow stages such as Clarity, Investigation, Repair, Review, and Diff Guard.
Context EngineContext indexing and context-pack capability available where enabled.