temporal-up

A command that starts Temporal's local development server. Temporal runs long-running, reliable workflows; this bundled server also includes PostgreSQL and a browser-based Web UI.

In plain words
What is it for?
Use it to start Temporal on localhost, inspect it through its Web UI, and run it beside a local Ory stack.
Why use it?
It gives a locally running worker or client a Temporal server to connect to during development, without requiring a production cluster.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/ory/claude-plugins/temporal-up
Clone the repo
git clone --depth 1 https://github.com/ory/claude-plugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 380 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00380
Opus 5 $0.00000 $0.00190
Sonnet 5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured yesterday against content hash c8876c7f3958, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

temporal-up scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/ory-agent-plugin/commands/temporal-up.md · 44 lines

What it actually says

Start Local Temporal Dev Server

Start a local Temporal development server alongside the local Ory stack so the worker scaffolded by ory-temporal-worker can connect. This runs Temporal's bundled dev server (Temporal Server + Postgres + Web UI in one process) — not a production cluster.

Prerequisite: the Temporal CLI is installed and temporal is on PATH. On macOS: brew install temporal. On Linux/Windows: download from https://temporal.download.

Run:

temporal server start-dev

This will:

  1. Start the Temporal Server on localhost:7233 (the gRPC endpoint workers and clients connect to)
  2. Expose the Web UI on http://localhost:8233
  3. Persist state under ~/.config/temporalio/ so workflows survive a restart

The process runs in the foreground. Stop it with Ctrl+C; data is preserved. For a clean reset, delete ~/.config/temporalio/ and start again.

For the matching Ory side of the stack (Identities, Permissions, OAuth2, login UI), use /ory-agent-plugin:local-up. The two stacks are independent — Temporal runs on :7233/:8233, Ory runs on :4000 and friends — so they can run side by side without port conflicts.

Once both are up, point the worker at them:

export ORY_PROJECT_URL=http://localhost:4000
export ORY_AUTH_GATE=1
cd temporal-worker
npm run start

See the ory-temporal-worker skill for the full worker scaffold and the permission-gate wiring.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 44 lines · 0 tokens per session scan A c8876c7f3958

Subscribe to this mod's changes

temporal-up is a command published in the GitHub repository ory/claude-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 380 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.