Loren ☺️

@feedmeapples might have more details on this scenario: > since this is a dev server CSRF protection unnecessarily complicates hosting dev server, requiring setting up reverse proxy / HTTPS if...

I think it would be helpful if it appeared as an env with values even if it isn't implemented that way. That way I can: 1. discover with [`env list`](https://github.com/temporalio/cli/issues/193)...

Current CLI matches the gRPC API terminology. Docs uses `name` for both Query and Signal, nothing for Update yet. Inclined toward using `name` for all 3 in docs & CLI.

👍 I meant the first as the firehose (with which someone could implement the second externally). Makes sense to include activity & cloud events as well. Product-wise, I think an...

Another use case: https://docs.prefect.io/ui/automations/

Could also add Cloud-specific events like namespace creation: > Expose ability to handle lifecycle events from our cloud. For example a company wants to run their own workflow when a...

> my preference would be for the tail position --env to work Mine as well!

https://typescript.temporal.io/api/classes/testing.TestWorkflowEnvironment#createlocal

Also methods. Or move to the bottom of results everything I don't care about. Like in this list, most of it is not what I'm searching for: https://typescript.temporal.io/search?q=heartbeat

For client, can update here, like canceled above: https://github.com/temporalio/sdk-typescript/blob/67526d3a9effaea51d9aac3573ba2f8c9d3e1bab/packages/client/src/workflow-client.ts#L400-L410 For proto serialization, we generate code based on protos from core, which come from `/api`, which is missing details: https://github.com/temporalio/api/blob/5c7111f395324103bf630d6a211279adbfb5e418/temporal/api/failure/v1/message.proto#L52-L53 PR...