premanmcp 1.1.4 → 1.1.6

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 CHANGED
@@ -18,6 +18,65 @@ four-tool PreMan conversation protocol:
18
18
 
19
19
  PreMan can add private agent capabilities without publishing a new npm package.
20
20
 
21
+ ## Installing
22
+
23
+ ```bash
24
+ npm install -g premanmcp # once; this is what puts `preman` on your PATH
25
+ preman install # account, desktop app, integrations
26
+ preman update # later, to get the newest version
27
+ ```
28
+
29
+ `preman install` walks the whole setup and installs the desktop app as part of
30
+ it — no question asked, because an account with no app is the state people got
31
+ stuck in. `--no-desktop` (or `PREMAN_NO_DESKTOP=1`) skips it, and it is skipped
32
+ automatically off macOS, where there is no build. The git pre-push hook is the
33
+ one thing still asked about, since it changes what happens on every push.
34
+
35
+ `preman install --cursor` writes Cursor's MCP config and nothing else, which is
36
+ what plain `install` used to mean; `install --api-key …` and
37
+ `install --project --backend …` are unchanged.
38
+
39
+ Nothing needs installing to try it: `npm exec -y premanmcp@latest -- <command>`
40
+ runs any of these once, fetching the newest version each time.
41
+
42
+ ## The `preman` terminal session
43
+
44
+ Installed globally, a bare `preman` opens an interactive session with the PreMan
45
+ agent in your terminal — the same agent, workspace and conversation as the app,
46
+ so anything started here is visible there.
47
+
48
+ ```bash
49
+ preman # open a session (signs you in if needed)
50
+ preman "which endpoints broke today?" # open one with the first message sent
51
+ preman chat --continue # pick up the most recent conversation
52
+ preman chat -p "list my endpoints" # one turn, printed, then exit
53
+ ```
54
+
55
+ Inside a session: `/help`, `/new`, `/conversations`, `/resume <id>`, `/app`,
56
+ `/eval`, `/clear`, `/exit`. `/eval list` shows what your agent can be measured
57
+ on, numbered; `/eval on 3 12` or `/eval on sycophancy` switches those on (a
58
+ number, a `3-7` range, `all`, an id, or enough of one to be unambiguous), `/eval
59
+ off` the same in reverse, and `/eval` runs what is on. `/eval defaults` reads
60
+ what this project says about itself, picks a few behaviours that suit it, and
61
+ switches those on — without an eval provider key on the account it falls back to
62
+ a curated shortlist and says so. A finished run prints its results here: what
63
+ was scored, what was flagged, what never ran, and why a failed run failed. The
64
+ link underneath opens the PreMan desktop app when it is installed (a build older
65
+ than 0.4.0 comes forward on whatever it was showing rather than on the run), and
66
+ the run's dashboard URL is always printed with it.
67
+
68
+ A session takes a screen of its own, the way `vim` does: nothing above it is
69
+ scrollable, and leaving hands your shell back exactly as it was with one line
70
+ saying how to resume. Ctrl+C stops the current turn (PreMan keeps working on it)
71
+ or clears a half-typed line; pressed again within two seconds it leaves. Ctrl+D
72
+ and `/exit` leave straight away. However the session ends -- including a closed
73
+ tab or a `kill` -- the terminal is put back: scrolling region released, title
74
+ cleared, cursor shown.
75
+
76
+ Piped or redirected stdin with no arguments stays the stdio MCP server below, so
77
+ an MCP host launching this package is unaffected. `preman start` asks for the
78
+ server explicitly.
79
+
21
80
  ## Marketplace users
22
81
 
23
82
  Do not install this package. The PreMan Codex/ChatGPT plugin connects directly