Zed

Write .rf.hcl in Zed with Rootform diagnostics, completion, hover, go to definition and formatting. Syntax highlighting, bracket matching, indentation and folding keep Dialects and Policy Packs readable.

Start editing

1. Install Rootform and confirm rootform version works.
2. Open Extensions, search for Rootform, and install it.
3. Open a .rf.hcl file.

The extension finds rootform on the workspace PATH and starts the language server. It uses your local executable; it does not bundle or download one.

If Rootform is installed elsewhere, set both the path and arguments in Zed's settings:

settings.json JSON

{
  "lsp": {
    "rootform": {
      "binary": {
        "path": "/absolute/path/to/rootform",
        "arguments": ["lsp"]
      }
    }
  }
}

Keep arguments: ["lsp"] with a path override so Zed starts the server rather than the default CLI command.

Work on a Dialect or Policy Pack

Use completion while writing declarations and expressions, hover to inspect symbols, and go to definition to follow their references. Format the document with Zed's formatting command. Diagnostics update as you edit, including unsaved changes.

The editor uses the same Rootform parser, compiler and formatter as the CLI through rootform lsp. Source validation runs without Terraform, OpenTofu, providers or project content downloads. A Policy still needs a Form for semantic validation and evaluation; editor diagnostics are not a Policy verdict.

Edit Rootform source explains source roots and the authoring workflow. Continue with Test and validate to prove behavior against evidence.

If language features do not start

Check the executable path and the lsp argument together. An absolute path avoids differences between a terminal and the workspace PATH. After fixing a launch error or replacing Rootform, run editor: restart language server.

Use the extension README for launch settings and the LSP reference for the server contract.