@devstationlabs/cli 0.1.1

package/README.md

@@ -0,0 +1,104 @@
+# devstation
+
+The DevStation coding agent, in your terminal. It reads a project, edits it,
+runs the tests, and shows you the diff before anything leaves your machine.
+
+## Install
+
+The binary carries its own runtime, so it needs nothing installed first:
+
+```sh
+curl -fsSL https://devstation.online/install.sh | sh
+```
+
+Or through npm, which needs nothing else either — it fetches the same binary
+and verifies the same checksums:
+
+```sh
+npm install -g @devstationlabs/cli
+```
+
+> Plain `devstation` on npm is an **unrelated package** — a dashboard for
+> managing dev servers. `npm i -g devstation` installs that, not this.
+
+Either way, check the install:
+
+```sh
+devstation doctor
+```
+
+## A key
+
+The agent needs a model. Set one of these and `doctor` will go green:
+
+```sh
+export ANTHROPIC_API_KEY=...     # preferred: prompt caching, native tool use
+export OPENROUTER_API_KEY=...    # also works
+```
+
+Put it in your shell profile so it survives a new terminal.
+
+## Use it
+
+```sh
+cd your-project
+devstation
+```
+
+That starts a session: say what you want, and the transcript carries across
+turns, so the second thing you ask can be about the first.
+
+For one job and out:
+
+```sh
+devstation run "fix the failing test in src/total.test.js, change the source not the test"
+```
+
+For a repository on GitHub, ending in a pull request you approve:
+
+```sh
+export GITHUB_TOKEN=$(gh auth token)
+devstation repo owner/name "add a Usage section to the README"
+```
+
+## What it will not do on its own
+
+Editing files, reading, searching and running the tests happen without asking.
+Anything that deletes, installs, runs an arbitrary command, or reaches outside
+the project asks first, and a plain Enter means no.
+
+Pushing and opening a pull request it cannot do at all. It proposes; you
+decide, with the diff in front of you.
+
+## Everything else
+
+```
+devstation                      start a session and talk to it
+devstation run <goal>           do one thing and stop
+devstation repo <owner/name> <goal>
+                                work on a GitHub repository
+devstation resume [id] [note]   carry on from a stopped or crashed run
+devstation status [id] [-f]     watch a run, from another terminal if you like
+devstation sessions             runs in this workspace
+devstation undo                 rewind the last checkpoint it made
+devstation checkpoints          what it can rewind to
+devstation diff                 everything it has changed
+devstation index                index this project so it can search it
+devstation memory               what it has been told about this project
+devstation tools                its tools, and which ask first
+devstation config               the settings a run would use
+devstation doctor               check this machine
+```
+
+Inside a session, `/help` lists the same things as slash commands.
+
+**[The full reference](../../docs/CLI.md)** covers every flag, the sandbox, MCP
+servers, troubleshooting, and how to uninstall.
+
+## Notes
+
+Runs are checkpointed to git as they go, which is what `undo` rewinds. Sessions
+are written to `.agent/` in the workspace after every message, so a crash is
+resumable and a second terminal can follow a run with `devstation status -f`.
+
+`.agent/` ignores itself, so none of it reaches your history.

package/bin/devstation.mjs

@@ -0,0 +1,55 @@
+#!/usr/bin/env node
+import { spawnSync } from "node:child_process";
+import { existsSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
+import { targetFor } from "../scripts/target.mjs";
+
+// What `devstation` runs when it was installed from npm.
+//
+// Three routes, in order of how well they work.
+//
+// The standalone binary, fetched at install time, carries its own runtime and
+// needs nothing on the machine. That is the normal case.
+//
+// The bundled JavaScript through Bun, for anyone who installed with
+// --ignore-scripts, or on a platform with no published binary. The project
+// index is SQLite through `bun:sqlite`, which is why this route needs Bun
+// rather than running on the node that just launched it.
+//
+// And if neither is available, a sentence saying which and what to do. A stack
+// trace about a missing module is the same information, worse.
+
+const here = dirname(fileURLToPath(import.meta.url));
+const args = process.argv.slice(2);
+
+const target = targetFor();
+const binary = target ? join(here, "..", "scripts", target) : null;
+
+if (binary && existsSync(binary)) {
+  const run = spawnSync(binary, args, { stdio: "inherit" });
+  process.exit(run.status ?? 1);
+}
+
+const bundle = join(here, "..", "devstation.js");
+if (existsSync(bundle)) {
+  const bun = spawnSync("bun", [bundle, ...args], { stdio: "inherit" });
+  if (!(bun.error && bun.error.code === "ENOENT")) process.exit(bun.status ?? 1);
+}
+
+process.stderr.write(
+  [
+    "DevStation could not start: neither the standalone binary nor Bun is here.",
+    "",
+    target
+      ? "  Reinstall to fetch the binary:  npm install -g @devstationlabs/cli"
+      : `  No prebuilt binary for ${process.platform}-${process.arch}.`,
+    "  Or install Bun:                 curl -fsSL https://bun.sh/install | bash",
+    "  Or take the binary directly:    https://github.com/linoxbt/dev-shipyard/releases/latest",
+    "",
+    "If your installer skips scripts (--ignore-scripts), the download above",
+    "never ran. Either allow it, or use one of the other two routes.",
+    "",
+  ].join("\n"),
+);
+process.exit(127);