# \#cli

**URL:** https://community.temporal.io/tag/cli/23.md

[Latest](https://community.temporal.io/latest.md) · [Categories](https://community.temporal.io/categories.md) · [Tags](https://community.temporal.io/tags.md)

---

## [Recommended Temporal CLI flow for interacting with schedules in mTLS namespaces?](https://community.temporal.io/t/recommended-temporal-cli-flow-for-interacting-with-schedules-in-mtls-namespaces/19672)

<div class="topic-metadata">

**Author:** [@chadxz](https://community.temporal.io/u/chadxz)\
**Replies:** 1\
**Last updated:** [June 29, 2026, 10:29pm UTC](https://community.temporal.io/t/recommended-temporal-cli-flow-for-interacting-with-schedules-in-mtls-namespaces/19672 "2026-06-29T22:29:28Z")

</div>

We have Temporal Cloud namespaces configured for mTLS auth. The client certs are issued by cert-manager in Kubernetes, and workers use TEMPORAL\_TLS\_CLIENT\_CERT\_PATH / TEMPORAL\_TLS\_CLIENT\_KEY\_PATH. For normal operations,…

---

## [Announcing Environment Configuration in Public Preview](https://community.temporal.io/t/announcing-environment-configuration-in-public-preview/18657)

<div class="topic-metadata">

**Author:** [@Conna\_Lanzafane](https://community.temporal.io/u/Conna_Lanzafane)\
**Replies:** 0\
**Last updated:** [November 12, 2025, 9:53pm UTC](https://community.temporal.io/t/announcing-environment-configuration-in-public-preview/18657 "2025-11-12T21:53:41Z")

</div>

Hi all! Excited to share that Environment Configuration is now in public preview. This feature helps users better manage environment information and utilize it in code to establish a connection to Temporal - e.g. endp…

---

## [Tctl is now deprecated - make the switch to Temporal CLI!](https://community.temporal.io/t/tctl-is-now-deprecated-make-the-switch-to-temporal-cli/18487)

<div class="topic-metadata">

**Author:** [@Conna\_Lanzafane](https://community.temporal.io/u/Conna_Lanzafane)\
**Replies:** 0\
**Last updated:** [October 8, 2025, 9:10pm UTC](https://community.temporal.io/t/tctl-is-now-deprecated-make-the-switch-to-temporal-cli/18487 "2025-10-08T21:10:34Z")

</div>

Hi all! Final reminder that as of September 30th, tctl is no longer supported and users are recommended to begin migrating Temporal CLI if they haven’t already. Temporal CLI offers a nice developer experience and makes i…

---

## [Announcing End of Support for tctl](https://community.temporal.io/t/announcing-end-of-support-for-tctl/17764)

<div class="topic-metadata">

**Author:** [@Conna\_Lanzafane](https://community.temporal.io/u/Conna_Lanzafane)\
**Replies:** 2\
**Last updated:** [August 27, 2025, 9:46pm UTC](https://community.temporal.io/t/announcing-end-of-support-for-tctl/17764 "2025-08-27T21:46:10Z")

</div>

Hi all! :waving\_hand: With the launch of Temporal CLI 1.0 in August last year, it’s time to start End of Support for tctl. Starting September 30th, 2025, Temporal will no longer support tctl and its repo will be archived…

---

## [Inconsistency in temporal workflow list query from cli](https://community.temporal.io/t/inconsistency-in-temporal-workflow-list-query-from-cli/17548)

<div class="topic-metadata">

**Author:** [@madhu](https://community.temporal.io/u/madhu)\
**Replies:** 1\
**Last updated:** [May 28, 2025, 1:01pm UTC](https://community.temporal.io/t/inconsistency-in-temporal-workflow-list-query-from-cli/17548 "2025-05-28T13:01:53Z")

</div>

What are you really trying to do? uniform way of querying archived and hot workflows Describe the bug temporal workflow list -q 'WorkflowType = "MyWorkflowType"' -n mynamespace works i expected temporal workflow…

---

## [Temporal cli api key support, environment and config file issues](https://community.temporal.io/t/temporal-cli-api-key-support-environment-and-config-file-issues/15954)

<div class="topic-metadata">

**Author:** [@sychou](https://community.temporal.io/u/sychou)\
**Replies:** 0\
**Last updated:** [January 3, 2025, 6:41pm UTC](https://community.temporal.io/t/temporal-cli-api-key-support-environment-and-config-file-issues/15954 "2025-01-03T18:41:14Z")

</div>

I’m using temporal cli to check on workflows and when I pass along all of the options as parameters, it works fine. However, I’ like to set the params in a config file and can’t figure out if $HOME/.config/temporalio/tem…

---

## [Retrieving archived workflow data from s3 via UI and tctl workflow list archived](https://community.temporal.io/t/retrieving-archived-workflow-data-from-s3-via-ui-and-tctl-workflow-list-archived/15626)

<div class="topic-metadata">

**Author:** [@Bala](https://community.temporal.io/u/Bala)\
**Replies:** 3\
**Last updated:** [December 16, 2024, 9:44am UTC](https://community.temporal.io/t/retrieving-archived-workflow-data-from-s3-via-ui-and-tctl-workflow-list-archived/15626 "2024-12-16T09:44:24Z")

</div>

I’m facing issues with setting up Archival with s3, though i’m half way there. user@TM00102 ~ % tctl -ns benchtest n desc Name: benchtest Id: 7029315a-7234-4b99-873d-2ad64363a9b7 Description: OwnerEmail: NamespaceData…

---

## [Temporal workflow describe can't parse json result](https://community.temporal.io/t/temporal-workflow-describe-cant-parse-json-result/12108)

<div class="topic-metadata">

**Author:** [@karney](https://community.temporal.io/u/karney)\
**Replies:** 2\
**Last updated:** [May 14, 2024, 9:20pm UTC](https://community.temporal.io/t/temporal-workflow-describe-cant-parse-json-result/12108 "2024-05-14T21:20:23Z")

</div>

when running temporal workflow describe or temporal workflow query the json result causes the the temporal CLI to output an error similar to this (the temporal UI is able to display the object fine, it’s not a big object…

---

## [Get input and output values from Temporal Cli](https://community.temporal.io/t/get-input-and-output-values-from-temporal-cli/10248)

<div class="topic-metadata">

**Author:** [@qaidanwallace](https://community.temporal.io/u/qaidanwallace)\
**Replies:** 0\
**Last updated:** [November 29, 2023, 3:56pm UTC](https://community.temporal.io/t/get-input-and-output-values-from-temporal-cli/10248 "2023-11-29T15:56:03Z")

</div>

Is there a way to retrieve the input and output values for a given workflow id from the cli? The temporal describe command gives plenty of information about a workflow but doesn’t show the input value or the output valu…

---

## [Unable to update namespaces using temporalio/cli](https://community.temporal.io/t/unable-to-update-namespaces-using-temporalio-cli/8771)

<div class="topic-metadata">

**Author:** [@Rene\_Scheepers](https://community.temporal.io/u/Rene_Scheepers)\
**Replies:** 2\
**Last updated:** [July 10, 2023, 8:45am UTC](https://community.temporal.io/t/unable-to-update-namespaces-using-temporalio-cli/8771 "2023-07-10T08:45:38Z")

</div>

Using temporalio/cli I’m unable to update any property on namespaces. While using tctl everything works as expected. The behaviour is the same when having Temporal deployed to a Kubernetes cluster using the Helm chart or…

---

## [Temporal CLI start-dev --config flag not supported](https://community.temporal.io/t/temporal-cli-start-dev-config-flag-not-supported/8745)

<div class="topic-metadata">

**Author:** [@eshieh](https://community.temporal.io/u/eshieh)\
**Replies:** 2\
**Last updated:** [July 6, 2023, 12:21pm UTC](https://community.temporal.io/t/temporal-cli-start-dev-config-flag-not-supported/8745 "2023-07-06T12:21:22Z")

</div>

Hi, According to Temporal CLI server command reference | Temporal Documentation, --config flag can be used to specify development yaml; however, when I ran temporal server start-dev --config $CONFIG\_FILE it returned wi…

---

## [Temporal cli cannot connect to frontend service via Ingress](https://community.temporal.io/t/temporal-cli-cannot-connect-to-frontend-service-via-ingress/8213)

<div class="topic-metadata">

**Author:** [@Andrei-Moiseev](https://community.temporal.io/u/Andrei-Moiseev)\
**Replies:** 3\
**Last updated:** [July 3, 2023, 6:29am UTC](https://community.temporal.io/t/temporal-cli-cannot-connect-to-frontend-service-via-ingress/8213 "2023-07-03T06:29:30Z")

</div>

I deployed Temporal Cluster on on-prem K8s. My deployment is based on Helm Chart with some modifications. I created Ingress for exposing frontend service outside of K8s, but Temporal cli tool fails to connect. All works…

---

## [Error: Unable to get existing search attributes](https://community.temporal.io/t/error-unable-to-get-existing-search-attributes/7855)

<div class="topic-metadata">

**Author:** [@sagardeo21](https://community.temporal.io/u/sagardeo21)\
**Replies:** 1\
**Last updated:** [May 19, 2023, 9:18pm UTC](https://community.temporal.io/t/error-unable-to-get-existing-search-attributes/7855 "2023-05-19T21:18:59Z")

</div>

Hi, We’re trying to add new custom attributes for Elasticsearch query using the below command: tctl admin cluster add\_search\_attributes --name clientID --type Keyword This fails with the below error: Error: Unable to…

---

## [Is temporal-cli and temporalio-tctl the same product](https://community.temporal.io/t/is-temporal-cli-and-temporalio-tctl-the-same-product/8296)

<div class="topic-metadata">

**Author:** [@derek.west](https://community.temporal.io/u/derek.west)\
**Replies:** 1\
**Last updated:** [May 19, 2023, 9:10pm UTC](https://community.temporal.io/t/is-temporal-cli-and-temporalio-tctl-the-same-product/8296 "2023-05-19T21:10:21Z")

</div>

Hey Team. My company is pretty strict about downloading software. So I need to make sure that the versions of stuff that I request are the same etc. Is the temporal-cli and temporalio-tctl the same product but just an…

---

## [Problem create domain](https://community.temporal.io/t/problem-create-domain/125)

<div class="topic-metadata">

**Author:** [@Nicolas\_Hernandez](https://community.temporal.io/u/Nicolas_Hernandez)\
**Replies:** 19\
**Last updated:** [February 23, 2021, 10:30am UTC](https://community.temporal.io/t/problem-create-domain/125 "2021-02-23T10:30:42Z")

</div>

I am running docker run --network=host --rm ubercadence/cli:master --do test-domain domain register -rd 1 after docker-compose up and I get the following error: Error: Register Domain operation failed. Error Details: co…

---

## [How to configure database type, host and port for temporal CLI](https://community.temporal.io/t/how-to-configure-database-type-host-and-port-for-temporal-cli/266)

<div class="topic-metadata">

**Author:** [@ganta](https://community.temporal.io/u/ganta)\
**Replies:** 5\
**Last updated:** [July 23, 2020, 6:30pm UTC](https://community.temporal.io/t/how-to-configure-database-type-host-and-port-for-temporal-cli/266 "2020-07-23T18:30:01Z")

</div>

Although I’ve specified DB related ENV variables during docker run, those values are not configured for tctl. By default, it is trying to connect 127.0.0.1:9042. How can I configure/override DB variables for CLI

---

## [Creating domain with cli is giving error](https://community.temporal.io/t/creating-domain-with-cli-is-giving-error/157)

<div class="topic-metadata">

**Author:** [@abhi93104](https://community.temporal.io/u/abhi93104)\
**Replies:** 6\
**Last updated:** [July 14, 2020, 5:32am UTC](https://community.temporal.io/t/creating-domain-with-cli-is-giving-error/157 "2020-07-14T05:32:37Z")

</div>

Hi team, Is something changed regarding domain registration from cli? I am getting error using this command: docker run --net host --rm ubercadence/cli:master --domain test-domain-2 domain register --global\_domain false …
