Controller UI Overview
The MergeLoom customer controller is the central workspace UI at https://controller.mergeloom.ai.
Use it for workspace setup, integrations, repository access, workflow rules, user access, prompts, billing, Cloud Hosted runtime status, and controller-side audit. For Self Hosted workspaces, the controller still coordinates intake, routing, queue state, and PR/MR publishing, but worker execution details live in the Local Worker UI.
What the Controller Owns
Section titled “What the Controller Owns”| Area | Controller location | Who normally uses it |
|---|---|---|
| Dashboard and analytics | Dashboard, Analytics | Workspace admins, engineering leads |
| Execution mode | Worker Setup or Cloud Runtime | Workspace admins |
| Integrations | Integrations | Workspace admins |
| Repository catalog | Repositories | Workspace admins |
| Workflow rules | Workflow | Workspace admins |
| Prompts and templates | Prompts | Workspace admins |
| Review notifications | Workflow | Workspace admins |
| Campaigns | Campaigns | Workspace admins and delivery leads |
| Access and SSO | Account & Access | Workspace admins |
| Billing and credits | Billing | Workspace admins |
| Cloud audit | Audit | Cloud Hosted workspaces |
| Controller audit | Audit or Activity | Cloud Hosted and Self Hosted workspaces |
Workspace users can view the workspace and run-visible information, but workspace configuration is read-only for users without the workspace admin role.
Cloud Hosted
Section titled “Cloud Hosted”For Cloud Hosted workspaces, the controller also shows the managed runtime:
- Cloud Runtime shows readiness, current model policy, live run state, and cloud provider status.
- Audit shows Ticket Audit, Code Audit, Controller Audit, and Context Engine audit where enabled.
- Billing shows run credits, Cloud AI credits, payment method state, and plan state.
Cloud Hosted customers do not open http://127.0.0.1:8010/. That Local Worker UI belongs to Self Hosted workers.
Self Hosted
Section titled “Self Hosted”For Self Hosted workspaces, use the controller for:
- integration connection state
- repository catalog sync and repository aliases
- workflow labels, status mappings, and scheduled intake
- worker enrollment values
- workspace default provider/model selection where shown
- controller-side job state and PR/MR coordination
- access, billing, prompts, and notifications
Use the Local Worker UI for provider credentials, live execution, worker health, Ticket Audit, Code Audit, and deep worker traces.
Common Questions
Section titled “Common Questions”Where do I choose the repository for a ticket?
Use the repository alias from Repositories and add the matching repo-<alias> label or tag to the ticket. See Repository Catalog.
Where do I turn on automatic intake? Open Workflow and enable Scheduled intake only after integrations, repository routing, and the execution mode are ready.
Where do I see why a ticket was skipped? Start with controller-side audit or activity. It records intake, assignment, routing, queue, integration, and PR/MR coordination events.
Where do I see provider logs for Self Hosted? Use the Local Worker UI. The controller deliberately does not become the system of record for worker-local provider traces.