unfold-deploy 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -1,6 +1,14 @@
 # Changelog
 
-## 0.1.0 (unreleased)
+## 0.2.0 (2026-11-05)
+
+- `unfold gcloud`: Cloud Run deploys (`gcloud run deploy`) as Prepare → Build → Deploy → Live, with build and revision log links, troubleshooting links, and readable errors from gcloud's HTML error pages.
+- `unfold claude "<task>"` and `unfold codex "<task>"`: run Claude Code or Codex non-interactively and show Start → Explore → Change → Verify → Done, with files changed, checks run, the final answer and cost or tokens. Verify is only confirmed by a passing check.
+- Providers that emit JSON events are shown as readable lines instead of raw JSON; their saved runs replay from recorded events.
+- New demos: `gcloud success`, `gcloud deploy-failure`, `claude success`, `codex checks-failing` (`unfold demo <provider> <name>`).
+- Summary headlines and labels now come from the provider ("Deployed", "Done", …).
+
+## 0.1.0 (2026-11-05)
 
 First release.
 

package/README.md

@@ -2,7 +2,14 @@
 
 **Watch what happens after you hit Enter.**
 
-Unfold wraps a CLI command and shows what it's doing as a flow, right in your terminal. The command's own output and prompts work exactly as before, and a small panel pinned to the bottom of the terminal tracks each stage as it happens. It starts with one workflow: a Vercel preview deploy.
+Unfold wraps a CLI command and shows what it's doing as a flow, right in your terminal. The command's own output and prompts work exactly as before, and a small panel pinned to the bottom of the terminal tracks each stage as it happens.
+
+| Command | Wraps | Flow |
+| --- | --- | --- |
+| `unfold vercel` | `vercel deploy` | Prepare → Upload → Build → Preview |
+| `unfold gcloud` | `gcloud run deploy` (Cloud Run) | Prepare → Build → Deploy → Live |
+| `unfold claude "<task>"` | Claude Code, non-interactive | Start → Explore → Change → Verify → Done |
+| `unfold codex "<task>"` | Codex CLI, non-interactive | Start → Explore → Change → Verify → Done |
 
 ```
 Vercel CLI 65.2.0
@@ -35,15 +42,19 @@ npm install -g unfold-deploy
 
 The package is `unfold-deploy`; the command is `unfold`. To try it without installing, prefix commands with `npx unfold-deploy` (for example `npx unfold-deploy demo success`).
 
-## Try it without a Vercel account
+## Try it without an account
 
 The demos play recorded terminal output through the same pipeline a real run uses:
 
 ```sh
-unfold demo success          # a preview deploy that succeeds
-unfold demo build-failure    # the build fails on a TypeScript error
-unfold demo interrupted      # Ctrl+C while Vercel is building
-unfold show                  # explore the run you just watched
+unfold demo success                  # Vercel: a preview deploy that succeeds
+unfold demo build-failure            # Vercel: the build fails on a TypeScript error
+unfold demo interrupted              # Vercel: Ctrl+C while building
+unfold demo gcloud success           # Cloud Run: a source deploy that goes live
+unfold demo gcloud deploy-failure    # Cloud Run: the container never listens on $PORT
+unfold demo claude success           # Claude Code fixes a failing test and confirms it
+unfold demo codex checks-failing     # Codex finishes, but the tests still fail
+unfold show                          # explore the run you just watched
 ```
 
 Add `--speed 2` to play faster. Press Ctrl+C during any demo to see the interrupted state.
@@ -67,6 +78,31 @@ unfold vercel --yes           # any vercel deploy flags pass straight through
 
 Unfold options: `--fix claude|codex` (see below), `--no-panel` (no pinned panel, summary only), `--speed <n>` (demos and replays).
 
+## Deploy to Cloud Run
+
+You need the Google Cloud CLI, logged in (`gcloud auth login`) with a project set. From your service's folder:
+
+```sh
+unfold gcloud --source . --region us-central1      # runs: gcloud run deploy --source . --region us-central1
+unfold gcloud my-api --image us-docker.pkg.dev/…   # prebuilt image: no Build stage
+```
+
+Everything after `unfold gcloud` goes to `gcloud run deploy`, and its questions (service name, region, unauthenticated access) still appear in your terminal. On failure the summary shows the error, the Cloud Build or revision logs link, and the troubleshooting link gcloud printed. HTML error pages gcloud sometimes prints are reduced to their readable sentence.
+
+## Watch a coding agent: Claude Code and Codex
+
+Unfold runs the agent in its non-interactive mode, which reports every step as a structured event, and shows it as a flow: what it read (**Explore**), which files it edited (**Change**), whether checks such as `npm test` or `tsc` passed (**Verify**), and its final answer (**Done**). The summary lists the files changed, the answer, and the cost or token use.
+
+```sh
+unfold claude "fix the failing test" --allowedTools Read Edit "Bash(npm test)"
+unfold claude "add input validation to the signup form" --permission-mode acceptEdits
+unfold codex "fix the failing test" --sandbox workspace-write
+```
+
+- Non-interactive agents can't stop to ask for permission. Give Claude Code the tools it needs with `--allowedTools` or `--permission-mode acceptEdits`; give Codex write access with `--sandbox workspace-write`. Denied tools are listed in the summary.
+- **Verify is only confirmed when a check passes.** If the agent never runs one, or the last one failed, Verify stays `?` with the reason, even when the agent says it's done.
+- Edits go straight to your working tree. Review them with `git diff`.
+
 ### Browser view (optional)
 
 Nothing is served unless you ask for it. Add `--web` to also open the flow in a local browser page, for example `unfold vercel --web` or `unfold show --web`. The page is served on `127.0.0.1` only. With `--web` you can also use `--no-open`, `--once` (exit when the run ends) and `--port <n>` (default 4317).
@@ -99,7 +135,8 @@ Try it without an account: `unfold demo build-failure`.
 
 ## Troubleshooting
 
-- **"Could not find vercel on your PATH"**: install it with `npm i -g vercel`, then run `vercel login`.
+- **"Could not find vercel / gcloud / claude / codex on your PATH"**: install that CLI and log in to it first; Unfold prints the install command.
+- **Agent stopped without changing anything**: it probably wasn't allowed to. Check "Permission denied" in the summary and allow the tool (see above).
 - **Stuck at a Vercel question**: Unfold passes your keystrokes straight to the Vercel CLI, so answer it as usual. In scripts, pass `--yes` and `--scope <team>`.
 - **"Unfold didn't recognize any of this output"**: your Vercel CLI may print a format Unfold doesn't know yet. The deploy itself is unaffected. Please open an issue and include your `vercel --version`.
 - **No live panel**: the panel needs a terminal at least 50×12 and the `node-pty` package. On Linux without build tools, node-pty may not install; Unfold then runs the CLI through the system `script` command, prints only the summary, and keeps prompts working. `UNFOLD_TERMINAL=script` or `UNFOLD_TERMINAL=pipe` forces a fallback, and `--no-panel` turns the panel off.

package/demos/claude-success.json

@@ -0,0 +1,72 @@
+{
+ "provider": "claude",
+ "description": "Claude Code fixes a failing test and confirms it with npm test.",
+ "command": [
+  "claude",
+  "-p",
+  "Fix the failing test",
+  "--permission-mode",
+  "acceptEdits",
+  "--output-format",
+  "stream-json",
+  "--verbose"
+ ],
+ "cwd": "/home/dev/tiny-app",
+ "exitCode": 0,
+ "signal": null,
+ "interrupted": false,
+ "chunks": [
+  {
+   "t": 300,
+   "d": "{\"type\":\"system\",\"subtype\":\"init\",\"cwd\":\"/home/dev/tiny-app\",\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\",\"model\":\"claude-opus-5-5\",\"permissionMode\":\"acceptEdits\",\"claude_code_version\":\"2.1.292\",\"tools\":[\"Read\",\"Edit\",\"Bash\"]}\r\n"
+  },
+  {
+   "t": 1800,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"text\",\"text\":\"I'll look at the code and run the tests first.\"}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 2700,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"tool_use\",\"id\":\"t1\",\"name\":\"Read\",\"input\":{\"file_path\":\"/home/dev/tiny-app/sum.js\"}}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 3000,
+   "d": "{\"type\":\"user\",\"message\":{\"content\":[{\"type\":\"tool_result\",\"tool_use_id\":\"t1\",\"content\":\"1\\texport function sum(a, b) {\\n2\\t  return a - b;\\n3\\t}\\n\",\"is_error\":false}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 4200,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"tool_use\",\"id\":\"t2\",\"name\":\"Bash\",\"input\":{\"command\":\"npm test\",\"description\":\"Run the tests\"}}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 6000,
+   "d": "{\"type\":\"user\",\"message\":{\"content\":[{\"type\":\"tool_result\",\"tool_use_id\":\"t2\",\"content\":\"Exit code 1\\nAssertionError [ERR_ASSERTION]: Expected values to be strictly equal:\\n\\n-1 !== 5\\n\",\"is_error\":true}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 7400,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"text\",\"text\":\"`sum` subtracts instead of adding. Fixing it.\"}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 8500,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"tool_use\",\"id\":\"t3\",\"name\":\"Edit\",\"input\":{\"file_path\":\"/home/dev/tiny-app/sum.js\",\"old_string\":\"return a - b;\",\"new_string\":\"return a + b;\"}}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 8800,
+   "d": "{\"type\":\"user\",\"message\":{\"content\":[{\"type\":\"tool_result\",\"tool_use_id\":\"t3\",\"content\":\"The file /home/dev/tiny-app/sum.js has been updated.\",\"is_error\":false}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 9700,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"tool_use\",\"id\":\"t4\",\"name\":\"Bash\",\"input\":{\"command\":\"npm test\",\"description\":\"Run the tests again\"}}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 11400,
+   "d": "{\"type\":\"user\",\"message\":{\"content\":[{\"type\":\"tool_result\",\"tool_use_id\":\"t4\",\"content\":\"> tiny-app@1.0.0 test\\n> node test.js\\n\\nok\\n\",\"is_error\":false}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 12600,
+   "d": "{\"type\":\"assistant\",\"message\":{\"content\":[{\"type\":\"text\",\"text\":\"Fixed `sum` in sum.js: it returned `a - b` instead of `a + b`. `npm test` now passes.\"}]},\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  },
+  {
+   "t": 12800,
+   "d": "{\"type\":\"result\",\"subtype\":\"success\",\"is_error\":false,\"duration_ms\":13800,\"num_turns\":6,\"result\":\"Fixed `sum` in sum.js: it returned `a - b` instead of `a + b`. `npm test` now passes.\",\"total_cost_usd\":0.1876,\"permission_denials\":[],\"session_id\":\"7b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d\"}\r\n"
+  }
+ ]
+}

package/demos/codex-checks-failing.json

@@ -0,0 +1,62 @@
+{
+ "provider": "codex",
+ "description": "Codex edits a date helper, but the tests still fail when it stops.",
+ "command": [
+  "codex",
+  "exec",
+  "--json",
+  "Fix the time zone bug in startOfDay",
+  "--sandbox",
+  "workspace-write"
+ ],
+ "cwd": "/home/dev/tiny-app",
+ "exitCode": 0,
+ "signal": null,
+ "interrupted": false,
+ "chunks": [
+  {
+   "t": 300,
+   "d": "{\"type\":\"thread.started\",\"thread_id\":\"01a1ae40-5b6c-7d8e-9f01-23456789abcd\"}\r\n"
+  },
+  {
+   "t": 400,
+   "d": "{\"type\":\"turn.started\"}\r\n"
+  },
+  {
+   "t": 2600,
+   "d": "{\"type\":\"item.completed\",\"item\":{\"id\":\"item_0\",\"type\":\"agent_message\",\"text\":\"I'll read the date helper and its tests, then fix the time zone bug.\"}}\r\n"
+  },
+  {
+   "t": 3500,
+   "d": "{\"type\":\"item.started\",\"item\":{\"id\":\"item_1\",\"type\":\"command_execution\",\"command\":\"/bin/zsh -lc \\\"cat src/dates.js test/dates.test.js\\\"\",\"aggregated_output\":\"\",\"exit_code\":null,\"status\":\"in_progress\"}}\r\n"
+  },
+  {
+   "t": 3800,
+   "d": "{\"type\":\"item.completed\",\"item\":{\"id\":\"item_1\",\"type\":\"command_execution\",\"command\":\"/bin/zsh -lc \\\"cat src/dates.js test/dates.test.js\\\"\",\"aggregated_output\":\"export function startOfDay(d) { … }\\n\",\"exit_code\":0,\"status\":\"completed\"}}\r\n"
+  },
+  {
+   "t": 6400,
+   "d": "{\"type\":\"item.started\",\"item\":{\"id\":\"item_2\",\"type\":\"file_change\",\"changes\":[{\"path\":\"/home/dev/tiny-app/src/dates.js\",\"kind\":\"update\"}],\"status\":\"in_progress\"}}\r\n"
+  },
+  {
+   "t": 6600,
+   "d": "{\"type\":\"item.completed\",\"item\":{\"id\":\"item_2\",\"type\":\"file_change\",\"changes\":[{\"path\":\"/home/dev/tiny-app/src/dates.js\",\"kind\":\"update\"}],\"status\":\"completed\"}}\r\n"
+  },
+  {
+   "t": 7400,
+   "d": "{\"type\":\"item.started\",\"item\":{\"id\":\"item_3\",\"type\":\"command_execution\",\"command\":\"/bin/zsh -lc \\\"npm test\\\"\",\"aggregated_output\":\"\",\"exit_code\":null,\"status\":\"in_progress\"}}\r\n"
+  },
+  {
+   "t": 9800,
+   "d": "{\"type\":\"item.completed\",\"item\":{\"id\":\"item_3\",\"type\":\"command_execution\",\"command\":\"/bin/zsh -lc \\\"npm test\\\"\",\"aggregated_output\":\"> tiny-app@1.0.0 test\\n> node --test\\n\\n✖ startOfDay keeps the local date (2.1ms)\\n  AssertionError: Expected \\\"2026-11-05\\\" but got \\\"2026-11-04\\\"\\n\\nℹ tests 6  pass 5  fail 1\\n\",\"exit_code\":1,\"status\":\"failed\"}}\r\n"
+  },
+  {
+   "t": 12400,
+   "d": "{\"type\":\"item.completed\",\"item\":{\"id\":\"item_4\",\"type\":\"agent_message\",\"text\":\"I changed startOfDay to use local time, but one test still fails: it expects 2026-11-05 and gets 2026-11-04, so the test itself may assume UTC. Can you confirm which time zone the dates should use?\"}}\r\n"
+  },
+  {
+   "t": 12600,
+   "d": "{\"type\":\"turn.completed\",\"usage\":{\"input_tokens\":64210,\"cached_input_tokens\":51200,\"output_tokens\":812}}\r\n"
+  }
+ ]
+}