### Terraform Version ```shell Terraform v1.12.2 on linux_amd64 ``` ### Terraform Configuration Files Doesn't matter. Use any config you'd like. ### Debug Output None. ### Expected Behavior When I use `--json` on a plan or apply, I expect to get all the JSON machine readable entries. In fact, when I do a local plan/apply (against a 'true' local workspace or a HCP workspace set to Local Execution Mode), that's exactly what I get. A plan/apply against a HCP workspace set to Remote Execution Mode does not work, as described below. ### Actual Behavior When doing `terraform plan --json` against a HCP workspace set to remote execution, everything starts out well. I get the initial -- `"@level":"info","@message":"Terraform 1.12.2","@module":"terraform.ui","@timestamp":"2025-07-10T08:24:41.125496-04:00","terraform":"1.12.2","type":"version","ui":"1.2"}` And then I get no more JSON records and the only output shown is the 'normal' plan -- ``` Running plan in the remote backend. Output will stream here. Pressing Ctrl-C will stop streaming the logs, but will not stop the plan running remotely. Preparing the remote plan... To view this run in a browser, visit: https://app.terraform.io/app/myorg/myws/runs/run-yG4u3Bxj33Hw3R9i Waiting for the plan to start... Terraform v1.12.2 on linux_amd64 Initializing plugins and modules... terraform_data.validator: Refreshing state... [id=91e23bfa-8432-b365-ff7b-eb37a304d41c] ``` ### Steps to Reproduce Set a HCP workspace to Remote Execution Mode and then run a `terraform plan --json` ### Additional Context Perhaps I'm missing a documented behavior. But I'd expect `--json` to work identically no matter the Execution Mode. It would be nice to have the 'normal' output filtered out when in `--json` mode, but I can grep it away if needed. I believe this last point has been discussed in several past issues. ### References _No response_ ### Generative AI / LLM assisted development? _No response_