foldrun 0.4.0 → 0.6.0

package/README.md

@@ -107,6 +107,7 @@ declared the same way.
 | `foldrun open [page]` | the dashboard for this workspace, in the browser |
 | `foldrun login` | sign this machine in from the browser — no key to copy |
 | `foldrun whoami` | who you are on the platform: account, role, workspaces |
+| `foldrun doctor` | check the path to the platform: node, CLI, account, DNS, a timed `/api/healthz` — exit 1 if any line fails |
 | `foldrun keys ls` | the account's API keys — also `create <label>`, `revoke <id>` |
 
 `foldrun --help` lists every flag.

package/bin/foldrun.mjs

@@ -15,9 +15,12 @@
 //   foldrun secrets <verb>  set / ls / rm — the vault, from the terminal
 //   foldrun deploy [dir]    push a workspace into an installation
 //   foldrun invoke <flow>   start a flow on a running platform
+//   foldrun source <verb>   ls / cat / put / mv / rm one workspace file on a platform
 //   foldrun open  [page]    the dashboard for this workspace
 //   foldrun login           sign this machine in from the browser
 //   foldrun whoami          who the platform thinks this terminal is
+//   foldrun doctor          what is between this terminal and the platform, checked
+//   foldrun accounts        every account signed in here; `use <name>` switches
 //   foldrun keys  <verb>    ls / create / revoke — the account's API keys
 //
 // `check` is the one to run in CI: it catches the mistakes that otherwise only
@@ -45,16 +48,20 @@ const HELP = `foldrun — agents are just folders
   foldrun eval [name]       run one eval, or all of them
   foldrun probe <model>     live check: can this model hold a tool loop here?
   foldrun logs [run-id]     recent runs, or one run's full event trail
-  foldrun secrets set NAME  store a secret (prompted, never echoed) — also ls, rm
+  foldrun secrets set NAME  store a secret (prompted, never echoed) — also ls, rm, status
   foldrun connect NAME      OAuth sign-in from the terminal, stored as an auto-refreshing secret
   foldrun deploy [dir]      push a workspace into an installation
   foldrun invoke <flow>     start a flow on a running platform (--to <workspace>)
+  foldrun source <verb>     the files on a platform, one at a time: ls, cat <path>, put <path>, mv, rm (--to <workspace>)
   foldrun open [page]       the dashboard for this workspace, in the browser
 
 Signing in
   foldrun login             sign this machine in from the browser (--token <key> to skip it)
   foldrun logout            forget this machine's key, and revoke it where allowed
   foldrun whoami            who you are on the platform: account, role, workspaces
+  foldrun doctor            check the path to the platform: node, CLI, account, DNS, a timed /api/healthz
+  foldrun accounts          every account signed in on this machine, and which one is active
+  foldrun use <name>        act as one of them from here on
   foldrun keys ls           the account's API keys — also create <label>, revoke <id>
   foldrun --help
 
@@ -62,8 +69,11 @@ Options
   --workspace <dir>         the workspace folder (default: .)
   --from <template>         start from a shipped template, e.g. templates/hello
   --task "<text>"           the instruction for a manual run
+  --test                    run, invoke: a test run — nothing outward, state/ untouched, receipts on the run page
   --follow                  logs: keep tailing a live run (with --url: on the platform)
   --value "<text>"          secrets set: skip the prompt (careful with shell history)
+  --file <path>             source put: the local file to send (default: stdin)
+  --message "<why>"         source put: recorded on the file's revision
   --account                 secrets: account scope instead of the workspace's
   --wait                    invoke: hold on and print the result
   --watch                   invoke: follow the run's trace here as it happens
@@ -84,6 +94,8 @@ Platform options (deploy, invoke, secrets, logs, keys)
   --data <dir>              the installation's data directory
   --url <url>               a running platform (or FOLDRUN_URL, or where you last signed in)
   --token <key>             API key for --url (or FOLDRUN_TOKEN, or the one from foldrun login)
+  FOLDRUN_TIMEOUT=<s>       seconds one request to the platform may take (default 30)
+  --profile <name>          act as one stored account for this command (see foldrun accounts)
   --local                   deploy: into the installation on this machine, even when signed in
   --commit <sha>            deploy: record which commit this is
   --dry-run                 deploy: check and report, change nothing
@@ -103,7 +115,7 @@ if (!command || command === "--help" || command === "-h") {
 // `--value` as the account's argument and stored an empty secret; `--force
 // ./dir` swallowed the directory. A flag followed by another flag is also
 // boolean, so an unlisted switch at least does not eat its neighbour.
-const BOOLEAN_FLAGS = new Set(["account", "follow", "force", "oauth2", "wait", "watch", "print", "dry-run", "help", "no-browser", "local"]);
+const BOOLEAN_FLAGS = new Set(["account", "follow", "force", "oauth2", "wait", "watch", "print", "dry-run", "help", "no-browser", "local", "test"]);
 const flags = {};
 const positional = [];
 for (let i = 0; i < rest.length; i++) {
@@ -154,12 +166,14 @@ if (isDeploy) {
   process.env.FOLDRUN_DATA ??= installationRoot ?? path.join(workspace, ".foldrun");
 }
 
-const { run } = await import(path.join(HERE, "../src/commands.mjs"));
+const { run, explain } = await import(path.join(HERE, "../src/commands.mjs"));
 
 try {
   const code = await run(command, positional, flags, workspace);
   process.exit(code ?? 0);
 } catch (err) {
-  console.error(`\n  ${err instanceof Error ? err.message : String(err)}\n`);
+  // The whole chain, not the top: "fetch failed" is the top, and the
+  // ECONNREFUSED underneath it is the part that says what to do.
+  console.error(`\n  ${explain(err)}\n`);
   process.exit(1);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foldrun",
-  "version": "0.4.0",
+  "version": "0.6.0",
   "description": "Agents are just folders. Write them, check them, run them — on your machine.",
   "license": "Apache-2.0",
   "type": "module",
@@ -11,7 +11,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@foldrun/core": "^0.3.0"
+    "@foldrun/core": "^0.4.0"
   },
   "files": [
     "bin",
@@ -20,8 +20,9 @@
   ],
   "scripts": {
     "e2e": "FOLDRUN_E2E=1 FOLDRUN_DATA=$(mktemp -d /tmp/foldrun-e2e-XXXXXX) node --test --test-timeout=300000 tests/e2e.test.ts",
-    "test": "FOLDRUN_DATA=$(mktemp -d /tmp/foldrun-test-XXXXXX) node --test tests/cli-secrets.test.ts tests/cli-check-library.test.ts tests/cli-connect.test.ts",
-    "release": "node scripts/release.mjs"
+    "test": "FOLDRUN_DATA=$(mktemp -d /tmp/foldrun-test-XXXXXX) node --test tests/cli-secrets.test.ts tests/cli-check-library.test.ts tests/cli-connect.test.ts tests/cli-accounts.test.ts tests/cli-remote.test.ts tests/cli-stream.test.ts tests/cli-doctor.test.ts",
+    "release": "node scripts/release.mjs",
+    "typecheck": "tsc -p tsconfig.json"
   },
   "repository": {
     "type": "git",
@@ -40,5 +41,10 @@
   ],
   "publishConfig": {
     "access": "public"
+  },
+  "devDependencies": {
+    "@types/node": "^22.20.2",
+    "gray-matter": "^4.0.3",
+    "typescript": "^5.9.3"
   }
 }