probe-research 0.11.0 → 0.13.0

package/README.md

@@ -6,14 +6,36 @@ The Probe Research setup wizard.
 npx probe-research
 ```
 
-Installs and configures [Probe Research](https://research.prbe.ai) for Claude Code.
-It asks which capabilities you want, installs only those plugins, and finishes
-with a single browser approval.
+Signs in to [Probe Research](https://research.prbe.ai) through your browser and
+opens the main wizard menu. If you create an account, finish onboarding on the
+website first. Its final step gives you a command like:
+
+```bash
+npx probe-research install ABCD234567
+```
+
+The 10-character code signs you in once without another browser approval, and
+`install` opens the guided tooling setup for Claude Code, Codex, or pi. Choose
+your agents, select past coding sessions and/or a folder to backfill, then
+confirm the capabilities before anything is installed. Imports run after setup
+and show what they found for review before uploading. Both imports are optional;
+choosing only a folder leaves session history out. Each
+selected agent receives its own capture credential when capture is enabled.
+
+`npx probe-research ABCD234567` also signs in, then opens the main menu.
+`npx probe-research install` runs guided setup with browser sign-in. Expired or
+already-used codes need to be replaced on the website.
 
 This package is a thin launcher. Probe Research is a Python CLI; this exists so
 the entry point matches the `npx <tool>` shape people already expect. It resolves
 a real `probe` (via an existing install, `uv`, or `pipx`) and hands over — there
 is no reimplementation here that could drift from the CLI.
 
-Re-run it any time to change what's enabled, diagnose a problem, update, print
-the manual steps, or remove Probe from the device.
+The main menu requires a signed-in account. Choose **Sign out** to clear this
+device's credentials, stop capture, and exit the wizard. Run the command again
+to sign in to another account. You can also change what's enabled, diagnose a
+problem, update, print the manual steps, or remove Probe from the device.
+
+Publishing this launcher requires `probe-research>=0.147.0` to be available on
+PyPI first. That CLI version introduces website sign-in codes; older installed
+CLIs are upgraded before the launcher forwards the new commands.

package/bin/probe-research.js

@@ -63,14 +63,37 @@ const MANIFEST_TIMEOUT_MS = 1500;
  * to repair the thing it installed. A healthy 0.26.x install pays one refetch,
  * which is the right trade against a broken one staying broken forever.
  *
- * (1) is why it is now 0.36.0. The dashboard's last onboarding step hands out
+ * (1) was why it was 0.36.0. The dashboard's last onboarding step hands out
  * `npx probe-research backfill`, and `probe backfill` does not exist before
  * 0.36.0. Arguments are forwarded to whatever `probe` this launcher resolves,
  * so under the old floor a user with 0.35.0 on PATH gets `No such command
  * 'backfill'` from a command the product just told them to run. A floor is the
  * only thing that can catch it: the copied command is identical either way.
+ *
+ * (1) also raised the floor to 0.56.0, and the failure is quieter. 0.56.0 adds the
+ * BULK verbs an automated caller reaches for rather than a human:
+ *
+ *   probe artifact add --from-manifest FILE   import many files in one process
+ *   probe artifact move ID --to LEVEL         promote/demote/lateral
+ *   probe metrics backfill RUN --key K        a whole derived curve, one request
+ *
+ * The first of those is the one that makes a floor load-bearing. It exists
+ * because per-file `artifact add` costs a process start and a slug resolution
+ * each, so 200k files is tens of CPU-hours -- which means whatever issues it is
+ * importing at that scale, unattended. Against a pre-0.56.0 `probe` on PATH,
+ * `--from-manifest` is an unknown OPTION: the CLI exits 2 having queued
+ * nothing, and there is no operator watching to read it. The old floor is
+ * satisfied by every one of those installs.
+ *
+ * PUBLISHING ORDER MATTERS. `${DIST}>=${target}` must resolve, so this package
+ * may only be `npm publish`ed once a CLI at or above the floor is live on PyPI.
+ * That ordering is not enforced anywhere: the PyPI release is automated and
+ * `npm publish` is manual, so it is a human who has to get it right. Raising
+ * the floor ahead of the release strands the from-zero entry point.
  */
-const MIN_CLI = "0.36.0";
+// 0.147.0 adds positional website sign-in codes to wizard/install. Publish this
+// launcher only after that CLI release is available on PyPI.
+const MIN_CLI = "0.147.0";
 const UV_INSTALL = "curl -LsSf https://astral.sh/uv/install.sh | sh";
 
 /** Compare dotted numeric versions. Returns true when `a` >= `b`. */
@@ -151,11 +174,70 @@ function run(cmd, args) {
   process.exit(r.status === null ? 1 : r.status);
 }
 
+/**
+ * The words the launcher itself interprets. Everything else is a CLI command of
+ * its own and is forwarded untouched.
+ *
+ * Every device setup goes through the wizard (Richard, 2026-09-29), so every
+ * setup spelling this package has ever advertised lands on `probe wizard`, and
+ * the launcher never forwards a retired setup command such as `probe install`:
+ * a later CLI deletes those, and a copied `npx probe-research install CODE` has
+ * to keep working across that release.
+ */
+const LauncherVerb = Object.freeze({
+  WIZARD: "wizard",
+  /** Launcher-only: "straight into the guided install", skipping the menu. */
+  INSTALL: "install",
+});
+/** What `install` means -- exactly what `probe install` always ran (`main.py`). */
+const INSTALL_ACTION = Object.freeze(["--action", "configure"]);
+/** The website's one-time sign-in code; the CLI enforces the same shape. */
+const SIGN_IN_CODE = /^[A-Z0-9]{10}$/;
+/** The CLI root's own options: a call that starts with one names its own
+ *  command (`--base-url X doctor`, `--base-url=X doctor`) and reaches `probe`
+ *  untouched. */
+const ROOT_ONLY_FLAGS = Object.freeze(["--version", "--help", "--base-url", "--spool-dir", "--async", "--sync"]);
+
+/**
+ * `probe` arguments for what was typed after `npx probe-research`.
+ *
+ *   (nothing)                  -> wizard
+ *   CODE [flags]               -> wizard CODE [flags]
+ *   install [CODE] [flags]     -> wizard [CODE] --action configure [flags]
+ *   CODE install [flags]       -> wizard CODE --action configure [flags]
+ *   --flag ...                 -> wizard --flag ...   (the CLI root's own excepted)
+ *   anything else              -> unchanged (`doctor`, `backfill`, `wizard ...`)
+ *
+ * A sign-in code keeps its meaning either way: bare, it signs in and opens the
+ * menu; with `install`, the one-time exchange waits for the agent selection so
+ * it grants exactly what the user chose.
+ */
+function cliArgs(args) {
+  const [first, ...rest] = args;
+  if (first === undefined) return [LauncherVerb.WIZARD];
+  if (SIGN_IN_CODE.test(first)) {
+    if (rest[0] === LauncherVerb.INSTALL) {
+      return [LauncherVerb.WIZARD, first, ...INSTALL_ACTION, ...rest.slice(1)];
+    }
+    return [LauncherVerb.WIZARD, first, ...rest];
+  }
+  if (first === LauncherVerb.INSTALL) {
+    const code = rest.length && SIGN_IN_CODE.test(rest[0]) ? rest.slice(0, 1) : [];
+    return [LauncherVerb.WIZARD, ...code, ...INSTALL_ACTION, ...rest.slice(code.length)];
+  }
+  // Flags alone (`npx probe-research --agent codex`) used to reach the CLI's
+  // root as `probe --agent codex`, which is not a command at all.
+  if (first.startsWith("-") && !ROOT_ONLY_FLAGS.includes(first.split("=")[0])) {
+    return [LauncherVerb.WIZARD, ...args];
+  }
+  return args;
+}
+
 async function main() {
   const args = process.argv.slice(2);
   // `npx probe-research` with no arguments runs the wizard — that is the entire
   // reason this package exists, so it should not require remembering a verb.
-  const forwarded = args.length ? args : ["wizard"];
+  const forwarded = cliArgs(args);
   const wanted = MIN_CLI;
 
   // Hand off to an existing install only when it is BOTH above the floor and
@@ -194,7 +276,9 @@ async function main() {
   // "fetching the latest" and then change nothing. Measured exactly that before
   // this line existed.
   const target = latest && atLeast(latest, wanted) ? latest : wanted;
-  const spec = `${DIST}>=${target}`;
+  // `[all]`: the CLI's dependencies are an extra from the release after
+  // 0.188 (plan 2.11); asking for it is harmless while core still has them.
+  const spec = `${DIST}[all]>=${target}`;
   // REFRESH. uv caches the ENVIRONMENT it built for a requirement, so a range
   // like `>=0.10.0` keeps serving whatever it resolved the FIRST time — every
   // user frozen on the version they happened to run on day one, with the

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "probe-research",
-  "version": "0.11.0",
-  "description": "Setup wizard for Probe Research in Claude Code. Runs from zero with npx.",
+  "version": "0.13.0",
+  "description": "Setup wizard for Probe Research in Claude Code and Codex. Runs from zero with npx.",
   "bin": {
     "probe-research": "bin/probe-research.js"
   },
@@ -19,6 +19,7 @@
   "homepage": "https://research.prbe.ai/connect",
   "keywords": [
     "claude-code",
+    "codex",
     "mlops",
     "experiment-tracking",
     "probe-research"