stackcanvas 0.2.2 → 0.2.3

package/README.md

@@ -1,6 +1,6 @@
 # stackcanvas
 
-Live infrastructure canvas for [Claude Code](https://claude.com/claude-code).
+Live infrastructure canvas for AI coding agents — any agent that speaks [MCP](https://modelcontextprotocol.io) ([Claude Code](https://claude.com/claude-code) is the CI-verified path).
 The agent writes and plans your Terraform — stackcanvas shows it as a living
 diagram. Drag new resources onto the canvas; the agent turns them into
 idiomatic HCL. No SaaS, no credentials leave your machine: everything runs on
@@ -23,7 +23,13 @@ localhost, reading your local state and plan.
    canvas highlights what will change. Only the agent executes Terraform —
    the canvas has no apply button by design.
 
-## Install (Claude Code)
+## Install
+
+stackcanvas is a standard MCP stdio server (`npx -y stackcanvas`) — point any
+MCP-capable coding agent at it. The paths below, in order of how battle-tested
+they are:
+
+### Claude Code (CI-verified)
 
     claude plugin marketplace add pshenok/stackcanvas
     claude plugin install stackcanvas@stackcanvas
@@ -42,12 +48,12 @@ Or without the plugin system:
 Then, inside a repo with Terraform, just ask: *open the stackcanvas canvas
 for this repo*.
 
-## Other MCP clients
+### Other MCP clients
 
-stackcanvas is a standard [MCP](https://modelcontextprotocol.io) server, so
-any MCP-compatible client can run it. The snippets below are **reported to
-work as standard MCP servers; not yet CI-verified** — only the Claude Code
-path above is exercised in CI.
+The snippets below are **reported to work; not yet CI-verified** — only the
+Claude Code path above is exercised in CI. Codex CLI and other MCP-capable
+agents should work with the equivalent stdio config (`npx -y stackcanvas`) —
+untested, reports welcome in issues.
 
 **Cursor** (`.cursor/mcp.json`):
 
@@ -106,7 +112,7 @@ to pin it — both take precedence over auto-detection.
 
 ## Demo
 
-`examples/demo` contains a small AWS config. Run `terraform init && terraform plan -out=tfplan && terraform show -json tfplan > .stackcanvas/plan.json` there and open the canvas to see create-highlighting. `plan` does not create or modify any resources — nothing is provisioned until `terraform apply` (note: the AWS provider still needs credentials and makes read-only API calls during plan).
+`examples/local-demo` is a **zero-credential** playground: `terraform init && terraform apply -auto-approve` creates real state using only local providers (no cloud account touched), and the canvas renders it — including sensitive masking on the generated password. `examples/demo` contains a small AWS config. Run `terraform init && terraform plan -out=tfplan && terraform show -json tfplan > .stackcanvas/plan.json` there and open the canvas to see create-highlighting. `plan` does not create or modify any resources — nothing is provisioned until `terraform apply` (note: the AWS provider still needs credentials and makes read-only API calls during plan).
 
 ## Telemetry
 

package/dist/cli.js

@@ -934,7 +934,7 @@ function openBrowser(url) {
 }
 
 // src/version.ts
-var VERSION = "0.2.2";
+var VERSION = "0.2.3";
 
 // src/server.ts
 function looksLikeTerraformRoot(dir) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stackcanvas",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "type": "module",
   "main": "dist/cli.js",
   "bin": {
@@ -29,7 +29,7 @@
     "@types/node": "^22.0.0",
     "tsup": "^8.0.0"
   },
-  "description": "Live infrastructure canvas for Claude Code: see what your AI agent is about to do to your Terraform \u2014 and approve it \u2014 before it happens. Local-first, credentials never leave your machine.",
+  "description": "Live infrastructure canvas for AI coding agents (MCP): see what your agent is about to do to your Terraform \u2014 and approve it \u2014 before it happens. Local-first, credentials never leave your machine.",
   "license": "MIT",
   "repository": {
     "type": "git",