How do I install the Local Temporal skill?

Run npx skillmds@latest add temporalio/local-temporal in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Local Temporal safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Local Temporal?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Local Temporal free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Local Temporal?

temporalio (@temporalio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Local Temporal by temporalio — Agent Skill

Name: Local Temporal
Author: temporalio

Local Temporal

Instructions for running the UI against a local Temporal server build instead of the built-in CLI dev server. Use when asked how to start the dev environment, run the UI locally, or connect to a local Temporal repo.

temporalio 4886c59 2.4 KB Updated Sep 17, 2026

File contents

Local Temporal Dev Setup

To develop against a local build of the Temporal server, you need two things running in separate terminals.

Terminal 1 — Temporal server (from your local temporal repo)

Navigate to your local clone of the temporalio/temporal repo and start the server:

make start

This builds and starts the server with SQLite in-memory. If you want a specific branch, check it out first:

git checkout <branch-name>
make bins  # safe to run even if already built — outputs "Nothing to be done" and exits cleanly
make start

The server runs gRPC on port 7233 and HTTP on 7243.

Terminal 2 — UI dev server (this repo)

From this repo, use the local-temporal script instead of the default dev script:

pnpm dev:local-temporal

This loads .env.local-temporal which points the UI at the local server instead of spinning up its own.

Why not `pnpm dev`?

pnpm dev (aliased to pnpm dev:ui-server) starts a bundled Temporal server alongside the UI. pnpm dev:local-temporal skips that and connects to whatever is already running on the configured ports.

Keeping the ui-server in sync with the Temporal server branch

This is critical when working on unreleased features. The ui-server (server/) is a separate Go binary that acts as a grpc-gateway — it decodes HTTP/JSON into proto messages and forwards them to the Temporal server over gRPC. Its proto descriptors are baked in at compile time from its own server/go.mod.

If the Temporal server branch uses a newer go.temporal.io/api version than server/go.mod, the ui-server will reject any new HTTP fields as "unknown field" before the request ever reaches the Temporal server.

When switching to a Temporal branch with API changes:

Check what go.temporal.io/api version the Temporal server branch uses:
```
grep "go.temporal.io/api" ~/code/temporal/go.mod
```

Update server/go.mod to match:

cd server
go get go.temporal.io/api@<version>

Rebuild the ui-server binary:
```
go build -o ui-server ./cmd/server
```
Then restart pnpm dev:local-temporal to pick up the new binary.

---name: local-temporaldescription: Instructions for running the UI against a local Temporal server build instead of the built-in CLI dev server. Use when asked how to start the dev environment, run the UI locally, or connect to a local Temporal repo.---# Local Temporal Dev SetupTo develop against a local build of the Temporal server, you need two things running in separate terminals.## Terminal 1 — Temporal server (from your local temporal repo)Navigate to your local clone of the `temporalio/temporal` repo and start the server:```bashmake start```This builds and starts the server with SQLite in-memory. If you want a specific branch, check it out first:```bashgit checkout <branch-name>make bins # safe to run even if already built — outputs "Nothing to be done" and exits cleanlymake start```The server runs gRPC on port `7233` and HTTP on `7243`.## Terminal 2 — UI dev server (this repo)From this repo, use the `local-temporal` script instead of the default `dev` script:```bashpnpm dev:local-temporal```This loads `.env.local-temporal` which points the UI at the local server instead of spinning up its own.## Why not `pnpm dev`?`pnpm dev` (aliased to `pnpm dev:ui-server`) starts a bundled Temporal server alongside the UI. `pnpm dev:local-temporal` skips that and connects to whatever is already running on the configured ports.## Keeping the ui-server in sync with the Temporal server branchThis is **critical** when working on unreleased features. The ui-server (`server/`) is a separate Go binary that acts as a grpc-gateway — it decodes HTTP/JSON into proto messages and forwards them to the Temporal server over gRPC. Its proto descriptors are baked in at compile time from its own `server/go.mod`.If the Temporal server branch uses a newer `go.temporal.io/api` version than `server/go.mod`, the ui-server will reject any new HTTP fields as "unknown field" before the request ever reaches the Temporal server.**When switching to a Temporal branch with API changes:**1. Check what `go.temporal.io/api` version the Temporal server branch uses: ```bash grep "go.temporal.io/api" ~/code/temporal/go.mod ```2. Update `server/go.mod` to match: ```bash cd server go get go.temporal.io/api@<version> ```3. Rebuild the ui-server binary: ```bash go build -o ui-server ./cmd/server ```4. Then restart `pnpm dev:local-temporal` to pick up the new binary.

Frequently asked questions