@mblua/agentscommander 0.47.0 → 0.48.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +53 -13
  2. package/install.js +1 -1
  3. package/package.json +1 -1
  4. package/run.js +15 -4
package/README.md CHANGED
@@ -5,7 +5,7 @@
5
5
  When installing through npm, use `-g` so the `agentscommander` command is available from any directory:
6
6
 
7
7
  ```bash
8
- npm install -g @mblua/agentscommander
8
+ npm install -g --allow-scripts=@mblua/agentscommander @mblua/agentscommander
9
9
  ```
10
10
 
11
11
  This installs the current `latest` release. Before installing, follow [Resolve versions and preserve configuration](#resolve-versions-and-preserve-configuration), then [Install and validate](#install-and-validate). Check the supported platforms and requirements below before installing.
@@ -15,14 +15,14 @@ This installs the current `latest` release. Before installing, follow [Resolve v
15
15
  New builds are published first under the `next` tag. To try one before it becomes the default release:
16
16
 
17
17
  ```bash
18
- npm install -g @mblua/agentscommander@next
18
+ npm install -g --allow-scripts=@mblua/agentscommander @mblua/agentscommander@next
19
19
  ```
20
20
 
21
21
  `next` builds are not fully tested and can break. Share feedback in the [#testers Discord channel](https://discord.gg/T4R8RvEFX4).
22
22
 
23
23
  ## npm website install command
24
24
 
25
- The npm website's **Install** sidebar shows the generic local-install command. For the recommended global npm installation, include `-g` as shown above.
25
+ The npm website's **Install** sidebar shows the generic local-install command. For the recommended global npm installation, include `-g` as shown above. On npm 12 and newer see [npm 12 and newer](#npm-12-and-newer).
26
26
 
27
27
  ## Choosing the npm route
28
28
 
@@ -65,21 +65,21 @@ npm view @mblua/agentscommander version
65
65
 
66
66
  The existing binary's exact resolver determines what must be preserved. The selected package's exact release tag determines post-install behavior. Verify both against the corresponding `v<version>` source tag; do not use `main` as evidence for a published npm package.
67
67
 
68
- ### npm `0.47.0`
68
+ ### npm `0.48.0`
69
69
 
70
- This version is published under `next`; the default `latest` remains `0.43.0` until promotion. Use `@next` or `@0.47.0` to install this release.
70
+ This version is published under `next`; the default `latest` remains `0.47.0` until promotion. Use `@next` or `@0.48.0` to install this release.
71
71
 
72
- `0.47.0` is the release described by this package. Its installer downloads the `v0.47.0` native release asset and verifies it against `SHASUMS256.txt`. On Windows and Linux it renames the asset to the unsuffixed executable in the package's `bin/` directory. On macOS it downloads the `agentscommander-mac-<arch>.app.tar.gz` bundle, extracts the single `.app` directory into `bin/`, and validates the executable named by the bundle's `CFBundleExecutable`. The launcher spawns that executable and injects no configuration override. A global install also creates the desktop entry points described in [Windows Start Menu shortcut](#windows-start-menu-shortcut), [macOS Launchpad and Spotlight](#macos-launchpad-and-spotlight), and [Linux application menu](#linux-application-menu).
72
+ `0.48.0` is the release described by this package. Its installer downloads the `v0.48.0` native release asset and verifies it against `SHASUMS256.txt`. On Windows and Linux it renames the asset to the unsuffixed executable in the package's `bin/` directory. On macOS it downloads the `agentscommander-mac-<arch>.app.tar.gz` bundle, extracts the single `.app` directory into `bin/`, and validates the executable named by the bundle's `CFBundleExecutable`. The launcher spawns that executable and injects no configuration override. A global install also creates the desktop entry points described in [Windows Start Menu shortcut](#windows-start-menu-shortcut), [macOS Launchpad and Spotlight](#macos-launchpad-and-spotlight), and [Linux application menu](#linux-application-menu).
73
73
 
74
- The `v0.47.0` native resolver selects a non-blank `AGENTSCOMMANDER_CONFIG_DIR` value verbatim when present. Otherwise, the normal unsuffixed npm executable selects the user's home directory plus `.agentscommander`, independently of its install location and build profile. It does not probe an adjacent configuration directory on this route. Suffixed executables use their adjacent `.agentscommander_<suffix>` directory and refuse to start when it is not writable.
74
+ The `v0.48.0` native resolver selects a non-blank `AGENTSCOMMANDER_CONFIG_DIR` value verbatim when present. Otherwise, the normal unsuffixed npm executable selects the user's home directory plus `.agentscommander`, independently of its install location and build profile. It does not probe an adjacent configuration directory on this route. Suffixed executables use their adjacent `.agentscommander_<suffix>` directory and refuse to start when it is not writable.
75
75
 
76
- **Version `0.47.0` keeps the `0.32.0` default location.** Versions `0.31.0` and `0.30.5` normally selected `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/` when that location was writable, with their documented home fallback and refusal rules. None of `0.32.0` through `0.47.0` discovers, copies, moves or migrates any old configuration automatically. Before updating from `0.31.0` or older, identify and back up the old version's active configuration. If you intend to keep using that directory, set `AGENTSCOMMANDER_CONFIG_DIR` to its verified path; otherwise arrange the intended configuration at the new home location separately. Version `0.33.0` dropped the legacy pre-v2 `codingAgentProfiles` settings migration, and later versions keep it removed.
76
+ **Version `0.48.0` keeps the `0.32.0` default location.** Versions `0.31.0` and `0.30.5` normally selected `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/` when that location was writable, with their documented home fallback and refusal rules. None of `0.32.0` through `0.48.0` discovers, copies, moves or migrates any old configuration automatically. Before updating from `0.31.0` or older, identify and back up the old version's active configuration. If you intend to keep using that directory, set `AGENTSCOMMANDER_CONFIG_DIR` to its verified path; otherwise arrange the intended configuration at the new home location separately. Version `0.33.0` dropped the legacy pre-v2 `codingAgentProfiles` settings migration, and later versions keep it removed.
77
77
 
78
- **Version `0.47.0` retains the configuration-file renaming introduced in `0.41.0`; you cannot downgrade below `0.41.0` after that migration.** On the first start it renames the files inside the active configuration directory to the layered names of the file naming convention, for example `settings.json` to `settings.30.instance.no-git.json`, once, without deleting or overwriting any file. An older version started afterwards does not find those names and starts from defaults. Back up the configuration directory before updating.
78
+ **Version `0.48.0` retains the configuration-file renaming introduced in `0.41.0`; you cannot downgrade below `0.41.0` after that migration.** On the first start it renames the files inside the active configuration directory to the layered names of the file naming convention, for example `settings.json` to `settings.30.instance.no-git.json`, once, without deleting or overwriting any file. An older version started afterwards does not find those names and starts from defaults. Back up the configuration directory before updating.
79
79
 
80
- **Version `0.47.0` keeps bounded backups of its settings file.** Every successful save archives the bytes it replaced into `settings.30.instance.no-git.backup.1.json` through `settings.30.instance.no-git.backup.5.json` in the same configuration directory, newest in slot 1. These files live beside `settings.30.instance.no-git.json`, so preserve them with it when you move or back up a configuration directory.
80
+ **Version `0.48.0` keeps bounded backups of its settings file.** Every successful save archives the bytes it replaced into `settings.30.instance.no-git.backup.1.json` through `settings.30.instance.no-git.backup.5.json` in the same configuration directory, newest in slot 1. These files live beside `settings.30.instance.no-git.json`, so preserve them with it when you move or back up a configuration directory.
81
81
 
82
- **Version `0.47.0` moves project paths into `project-paths.json`.** On the first start with legacy project fields it writes the original settings bytes to `project-paths.pre-migration.no-git.json`, then makes `project-paths.json` in the same configuration directory the only project-path source. Older versions do not read that file; back up the configuration directory before updating.
82
+ **Version `0.48.0` moves project paths into `project-paths.json`.** On the first start with legacy project fields it writes the original settings bytes to `project-paths.pre-migration.no-git.json`, then makes `project-paths.json` in the same configuration directory the only project-path source. Older versions do not read that file; back up the configuration directory before updating.
83
83
 
84
84
  The older npm `0.30.3` resolver immediately selected an executable-adjacent directory when the parent and stem were available and did not support the configuration override or portable-marker/write-probe rules. npm never published `0.30.4`; that number exists only as a GitHub release. For other versions, inspect `src-tauri/src/config/mod.rs`, `src-tauri/src/config/profile.rs`, `npm/run.js`, and `npm/install.js` at the exact `v<version>` tag.
85
85
 
@@ -90,10 +90,10 @@ Copy the complete persistent configuration directory to a user-controlled backup
90
90
  ## Install and validate
91
91
 
92
92
  ```bash
93
- npm install -g @mblua/agentscommander
93
+ npm install -g --allow-scripts=@mblua/agentscommander @mblua/agentscommander
94
94
  ```
95
95
 
96
- The command installs the current `latest` release and exits 0 on success. The package's install script downloads that package version's raw asset and `SHASUMS256.txt` from `mblua/AgentsCommander`, computes SHA-256, and fails the install on a missing record or mismatch. This does not protect against compromise of the publisher or repository account because the asset and checksum share that trust boundary.
96
+ The command installs the current `latest` release and exits 0 on success. npm 12 and newer also exit 0 when they skip the install script, so always validate with `agentscommander --version`. The package's install script downloads that package version's raw asset and `SHASUMS256.txt` from `mblua/AgentsCommander`, computes SHA-256, and fails the install on a missing record or mismatch. This does not protect against compromise of the publisher or repository account because the asset and checksum share that trust boundary.
97
97
 
98
98
  Validate the installed command:
99
99
 
@@ -104,6 +104,46 @@ agentscommander --help
104
104
 
105
105
  Both commands must exit 0. Confirm that `npm list` and the installed `package.json` report the `latest` version that `npm view @mblua/agentscommander version` returned; re-check the installed scripts, native path, and checksum correlation described above. `--help` must print the AgentsCommander command help, and on `0.31.0` or newer `agentscommander --version` must print the same version `npm list` reports. The npm package is `@mblua/agentscommander`; the installed command is `agentscommander`.
106
106
 
107
+ ### npm 12 and newer
108
+
109
+ npm 12 and newer run a package's install script only when you allow it. This package's install script downloads the executable, so without the opt-in npm still exits 0 but `bin/` stays empty and `agentscommander` reports `Cannot find AgentsCommander executable`. A package cannot allow its own scripts; the `--allow-scripts` flag in the commands above is that opt-in.
110
+
111
+ If a global install already ran without the flag, run:
112
+
113
+ ```bash
114
+ npm rebuild -g --allow-scripts=@mblua/agentscommander @mblua/agentscommander
115
+ ```
116
+
117
+ For a local (project) install, `--allow-scripts` is rejected. Add the package name to the project `package.json` before installing:
118
+
119
+ ```json
120
+ "allowScripts": { "@mblua/agentscommander": true }
121
+ ```
122
+
123
+ Or, after a blocked local install, run these two commands separately. `approve` pins the installed version, so repeat both after an upgrade:
124
+
125
+ ```bash
126
+ npm install-scripts approve @mblua/agentscommander
127
+ npm rebuild @mblua/agentscommander
128
+ ```
129
+
130
+ For `npx`, pass the flag on the first run:
131
+
132
+ ```bash
133
+ npx --allow-scripts=@mblua/agentscommander @mblua/agentscommander@<version>
134
+ ```
135
+
136
+ If `npx` already ran without the flag, it reuses that blocked folder, so the flag alone does not help. Clear the npx cache first, then run the same `npx` command again (two separate commands):
137
+
138
+ ```bash
139
+ npm cache npx rm --force
140
+ npx --allow-scripts=@mblua/agentscommander @mblua/agentscommander@<version>
141
+ ```
142
+
143
+ If the package is also installed globally or in the project, fix that install first: npx runs that install, not its cache.
144
+
145
+ If `ignore-scripts` is set (flag or `.npmrc`), remove it first; it overrides `allow-scripts`.
146
+
107
147
  ### Windows Start Menu shortcut
108
148
 
109
149
  On Windows, a global install also creates a per-user Start Menu shortcut named **AgentsCommander**, with the app icon, at `%APPDATA%\Microsoft\Windows\Start Menu\Programs\AgentsCommander.lnk`. It opens the installed `bin\agentscommander.exe`. A local install (without `-g`) creates no shortcut. To skip it, set `AGENTSCOMMANDER_NO_SHORTCUT=1` before installing. If the shortcut cannot be created, the install prints a warning and still succeeds. Installing again replaces the same shortcut.
package/install.js CHANGED
@@ -9,7 +9,7 @@ const { createStartMenuShortcut } = require('./windows-shortcut');
9
9
  const { createLaunchpadAlias } = require('./macos-alias');
10
10
  const { createDesktopEntry } = require('./linux-desktop-entry');
11
11
 
12
- const VERSION = "0.47.0"; // Must match package.json
12
+ const VERSION = "0.48.0"; // Must match package.json
13
13
  const OWNER = 'mblua';
14
14
  const REPO = 'AgentsCommander';
15
15
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mblua/agentscommander",
3
- "version": "0.47.0",
3
+ "version": "0.48.0",
4
4
  "description": "Install and run AgentsCommander, the local terminal session manager for AI coding agent teams with Claude Code, Codex, Hermes, Cursor CLI, OpenCode, and more to come.",
5
5
  "license": "MIT",
6
6
  "bin": {
package/run.js CHANGED
@@ -7,8 +7,19 @@ const { resolveBinPath } = require('./resolve-bin');
7
7
 
8
8
  const binDir = path.join(__dirname, 'bin');
9
9
 
10
- const IGNORE_SCRIPTS_HINT =
11
- 'Hint: if npm install ran with --ignore-scripts, reinstall without that flag, or run: npm rebuild -g @mblua/agentscommander';
10
+ const MISSING_EXE_HINT = [
11
+ "Hint: npm did not run this package's install script, which downloads the executable.",
12
+ 'npm 12 and newer block it unless allowed. To fix a global install, run:',
13
+ ' npm rebuild -g --allow-scripts=@mblua/agentscommander @mblua/agentscommander',
14
+ 'For a local install on npm 12 and newer, run these two commands:',
15
+ ' npm install-scripts approve @mblua/agentscommander',
16
+ ' npm rebuild @mblua/agentscommander',
17
+ 'For npx, clear the npx cache, then run npx again with the flag:',
18
+ ' npm cache npx rm --force',
19
+ ' npx --allow-scripts=@mblua/agentscommander @mblua/agentscommander',
20
+ 'If ignore-scripts is set (flag or .npmrc), remove it first; it overrides allow-scripts.',
21
+ 'On older npm, run: npm rebuild @mblua/agentscommander (add -g for a global install).',
22
+ ].join('\n');
12
23
 
13
24
  let binPath;
14
25
  try {
@@ -16,14 +27,14 @@ try {
16
27
  } catch (err) {
17
28
  console.error(`Error: ${err.message}`);
18
29
  console.error('Please ensure the package was installed correctly.');
19
- console.error(IGNORE_SCRIPTS_HINT);
30
+ console.error(MISSING_EXE_HINT);
20
31
  process.exit(1);
21
32
  }
22
33
 
23
34
  if (!fs.existsSync(binPath)) {
24
35
  console.error(`Error: Cannot find AgentsCommander executable at ${binPath}`);
25
36
  console.error('Please ensure the package was installed correctly.');
26
- console.error(IGNORE_SCRIPTS_HINT);
37
+ console.error(MISSING_EXE_HINT);
27
38
  process.exit(1);
28
39
  }
29
40