@mblua/agentscommander 0.30.3 → 0.30.5
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.
- package/README.md +67 -15
- package/install.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,32 +1,84 @@
|
|
|
1
|
-
# AgentsCommander
|
|
1
|
+
# AgentsCommander from npm
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
For developers who deliberately choose the secondary npm route, this page defines the supported hosts, install command, verification signal, and configuration precaution.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
npm is not the recommended first install. Start with the reviewable [Coding Agent installation contract](https://github.com/mblua/AgentsCommander/blob/main/docs/install-with-agent.md), which detects the host, selects an approved stable-release asset, verifies its checksum, and waits for approval.
|
|
6
6
|
|
|
7
|
-
##
|
|
7
|
+
## Platform boundary
|
|
8
|
+
|
|
9
|
+
Use this package only on these documented combinations:
|
|
10
|
+
|
|
11
|
+
| Host | Native architecture | Status |
|
|
12
|
+
|---|---|---|
|
|
13
|
+
| Windows 10 version 1809 or newer, or Windows 11 | x86_64 / AMD64 | Fully supported |
|
|
14
|
+
| Linux | x86_64 / AMD64 | Partial and in progress; continue only after acknowledging the limitation |
|
|
15
|
+
| macOS | Any | Not supported; do not install through npm |
|
|
16
|
+
| Any other OS or architecture | Any | Unsupported; do not substitute an asset or use emulation |
|
|
17
|
+
|
|
18
|
+
The current npm installer does not enforce this complete allowlist: its asset mapping treats architectures other than `arm64` as `x86_64`. An asset selection or download is not a support promise. Follow the canonical [platform gates](https://github.com/mblua/AgentsCommander/blob/main/docs/install-with-agent.md#support-gates).
|
|
19
|
+
|
|
20
|
+
## Requirements
|
|
21
|
+
|
|
22
|
+
- Node.js 18 or newer.
|
|
23
|
+
- npm.
|
|
24
|
+
- One supported Coding Agent CLI installed and authenticated separately: Claude Code, Codex, Antigravity, or Pi.
|
|
25
|
+
|
|
26
|
+
AgentsCommander does not install or authenticate Coding Agent CLIs for you.
|
|
27
|
+
|
|
28
|
+
## Resolve versions and preserve configuration
|
|
29
|
+
|
|
30
|
+
Before an install, update, or uninstall, resolve and report the exact existing package and binary versions, then the exact registry release selected for comparison. For an install or update, that selected release must also be the version you install; for an uninstall, report that no replacement will be installed.
|
|
8
31
|
|
|
9
32
|
```bash
|
|
10
|
-
npm
|
|
33
|
+
npm list -g @mblua/agentscommander --depth=0
|
|
34
|
+
npm root -g
|
|
35
|
+
npm view @mblua/agentscommander@latest version
|
|
11
36
|
```
|
|
12
37
|
|
|
13
|
-
|
|
38
|
+
`npm list` reports the installed package version and can exit nonzero when the package is absent. `npm root -g` exits 0 and prints the global `node_modules` directory. Use that root to inspect the installed `@mblua/agentscommander/package.json`, `install.js`, `run.js`, and native file under `bin/`. Correlate the package-manager record and `package.json` version with the install script's version and release URL, the launcher's exact native path, and the corresponding GitHub tag, asset, and checksum. `npm view` reports the selected registry version without installing it. If the local records, independent release evidence, native file, or selected version disagree or cannot be identified exactly, stop before mutation. Do not probe the native binary for a self-reported version unless its exact tag proves support; `v0.30.3` and `main` at this documentation commit do not support such a flag.
|
|
39
|
+
|
|
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
|
+
|
|
42
|
+
### npm `0.30.3`
|
|
43
|
+
|
|
44
|
+
The published `0.30.3` install script downloads the `v0.30.3` native release asset, and its launcher only spawns that binary from the package's `bin/` directory. It injects no configuration override. The native resolver:
|
|
45
|
+
|
|
46
|
+
1. immediately selects `<native-executable-folder>/.<native-executable-stem>` when the executable path has a parent and file stem; and
|
|
47
|
+
2. uses `$HOME/.agentscommander-new` only when that parent and stem cannot be derived.
|
|
48
|
+
|
|
49
|
+
Release `v0.30.3` does not read `AGENTSCOMMANDER_CONFIG_DIR`, inspect `portable.txt`, probe candidate writability, or fall back to home because the adjacent path is read-only. For a normal npm `0.30.3` install, the selected directory is therefore `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/`.
|
|
50
|
+
|
|
51
|
+
The public override, marker, write probes, and conclusively-unwritable home fallback documented for the newer resolver are present on `main` but unpublished in `0.30.3`. Apply them only to a development build from matching source, or to a later npm version after verifying that version's exact release tag and package launcher. 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 tag; do not extrapolate either `v0.30.3` or `main` and do not invent a cutoff version.
|
|
52
|
+
|
|
53
|
+
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.
|
|
54
|
+
|
|
55
|
+
Copy the complete persistent configuration directory to a user-controlled backup and verify the copy before running npm. Stop before an update or uninstall if more than one plausible directory exists, existing state cannot be attributed safely, the exact existing version or launch context is unknown, a selected candidate is mounted/read-only and ephemeral, or any other evidence is ambiguous. If selection is unambiguous and the selected persistent directory does not exist, record that there is no existing configuration to preserve. See the versioned [configuration-selection rule](https://github.com/mblua/AgentsCommander/blob/main/docs/features/portable-instances.md#config-directory-rule).
|
|
56
|
+
|
|
57
|
+
## Install and validate
|
|
14
58
|
|
|
15
59
|
```bash
|
|
16
|
-
agentscommander
|
|
60
|
+
npm install -g @mblua/agentscommander@<version>
|
|
17
61
|
```
|
|
18
62
|
|
|
19
|
-
The
|
|
63
|
+
Replace `<version>` with the exact version already inspected and approved; do not leave the install unpinned after resolving `latest`. The command 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.
|
|
64
|
+
|
|
65
|
+
Validate the installed command:
|
|
20
66
|
|
|
21
|
-
|
|
67
|
+
```bash
|
|
68
|
+
npm list -g @mblua/agentscommander --depth=0
|
|
69
|
+
agentscommander --help
|
|
70
|
+
```
|
|
22
71
|
|
|
23
|
-
|
|
72
|
+
Both commands must exit 0. Confirm that `npm list` and the installed `package.json` report the approved package version; re-check the installed scripts, native path, and checksum correlation described above. `--help` must print the AgentsCommander command help. The npm package is `@mblua/agentscommander`; the installed command is `agentscommander`.
|
|
24
73
|
|
|
25
|
-
|
|
74
|
+
## Uninstall
|
|
26
75
|
|
|
27
|
-
|
|
76
|
+
Identify, back up, and verify the version-selected configuration as described above, then run:
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
npm uninstall -g @mblua/agentscommander
|
|
80
|
+
```
|
|
28
81
|
|
|
29
|
-
|
|
30
|
-
- One supported coding-agent CLI installed separately: Claude Code, Codex, Antigravity, or Pi
|
|
82
|
+
Success exits 0. Restore a previous version or remove the saved configuration only as a separate, deliberate action.
|
|
31
83
|
|
|
32
|
-
|
|
84
|
+
For stable-release downloads and rollback rules, use the [manual alternatives](https://github.com/mblua/AgentsCommander/blob/main/docs/install-with-agent.md#manual-alternatives).
|
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.30.
|
|
8
|
+
const VERSION = "0.30.5"; // 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.30.
|
|
3
|
+
"version": "0.30.5",
|
|
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": {
|