We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 15 since February 2026, each linked to its source.
temporalWhen you need to operate a Standalone Activity, use `temporal activity` to start or execute it, inspect it, wait for its result, or control it by Activity ID. Pause, unpause, reset, and update-options are Experimental; use a list-filter query for supported batch actions.
temporal activity start --activity-id <activity-id> --type <activity-type> --task-queue <task-queue> --start-to-close-timeout 5m --input '{"some-key":"some-value"}'When moving a Workflow to a Worker Deployment Version for one Workflow Task, run `temporal workflow update-options` with `one_time` behavior and the target Deployment Name and Build ID.
temporal workflow update-options --workflow-id <workflow-id> --versioning-override-behavior one_time --versioning-override-deployment-name <deployment-name> --versioning-override-build-id <build-id>When you need to start or manage a Nexus Operation without a caller Workflow, use `temporal nexus operation` with the appropriate lifecycle subcommand; the command group is Experimental.
temporal nexus operation start --endpoint <endpoint> --service <service> --operation <operation> --operation-id <operation-id> [--input '<json>']When you need the worker count for a namespace, run `temporal worker count`; add `--query` to count a subset. The v1.9.1 release marks this command experimental.
temporal worker count --namespace <namespace>When connecting to an OSS server v1.32.0, start a standalone Nexus operation with `temporal nexus operation start`, supplying its endpoint, service, operation, operation ID, and JSON input. The release note identifies this command group as experimental.
temporal operator nexus endpoint create --name <endpoint> --target-namespace <namespace> --target-task-queue <task-queue>When you need the global or connection options and their environment variables or config keys, run `temporal options` to display them in tables. Use the `temporal options` hint in root or subcommand help to find the command.
temporal optionsWhen you need to preview a schedule’s matching times in a time range, run `temporal schedule list-matching-times` with its schedule ID, start time, and end time. It lists matching times without running the schedule actions.
temporal schedule list-matching-times \
--schedule-id <ScheduleId> \
--start-time <StartTimestamp> \
--end-time <EndTimestamp>When starting a standalone activity, pass `--start-delay <duration>` to delay its first task; then describe it by activity ID (and optionally run ID) to inspect the result. The v1.9.0 release note says describe text output exposes `StartDelay`.
temporal activity start --activity-id <ActivityId> --type <ActivityType> --task-queue <TaskQueue> --start-to-close-timeout 30s --start-delay 2sWhen you need to preview a schedule over a time range, run `temporal schedule list-matching-times` with its Schedule ID and required start and end timestamps. It lists matching times without running the scheduled actions.
temporal schedule list-matching-times \
--schedule-id "<ScheduleID>" \
--start-time "<RFC3339 start timestamp>" \
--end-time "<RFC3339 end timestamp>"When using a dev server, the required Standalone Activity dynamic config is enabled automatically; on a self-hosted server, enable `EnableChasm` and `activity.Enabled` manually. Then use `temporal activity` commands to start or execute an activity, inspect or query it, and wait for its result or cancel or terminate it.
temporal activity start --activity-id <activity-id> --type <activity-type> --task-queue <task-queue> --start-to-close-timeout 5m --input '<json-input>'