@vikat/vikat-gateway-cli 1.0.1 → 1.0.2

package/bin.js

@@ -1,11 +1,13 @@
 #!/usr/bin/env node
 
+import { spawnSync } from "child_process";
 import { createHash } from "crypto";
-import { chmodSync, createWriteStream, existsSync, fsyncSync, mkdirSync, readFileSync, appendFileSync, renameSync, unlinkSync } from "fs";
+import { chmodSync, createWriteStream, existsSync, fsyncSync, mkdirSync, readFileSync, appendFileSync, realpathSync, renameSync, unlinkSync } from "fs";
 import { homedir } from "os";
 import { dirname, join } from "path";
 import { Readable } from "stream";
 import { createInterface } from "readline";
+import { fileURLToPath } from "url";
 
 const BASE_URL = "https://downloads.vikat.ai";
 // Matches the migration CLI. Without a bound, a hung host hangs the install.
@@ -337,7 +339,50 @@ function printStartMessage(message) {
 	console.log(`Enter 'vikat' when you're ready to start the CLI.`);
 }
 
+// ─── ONCE INSTALLED, GET OUT OF THE WAY ─────────────────────────────────────
+//
+// This package declares bin "vikat", and bin.js is an INSTALLER. So
+// `npm i -g @vikat/vikat-gateway-cli` puts the installer at /usr/local/bin/vikat
+// — ahead of ~/.vikat/bin on PATH — where it permanently shadows the CLI it
+// just downloaded. Typing `vikat` re-ran the installer. Every time. Forever.
+// Its own closing line, "Enter 'vikat' when you're ready to start the CLI",
+// sent the user straight back round the loop, and every argument was swallowed:
+// `vikat version` printed installer text and never a version.
+//
+// So: if the CLI is already there, exec it and pass the arguments through. The
+// shim becomes transparent and `vikat` means the CLI, from whichever directory
+// PATH happens to resolve first.
+//
+// FIRST run still installs and still does NOT auto-start. That is deliberate
+// upstream behaviour ("The installer won't start Vikat automatically"), it is
+// what the quickstart documents, and `npx @vikat/vikat-gateway-cli` on a clean
+// machine must keep behaving that way.
+//
+// Installer flags are the exception: --cli-version means "install this version",
+// not "run the tool", so it always takes the install path.
+function execInstalledCli(args) {
+	const target = join(homedir(), ".vikat", "bin", process.platform === "win32" ? "vikat.exe" : "vikat");
+	if (!existsSync(target)) return false;
+
+	// Never exec ourselves. If some future packaging put this script at that
+	// path, the transparent shim would become an infinite fork bomb rather than
+	// the loop it replaced.
+	try {
+		if (realpathSync(target) === realpathSync(fileURLToPath(import.meta.url))) return false;
+	} catch {
+		return false;
+	}
+
+	const res = spawnSync(target, args, { stdio: "inherit" });
+	if (res.error) return false;               // fall through to the installer
+	process.exit(res.status === null ? 1 : res.status);
+}
+
 async function main() {
+	const passthrough = process.argv.slice(2);
+	const installerFlag = passthrough.some((a) => a.startsWith("--cli-version"));
+	if (!installerFlag) execInstalledCli(passthrough);
+
 	const { platformDir, archDir, binaryName } = getPlatformArchAndBinary();
 
 	let namedVersion;
@@ -394,10 +439,25 @@ async function main() {
 	const shellConfig = getShellConfig();
 
 	if (!shellConfig) {
-		// Windows — print manual instructions
+		// getShellConfig() returns null for TWO different situations, and this
+		// branch used to assume the first: actual Windows, and a POSIX machine
+		// whose $SHELL is unset or unrecognised. The second is ordinary — SHELL
+		// is not set in most Docker images, in cron, or in a CI step — and those
+		// users were told to open "System Settings > Environment Variables",
+		// which does not exist on Linux. Advice that cannot be followed reads as
+		// a broken installer.
 		console.log(`\nTo complete installation, add the following directory to your PATH:`);
 		console.log(`  ${installDir}`);
-		console.log(`\nYou can do this in System Settings > Environment Variables.`);
+		if (process.platform === "win32") {
+			console.log(`\nYou can do this in System Settings > Environment Variables.`);
+		} else {
+			// Named rather than guessed: $SHELL told us nothing, so pointing at
+			// one specific rc file would be a guess presented as an instruction.
+			console.log(`\nAdd this line to whichever startup file your shell reads`);
+			console.log(`(~/.bashrc, ~/.zshrc, ~/.profile):`);
+			console.log(`  export PATH="$HOME/.vikat/bin:$PATH"`);
+			console.log(`\n($SHELL is unset or unrecognised here, so this step could not be done for you.)`);
+		}
 		printStartMessage("The installer won't start Vikat automatically.");
 		return;
 	}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vikat/vikat-gateway-cli",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Vikat CLI - Use any harness + any models through Vikat gateway with full observability and governance",
   "keywords": [
     "ai",