memshell-party-cli 0.3.1 → 0.3.2

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "memshell-party-cli",
3
- "version": "0.3.1",
3
+ "version": "0.3.2",
4
4
  "description": "Command-line client and MCP server for MemShellParty (party.mem.mk) — generate Java memory shells and probes from the terminal.",
5
5
  "keywords": [
6
6
  "memshell",
@@ -198,10 +198,10 @@ Flag soup gets old fast. Save each working shell into a **project** (a named gro
198
198
  with an optional remark and category), then reference it as `<project>/<shell>`:
199
199
 
200
200
  ```bash
201
- memparty target save hw222/bh9060 -u <shell-url> -t behinder --pass rebeyond \
201
+ memparty save hw222/bh9060 -u <shell-url> -t behinder --pass rebeyond \
202
202
  --header-name User-Agent --header-value <headerValue-from-gen-json> \
203
203
  --remark "内网测试环境" --category test --shell-remark "root 权限"
204
- memparty target list # everything, or --category test
204
+ memparty list # everything, or --category test
205
205
  memparty exec hw222/bh9060 --cmd "whoami" # no other flags needed
206
206
  memparty exec hw222 --cmd "id" # bare project works when it holds one shell
207
207
  ```
@@ -214,7 +214,7 @@ The store lives at `~/.memparty/targets.json`.
214
214
 
215
215
  ## Step 7 — Audit with the operation log
216
216
 
217
- Every operation (gen, probe, connect, exec, target save/note/remove) is appended to
217
+ Every operation (gen, probe, connect, exec, save/note/remove) is appended to
218
218
  `~/.memparty/operations.jsonl` — no credentials, no payload bytes; exec output is truncated.
219
219
  Query it to recall what was done against a target:
220
220