Temporal for Omarchy

Your Temporal fleet in the Omarchy bar — servers, namespaces, workflows, activities, task queues and schedules, each shown as its own kind of thing, arranged the way they actually nest.

The bar shows how many Workflow Executions are running and how many have failed recently. Clicking opens a panel you drill down through:

Servers  ›  local  ›  orders  ›  retry-orders
                                 ⚡ keeps_failing
                                   cannot reach billing-orders (attempt 7)
                                   Scheduled · retry in 7s

It is read-only. Nothing here can cancel, terminate, signal or reset a Workflow — the only outbound action is opening a page in your browser.

Install

omarchy plugin add https://github.com/ancelik/omarchy-temporal.git --enable

Then open the widget. With nothing configured it opens on a setup screen that looks for servers on this machine and reads any profiles in your temporal.toml, and adds one on a keystroke. Or from a terminal:

omtemporal setup

Remove

omarchy plugin remove io.github.ancelik.omarchy-temporal

That deletes ~/.config/omarchy/plugins/io.github.ancelik.omarchy-temporal/ and drops the widget from the bar. Your servers are stored on the widget's entry in ~/.config/omarchy/shell.json, which omarchy plugin remove takes with it — if you want to keep them, copy that entry first.

Nothing else is installed: no system packages, no services, no files outside Omarchy's own plugin and config directories.

The primitives

Each level of the panel shows exactly one kind of thing, with its own glyph and a one-line explanation of what it is. That is the point: a namespace and a task queue are not the same sort of object, and a list that mixes them teaches you nothing.

The task-queue level is the one to reach for when work stops moving. Temporal will happily accept executions onto a queue nobody is polling, and this is the only view that says so out loud.

Transports

Each server is reached one of two ways, chosen explicitly per server.

Prefer http where it is available. Reach for cli when the HTTP listener is off — which is the default for most real deployments — when the connection needs client certificates, which the shell's HTTP client cannot present, or for Temporal Cloud, which publishes no HTTP API. A server configured with a client certificate is moved onto cli automatically and told you so.

See AUTH.md for every mechanism, which transport each needs, and worked examples including Temporal Cloud and mTLS.

Both go through the same parsers, so the two render identically. testbed/parity-test.mjs exists to keep that true.

Configuring

The setup screen and omtemporal both write for you. To edit by hand, the widget's entry lives in ~/.config/omarchy/shell.json:

{
  "id": "io.github.ancelik.omarchy-temporal",
  "refreshIntervalSec": 30,
  "servers": [
    { "label": "local", "url": "http://localhost:7243", "uiUrl": "http://localhost:8233" },
    { "label": "prod",  "transport": "cli", "profile": "prod", "namespaces": ["payments"] }
  ]
}

Credentials never reach a command line: the collector spec goes in on stdin and temporal gets its key from the environment. See Secrets and argv.

You may see "servers": {"list": [...]}. That is what the setup screen writes. The shell's setBarWidget IPC silently drops a setting whose value is a bare JSON array, but preserves the identical array nested in an object. Both forms are read the same way, so a hand-written plain array keeps working.

Widget settings

Deep data — activities, pollers, schedules, batch operations — is fetched when you drill into it, not polled for every namespace. A six-namespace fleet costs two requests per namespace per tick, not twenty.

Using it

Breadcrumbs are clickable, so you can jump back several levels at once.

Command line

omtemporal setup                              # interactive picker
omtemporal list                               # configured servers
omtemporal add http://localhost:7243 local    # HTTP
omtemporal add localhost:7233                 # gRPC, via the CLI
omtemporal add profile:prod                   # a temporal.toml profile
omtemporal add https://temporal.corp:7243 prod apiKeyCommand='pass temporal/prod'
omtemporal remove local
omtemporal status
omtemporal doctor                             # why is the widget empty
omtemporal open namespace 0 orders            # jump straight to a level

add and remove call into the running widget, so the terminal and the panel share one implementation and cannot drift apart.

Credentials are editable from the panel too — press s for the server list, Enter on a server, and every field is there: API key, key command, headers, pinned namespaces, TLS paths and the transport. Keys are entered masked and shown only as their length afterwards, and an empty submission leaves a stored key untouched rather than wiping it.

omtemporal doctor is the first thing to run when something looks wrong: it checks the shell, the widget, the CLI, every server's reachability, whether each HTTP server's API is actually enabled — and, since that is now the leading cause of an empty panel, its credentials. What each server carries, anything already known to be wrong with the way it is configured, whether the certificates it names exist and are readable, and whether the key command runs. It reports how many characters the command produced, never the token.

omtemporal open is useful as a keybind — point it at the namespace you care about and skip the drilling.

Two different failure counts, on purpose

The panel shows each namespace's lifetime totals from CountWorkflowExecutions — the true number of failed executions it has ever accumulated.

The bar counts only failures inside the recent window. A namespace that failed something last Tuesday would otherwise pin the widget to its urgent colour forever, which trains you to ignore it. The bar answers "is something going wrong now?"; the panel answers "how much has gone wrong here?".

IPC

omarchy-shell temporal toggle
omarchy-shell temporal refresh
omarchy-shell temporal status
omarchy-shell temporal servers      # per-server reachability
omarchy-shell temporal auth         # per-server credentials, for doctor
omarchy-shell temporal openAt '{"level":"namespace","serverIndex":0,"namespace":"orders"}'

Development

testbed/ brings up two Temporal servers with six namespaces between them and workers that keep every primitive populated — including a Workflow whose Activity retries forever, so the Activity view always has something to show. See testbed/README.md.

bin/dev-install               # validate, copy into ~/.config/omarchy/plugins/, rescan
node testbed/parity-test.mjs  # assert HTTP and CLI parse identically

# An authenticating front door, for the 401/403 and namespace-fallback paths.
# `temporal server start-dev` cannot enforce anything, so a proxy stands in.
docker compose -f testbed/compose.yaml --profile auth up -d authproxy

Saving a file under ~/.config/omarchy/plugins/ hot-reloads plugin QML, but the QML engine caches imported .js files and does not always pick up changes to IPC handlers — after editing Model.js or adding an IPC method, run omarchy-restart-shell. Errors go to the shell's journal:

journalctl --user -f | grep io.github.ancelik.omarchy-temporal

Layout

Levels are not separate files on purpose. Each one is a list of entries built by a function in Model.js and drawn by EntryList, which is what keeps a namespace looking like a namespace everywhere it appears — and makes the entry builders testable without a running shell.

Limits

• mTLS needs the cli transport. QML's XMLHttpRequest cannot present a client certificate, so a server configured with one is moved onto cli.
• Temporal Cloud needs the cli transport. Cloud publishes no documented HTTP API; see AUTH.md.
• Standalone Activities are not shown. The API exposes them, but the Activity view is built on pendingActivities from a Workflow description, which is the one that answers why something is stuck.
• Batch operations are listed, not started. Neither the Python SDK nor temporal batch can start one.

Branding

The mark is Temporal's own symbol — the path from their published Temporal_Symbol SVG, converted to beziers and drawn on a Canvas so it stays sharp at bar sizes and can take the theme's colour. It is reproduced faithfully, including the merge at the lower-right crossing that makes the mark subtly asymmetric (that is in Temporal's own PNG export too, so it is the mark rather than an export artefact).

By default the mark is drawn in your Omarchy theme's foreground colour, and in the theme's urgent colour when something needs attention. That is a deliberate departure from painting it Temporal's brand indigo: an Omarchy bar is themed end to end, a widget that ignores the active theme looks broken next to every other icon, and a mark that stays branded while the fleet is on fire is worse than one that turns red. Set brandColor: true to use Temporal's primary brand colour, UV #444CE7, when nothing is wrong.

Temporal is a trademark of Temporal Technologies, Inc. This plugin is unofficial, is not affiliated with or endorsed by Temporal, and uses the mark only to identify the product it monitors. Brand assets and guidelines: https://temporal.io/brand.

License and dependencies

MIT — see LICENSE, which also lists third-party dependencies.

The plugin itself is self-contained QML plus one stdlib-only Python script. It requires nothing beyond Omarchy unless you use the cli transport, which needs the temporal CLI (MIT) on your PATH and python3 to run collect.py. The http transport needs neither.

Everything under testbed/ is for development only. It is not loaded by the plugin and is not needed to run it.