orchestrai 0.1.4 → 0.1.6

package/README.md

@@ -1,6 +1,6 @@
 # orchestrai
 
-Run [OrchestrAI](https://github.com/Muhamad-Yussuf/devops-mcp-server) — a local, terminal-oriented multi-agent DevOps orchestration prototype — with nothing pre-installed:
+Run OrchestrAI — a local, terminal-oriented multi-agent DevOps orchestration prototype — with nothing pre-installed:
 
 ```
 npx orchestrai --project /path/to/your/project
@@ -14,6 +14,8 @@ bunx orchestrai --project /path/to/your/project
 
 No Bun, no clone, no separate download step — the right platform binary installs automatically as part of this package (an optional dependency scoped to your OS/architecture), and this command just runs it.
 
+`orchestrai` starts the full local stack — 5 specialist agents (planning, DevOps, testing, documentation, security), an MCP tool server, and an orchestrator that routes work between them — then opens a **dashboard at [http://localhost:3000/dashboard](http://localhost:3000/dashboard)**. That's where you submit tasks and watch them run.
+
 ## Supported platforms
 
 | Platform | Package |
@@ -22,7 +24,7 @@ No Bun, no clone, no separate download step — the right platform binary instal
 | Linux x64 | `orchestrai-linux-x64` |
 | macOS Apple Silicon (arm64) | `orchestrai-darwin-arm64` |
 
-macOS Intel (x64) isn't published yet. If `npx`/`bunx` reports no build for your platform, that's why — build from source instead (see the main repository).
+macOS Intel (x64) isn't published yet. If `npx`/`bunx` reports no build for your platform, that's why.
 
 ### macOS: unsigned binary
 
@@ -40,12 +42,17 @@ xattr -d com.apple.quarantine "$(which orchestrai)"
 orchestrai                          # start everything, interactively in a real terminal
 orchestrai init                     # interactive setup wizard, run once per project
 orchestrai --project "/path/to/app"
-orchestrai --only devops-agent
+orchestrai --only devops-agent      # start a subset of services (comma-separated)
+orchestrai --headless               # backend only, plain logs — no interactive viewer
 orchestrai --help
 ```
 
-See the [main repository](https://github.com/Muhamad-Yussuf/devops-mcp-server) for full documentation.
+`orchestrai init` walks you through target path, which services to run, and whether to enable the optional LLM planning harness (provider/model/API key) — answer once, and a plain `orchestrai` afterward reuses that setup with no flags needed.
 
 ## Reproducibility
 
 Each published version of this package corresponds to a specific, immutable build — pinning a version (`npx orchestrai@1.2.3`) always resolves the identical binary, not a rolling "latest."
+
+## Source
+
+The source repository is currently private, so it isn't publicly browsable — everything you need to actually run this is in this package itself (`orchestrai --help` and `orchestrai init` cover it). This README will link out to public docs if/when that changes.

package/bin/orchestrai.js

@@ -24,7 +24,7 @@
 
 const path = require("path")
 const { spawnSync } = require("child_process")
-const { chmodSync } = require("fs")
+const { chmodSync, existsSync } = require("fs")
 
 // One fixed platform package per supported platform+arch — mirrors
 // npm-package/*/package.json's own "os"/"cpu" restrictions exactly.
@@ -47,12 +47,19 @@ function resolveBinaryPath() {
         `See https://github.com/Muhamad-Yussuf/devops-mcp-server#readme for building from source instead.`,
     )
   }
+  // Resolve the platform package's own package.json first, then join the
+  // known relative bin path onto its directory — rather than
+  // require.resolve()-ing the binary's deep sub-path directly. Found live
+  // (a real WSL/global-install report, binary confirmed present on disk
+  // in exactly the expected location, yet the deep-path resolve() still
+  // failed) that the direct approach is fragile in at least one real
+  // global-install layout, for a reason not fully pinned down. Resolving
+  // package.json is the same pattern esbuild's own installer uses for
+  // this exact reason — it only depends on Node finding the package
+  // directory at all, not on any deep multi-segment specifier resolution.
+  let pkgDir
   try {
-    // require.resolve() walks node_modules exactly the way `require()`
-    // would — correct whether this dispatcher is itself inside
-    // node_modules/orchestrai/bin/ (the real installed case) or run
-    // directly from a workspace/monorepo layout during local testing.
-    return require.resolve(path.join(entry.pkg, "bin", entry.bin))
+    pkgDir = path.dirname(require.resolve(path.join(entry.pkg, "package.json")))
   } catch {
     throw new Error(
       `The "${entry.pkg}" optional dependency isn't installed. ` +
@@ -61,6 +68,17 @@ function resolveBinaryPath() {
         `Try reinstalling without those flags.`,
     )
   }
+
+  const binPath = path.join(pkgDir, "bin", entry.bin)
+  if (!existsSync(binPath)) {
+    throw new Error(
+      `The "${entry.pkg}" optional dependency is installed at ${pkgDir}, ` +
+        `but its expected binary is missing at ${binPath}. The install may ` +
+        `be corrupted — try "npm uninstall -g orchestrai && npm cache clean ` +
+        `--force && npm i -g orchestrai" to reinstall cleanly.`,
+    )
+  }
+  return binPath
 }
 
 function main() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestrai",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "OrchestrAI — run the standalone orchestrai binary via bunx/npx with nothing pre-installed. The right platform binary is installed automatically as an optional dependency; no network download at runtime.",
   "license": "MIT",
   "bin": {
@@ -11,9 +11,9 @@
     "README.md"
   ],
   "optionalDependencies": {
-    "orchestrai-windows-x64": "0.1.4",
-    "orchestrai-linux-x64": "0.1.4",
-    "orchestrai-darwin-arm64": "0.1.4"
+    "orchestrai-windows-x64": "0.1.6",
+    "orchestrai-linux-x64": "0.1.6",
+    "orchestrai-darwin-arm64": "0.1.6"
   },
   "engines": {
     "node": ">=18"