What shipped, what's coming

Shipped means in the build you can install today. Roadmap means coming — never implied as shipped.

• Canvas view over .tf, .tfvars and local modules — blocks as nodes, properties as rows, references as wires.
• Resolved values on every row, computed locally by the WebAssembly HCL engine; honest (known after apply) for values that depend on a real apply.
• Lineage tracing — click a row, its whole path lights up.
• Value marks on every row — literal, reference, interpolated or computed — with a legend, so a resolved value is never mistaken for a hard-coded one.
• Bidirectional write-back: re-point a reference, or edit a value in the properties panel. Both are HCL-validated, both show the exact diff for approval, and only that expression's bytes change.
• Type-aware re-pointing: while you drag, compatible targets light up and incompatible ones refuse the drop. Where several wires share a source, you pick the destination first so the edit can only mean one thing.
• Everything staged until Save, with a review of every pending Terraform change and per-file revert. Reload asks before discarding staged work.
• Simulated workspaces: named sets of variable values kept in the .canvas file, switched from the toolbar or compared all at once — for the values a real workspace injects at plan time.
• File panel and grouping: every file on the canvas with its resources, click to highlight; group the canvas by file, location or resource group, and collapse the groups you are not reading.
• Checked-in .canvas files: one definition, parameterized by workspaces, with overridden values marked.
• Offline licence verification; air-gapped operation after activation.

• Project-wide forest view — the whole configuration on one canvas. The headline item, and the reason the tool exists.
• moved-block refactoring — rename and restructure with state-safe moves.
• Registry and git module sources (local ./ and ../ today).
• Drilling into a module — today it is a box with input and output ports.
• Provider schemas — read from terraform providers schema after you have run init, on your explicit command, never automatically. Shows the attributes a resource could set, makes required/optional/computed exact, and flags a missing required attribute before validate does.
• Provider upgrade impact — pick a target provider version and see, on your own resources, every attribute that was removed, renamed, deprecated, changed type or became required — before you touch a version constraint. The breakage list for your config, not the release notes.
• A palette of provider attributes and resources, driven by those schemas — adding what you have not written yet.
• Adding and deleting resources from the canvas.
• Instance expansion for count and for_each — today a resource with three instances is one node.