メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/temporalio/ui --skill local-temporalコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
How the UI shows system Nexus endpoint operations, and how to add a new one. Use this skill when a person adds, scaffolds, or changes the display of a `__temporal_system` Nexus operation such as SignalWithStart, StartWorkflow, SignalWorkflow, or QueryWorkflow. Also use it when the event history shows a raw "Nexus Operation Scheduled" card that must show the operation.
Find, run, inspect, author, and promote Temporal Catalog examples in the temporalio/ui repository. Use when asked to add or change a workflow example, run the catalog locally, debug a catalog example that will not start, promote a local example into the shared catalog, or explain how catalog namespaces, task queues, and prerequisites are configured.
Locally regenerate @temporalio/proto TypeScript types from current temporalio/api protos, to unblock UI development against unreleased proto fields. Use when the published @temporalio/proto package lags the protos you're developing against (missing/renamed fields). The generated output is local-only and never committed.
SOC 職業分類に基づく
SKILL.md を表示中
| name | local-temporal |
| description | 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. |
To develop against a local build of the Temporal server, you need two things running in separate terminals.
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.
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.
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.
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.