In order to be explicit that `-state` and its relatives are legacy backward-compat mechanisms specific to the local backend, for most commands we've factored them out into [a `local`-backend-specific documentation section](https://www.terraform.io/docs/language/settings/backends/local.html#command-line-arguments) so they can be accompanied by the central explanation about them being legacy and not fully supported across all backends. However, we do still seem to have some laggards which are still presenting these as generally-available options. Let's review each of the commands' docs pages and make them all include a paragraph similar to the ones we've added elsewhere: > For configurations using [the `local` backend](https://www.terraform.io/docs/language/settings/backends/local.html) only, terraform plan accepts the legacy command line option [`-state`](https://www.terraform.io/docs/language/settings/backends/local.html#command-line-arguments). --- Thanks to [a community forum topic](https://discuss.hashicorp.com/t/terraform-workspace-not-creating-with-existing-state/28827), we have at least one example to fix: the [`terraform workspace new`](https://www.terraform.io/docs/cli/commands/workspace/new.html) documentation.