@mblua/agentscommander 0.31.0 → 0.32.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 (3) hide show
  1. package/README.md +5 -9
  2. package/install.js +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -39,19 +39,15 @@ npm view @mblua/agentscommander@latest version
39
39
 
40
40
  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.
41
41
 
42
- ### npm `0.31.0`
42
+ ### npm `0.32.0`
43
43
 
44
- `0.31.0` is the npm `latest` at this documentation commit. Its published install script downloads the `v0.31.0` native release asset, verifies it against `SHASUMS256.txt`, and renames it to the executable in the package's `bin/` directory; the launcher only spawns that binary and injects no configuration override. The `v0.31.0` native resolver, unchanged from `v0.30.5`:
44
+ `0.32.0` is the release described by this package. Its installer downloads the `v0.32.0` native release asset, verifies it against `SHASUMS256.txt`, and renames it to the unsuffixed executable in the package's `bin/` directory. The launcher spawns that binary and injects no configuration override.
45
45
 
46
- 1. selects the `AGENTSCOMMANDER_CONFIG_DIR` value verbatim when that variable is set and non-blank, running no probes;
47
- 2. otherwise derives the candidate `<native-executable-folder>/.<native-executable-stem>`, checks for a `portable.txt` marker beside the executable, and write-probes the candidate;
48
- 3. selects that candidate when the write probe succeeds, with or without the marker;
49
- 4. falls back to `$HOME/.agentscommander-new` only when the executable's parent and stem cannot be derived, or when the marker is absent and the candidate is conclusively unwritable; and
50
- 5. refuses to start on every other probe outcome (marker present but candidate unwritable, or an indeterminate probe), reporting an error that says to set `AGENTSCOMMANDER_CONFIG_DIR`.
46
+ The `v0.32.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 inspect an adjacent `portable.txt` marker or probe an adjacent configuration directory on this route. Suffixed executables retain their separate instance-location rules.
51
47
 
52
- The npm installer writes no `portable.txt`. For a normal npm `0.31.0` install with a writable global `node_modules`, the write probe succeeds and the selected directory is therefore `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/`, the same location `0.30.3` selected, now confirmed by a probe instead of assumed.
48
+ **This changes the default location from npm `0.31.0` and `0.30.5`.** Those versions normally selected `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/` when that location was writable, with their documented home fallback and refusal rules. Version `0.32.0` does not discover, copy, move or migrate any old configuration automatically. Before updating, 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.
53
49
 
54
- The previous npm version, `0.30.5`, shares this resolver exactly. The older npm version `0.30.3` ships none of this: its resolver immediately selects `<native-executable-folder>/.<native-executable-stem>` whenever that parent and stem can be derived, uses `$HOME/.agentscommander-new` only when they cannot, and never reads `AGENTSCOMMANDER_CONFIG_DIR`, inspects `portable.txt`, probes writability, or falls back to home because the adjacent path is read-only. npm never published a `0.30.4` package; that number exists only as a GitHub release. For any other published version, inspect `src-tauri/src/config/mod.rs`, `src-tauri/src/config/profile.rs`, `npm/run.js`, and `npm/install.js` at its exact `v<version>` tag; do not extrapolate from `0.31.0`, `0.30.5`, `0.30.3`, or `main`.
50
+ 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.
55
51
 
56
52
  Before an npm update or uninstall, identify the active directory with the existing binary's verified rule and exact path. The presence of a directory alone is not proof of selection.
57
53
 
package/install.js CHANGED
@@ -5,7 +5,7 @@ const crypto = require('crypto');
5
5
  const os = require('os');
6
6
  const { execSync } = require('child_process');
7
7
 
8
- const VERSION = "0.31.0"; // Must match package.json
8
+ const VERSION = "0.32.0"; // Must match package.json
9
9
  const OWNER = 'mblua';
10
10
  const REPO = 'AgentsCommander';
11
11
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mblua/agentscommander",
3
- "version": "0.31.0",
3
+ "version": "0.32.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": {