Dashboard tour
The Loha dashboard is organized around four primary surfaces. Most of your time will be spent in the first two.
Prefer to ask instead of click?
An AI client can read most of the Builds and Repositories data over the MCP server. Try "Open the most recent failed build and show me which step failed, with its exit code." Connecting a repo, authoring a pipeline, and managing secrets stay dashboard-only.
Builds
The list of every build that's run in your workspace, newest first. The first column is the build id, shortened, with a copy button for the full id, followed by status, branch, commit, duration, and trigger source.
Click in for the live build view: a step-by-step tree, real-time log streaming via SSE, retry and cancel controls. Logs stream sub-second from the executing pod: there's no polling and no log delay.
Repositories
Connect, configure, and manage Git repositories. Each repo has five tabs:
- Overview: connection status and a summary of the repo
- Builds: filtered build history for this repo
- Triggers: the push, pull-request, and manual triggers wired to this repo
- Variables: repository-scoped variables and secrets (layered on top of organization-scoped ones)
- Settings: webhook status, default branch, danger-zone actions
Triggers
Where you create and configure triggers: the objects that decide when a pipeline runs. A trigger's detail page also holds its webhook URL, its secret rotation control, and Run now.
The trigger form embeds a YAML editor for .loha.yml with syntax highlighting, code folding, and live schema linting: validation errors from the Loha parser appear inline as you type. Use it when a trigger's config source is inline rather than a file in the repo.
Settings
Workspace-level configuration, organized into tabs:
- Profile: workspace name, logo, slug, status
- Usage: build minutes, parallel builds, projects, and seats against your limit preset (see Workspace activation)
- Retention: the effective retention policy, read-only
- Repo hosts: connected Git host credentials (see Repo hosts)
- Registries: container registry credentials
- Security: the require-2FA mandate and privileged-access activity
- Audit: every privileged action, append-only, with CSV export
- API Keys: your personal access tokens for the CLI, API, and MCP server (members, admins and owners can create them, where member self-service is enabled for the workspace; guests cannot)
- Webhooks: outbound webhook subscriptions
- Danger: schedule workspace deletion (30-day grace window, cancellable)
Two things that are not here: Members is a top-level page rather than a settings tab, and Variables are scoped to a project, not the workspace.
Some surfaces are gated behind platform feature flags and may not appear in every workspace.
Build event stream
Most surfaces auto-update via Server-Sent Events. You don't need to refresh: when a build finishes, the row updates in place.