@actions-json/bridge 0.1.119 → 0.1.121

package/README.md

@@ -1,44 +1,38 @@
 # @actions-json/bridge
 
 Run the [actions.json](https://yaniv256.github.io/actions.json/) MCP bridge with
-`npx` — no Rust toolchain required. On first run this downloads the prebuilt
-`actions-json-mcp` binary for your platform from the GitHub release, caches it,
-and runs it with the arguments you pass.
+`npx` — no Rust toolchain, no setup. On first run it downloads the prebuilt
+`actions-json-mcp` binary for your platform, bundles the primitive dictionary
+(so you don't pass `--actions`), and scaffolds a storage workspace at
+`~/.actions-json/storage` (so you don't pass `--storage-root`).
 
 ## Usage
 
 ```bash
-npx @actions-json/bridge mcp \
-  --bind 0.0.0.0:17345 \
-  --actions /abs/path/to/overlay.actions.json \
-  --storage-root /abs/path/to/actions.json.storage
+npx @actions-json/bridge mcp
 ```
 
-Register it with a coding agent the same way — for Claude Code:
+Register it with a coding agent — Claude Code:
 
 ```bash
-claude mcp add actions-json -- \
-  npx -y @actions-json/bridge mcp \
-  --bind 0.0.0.0:17345 \
-  --actions /abs/path/to/overlay.actions.json \
-  --storage-root /abs/path/to/actions.json.storage
+claude mcp add actions-json -- npx -y @actions-json/bridge mcp
 ```
 
-For Codex (`~/.codex/config.toml`):
-
-```toml
-[mcp_servers.actions-json]
-command = "npx"
-args = [
-  "-y", "@actions-json/bridge", "mcp",
-  "--bind", "0.0.0.0:17345",
-  "--actions", "/abs/path/to/overlay.actions.json",
-  "--storage-root", "/abs/path/to/actions.json.storage",
-]
+Codex:
+
+```bash
+codex mcp add actions-json -- npx -y @actions-json/bridge mcp
 ```
 
-All arguments after the binary are passed straight through to `actions-json-mcp`.
-See [Getting Started](https://yaniv256.github.io/actions.json/getting-started.html).
+Overrides (the defaults are skipped when you pass your own):
+
+- `--storage-root <dir>` — use a different storage workspace. Or set
+  `ACTIONS_JSON_STORAGE`.
+- `--actions <file>` — use a custom primitive dictionary instead of the bundled
+  one.
+
+All arguments after the binary pass straight through to `actions-json-mcp`. See
+[Getting Started](https://yaniv256.github.io/actions.json/getting-started.html).
 
 ## Platforms
 

package/bin/cli.js

@@ -4,10 +4,40 @@
 // Thin launcher: ensure the prebuilt actions-json-mcp binary is present
 // (downloading it on first run), then exec it with whatever args were passed.
 // Example:
-//   npx @actions-json/bridge mcp --bind 0.0.0.0:17345 --actions ... --storage-root ...
+//   npx @actions-json/bridge mcp --storage-root .storage
 
+const path = require('node:path');
 const { spawn } = require('node:child_process');
 const { ensureBinary } = require('../lib/install');
+const { ensureStorageRoot } = require('../lib/storage');
+
+// The primitive dictionary (browser-control tool catalog) ships with this
+// package — it's a fixed runtime file, not user config. When the caller runs a
+// subcommand that needs it and didn't pass --actions, default to the bundled
+// copy so users don't have to know its path.
+const BUNDLED_ACTIONS = path.join(__dirname, '..', 'dictionary', 'overlay.actions.json');
+const SUBCOMMANDS_NEEDING_ACTIONS = new Set(['mcp', 'serve']);
+
+function isRunSubcommand(args) {
+  return SUBCOMMANDS_NEEDING_ACTIONS.has(args[0]) &&
+    !args.includes('--help') && !args.includes('-h');
+}
+
+// Inject defaults the user shouldn't have to specify: the bundled primitive
+// dictionary (--actions) and a scaffolded storage root (--storage-root). Both
+// are skipped if the user passed their own.
+function withDefaults(args) {
+  if (!isRunSubcommand(args)) return args;
+  const out = [args[0]];
+  if (!args.includes('--actions')) {
+    out.push('--actions', BUNDLED_ACTIONS);
+  }
+  if (!args.includes('--storage-root')) {
+    out.push('--storage-root', ensureStorageRoot());
+  }
+  out.push(...args.slice(1));
+  return out;
+}
 
 async function main() {
   let bin;
@@ -19,7 +49,7 @@ async function main() {
     return;
   }
 
-  const args = process.argv.slice(2);
+  const args = withDefaults(process.argv.slice(2));
   const child = spawn(bin, args, { stdio: 'inherit' });
 
   // Forward termination signals so the bridge shuts down cleanly.