@eventmodelers/cli 1.0.55 → 1.0.57

package/README.md

@@ -116,6 +116,9 @@ npx @eventmodelers/cli run                          # start the agent loop (ralp
 npx @eventmodelers/cli run --ollama                 # same, via local Ollama (ralph-ollama.js)
 npx @eventmodelers/cli run --bash                   # bash-only loop, no realtime (ralph.sh)
 npx @eventmodelers/cli run --local                  # skip platform config/credential lookup entirely — local-only, no board sync
+npx @eventmodelers/cli run --modeling               # modeling-kit: warm Claude process driven by the board's prompt queue
+npx @eventmodelers/cli run --standalone             # same, plus acting on board changes unprompted — and needs no install at all
+npx @eventmodelers/cli run --standalone --board-id <uuid>  # …from any directory, against any board (see Power users)
 npx @eventmodelers/cli fetch --context <name>                     # pull full slice detail for one context on the board into <kit-dir>/.slices/
 npx @eventmodelers/cli fetch --context <name> --slice-id <id>     # same, then print just that slice
 npx @eventmodelers/cli fetch --context <name> --slice-title <title> # same, then print just the slice matching this title
@@ -153,6 +156,83 @@ This scaffolds `.build-kit/CLAUDE.md`, `lib/prompt.md`, `lib/backend-prompt.md`,
 
 Installing both a build stack and `init-modeling` into the same project reuses this one `.eventmodelers/config.json` — run whichever `init` command second and it finds the existing config already satisfies the required fields and skips straight past the credential prompt.
 
+### The modeling agent — `run --modeling` and `--standalone`
+
+A modeling-kit install has one runtime: a warm Claude process the CLI keeps alive across
+turns and feeds directly over stdin, so a prompt typed (or spoken) on the board is picked up
+with no cold start and no `tasks.json` round trip.
+
+```bash
+npx @eventmodelers/cli run --modeling               # react to prompts sent to this board
+npx @eventmodelers/cli run --standalone             # …and to board changes, on its own initiative
+```
+
+`--standalone` implies `--modeling`, so you never need both.
+
+**No install required.** A modeling agent never touches the directory it was started from —
+it works against the board over MCP/REST — so it doesn't need a kit scaffolded there. When
+the current directory has no modeling kit, `run --modeling`/`run --standalone` fall back to a
+single global install under `~/.eventmodelers/kit`, initialized on first use and refreshed
+when you upgrade the CLI. Pass `--global` to prefer it even when a local kit does exist.
+
+```bash
+npx @eventmodelers/cli run --standalone --board-id <uuid>   # from any directory, nothing written there
+```
+
+**Credentials are per board, not per directory.** The first time this machine runs a board it
+asks one question — does this board get credentials of its own, or does it use your
+account-wide ones? Answer once and it's remembered: either the board's credentials or a
+`useGlobal` marker lands in `~/.eventmodelers/boards/<board>.json`, and you're not asked
+again. The question is skipped entirely when the answer is already implied (credentials given
+on the command line) or when there's no one to ask (`--print`, or a non-interactive stdin such
+as CI or a process supervisor).
+
+To configure a board up front instead, paste the blob from
+[app.eventmodelers.ai/account](https://app.eventmodelers.ai/account):
+
+```bash
+npx @eventmodelers/cli init-config --credentials "token=<uuid>,boardId=<uuid>,organizationId=<uuid>,baseUrl=https://api.eventmodelers.ai"
+npx @eventmodelers/cli run --standalone --board-id <uuid>    # all it needs from here on
+```
+
+`--credentials` also takes the equivalent JSON, or `-` to read either from stdin, so a token
+need never appear in your shell history or in `ps`. `run` accepts it too, for configuring and
+starting in one command. Resolution order for a run is `--credentials` and the individual
+`--token`/`--organization-id`/`--board-id`/`--base-url` flags, then `EVENTMODELERS_*` env vars,
+then `~/.eventmodelers/boards/<board>.json`, then the usual `.eventmodelers/config.json` walk,
+and finally the account's default board. Whatever a run resolves is saved back to the
+per-board file (`0600`, in a `0700` directory) along with a stable agent id for the board's
+alive-ping. One machine can therefore drive several boards, across several accounts, at once.
+The global kit itself holds no credentials at all — the token reaches `claude` through the
+spawned process's environment.
+
+A kit installed in the current directory still wins by default and behaves exactly as before,
+reading its own `.eventmodelers/config.json`.
+
+Without `--standalone` the agent only ever answers direct messages. With it, the loop also
+subscribes to the board's own change channel — the same one the canvas and the build agents
+use — and when the board falls quiet after someone edits it, the agent gets a turn nobody
+asked for and decides for itself whether there's something a human collaborator would
+obviously have done: example data on a freshly placed element, a missing attribute on the
+rest of the chain, a screen for an empty SCREEN node, a question comment on a gap. It does at
+most one focused thing per change, adds rather than deletes, and answers `NOOP` when there's
+nothing worth doing (see the "Standalone board-change turns" section in
+`.agent-modeling-kit/CLAUDE.md`).
+
+Its own writes come back on that same channel and the platform can't tell them apart from a
+human's, so the lane is deliberately damped: it waits for a quiet period, ignores everything
+that arrives while a turn runs or shortly after one ends, and never fires twice in quick
+succession. Override the three windows if the defaults don't suit your board:
+
+| Env var | Default | What it controls |
+|---|---|---|
+| `EVENTMODELERS_STANDALONE_DEBOUNCE_MS` | `8000` | quiet period before a board change turns into a turn |
+| `EVENTMODELERS_STANDALONE_ECHO_WINDOW_MS` | `20000` | after a turn, how long incoming changes are treated as the agent's own echo |
+| `EVENTMODELERS_STANDALONE_MIN_INTERVAL_MS` | `60000` | floor between two self-directed turns |
+
+Direct prompts always outrank the agent's own initiative — a standalone turn waits while
+anything from the prompt queue is running.
+
 ### Installing skills globally
 
 By default, skills are copied into the project's own `.claude/skills/`. Pass `--global` to `init` or `init-modeling` to install them into `~/.claude/skills/` instead — available in every project without re-running the installer each time:
@@ -248,6 +328,8 @@ Running any command from inside `~/projects/checkout-app` resolves `organization
 ```bash
 npx @eventmodelers/cli init-config                      # interactive, writes to ./.eventmodelers/config.json
 npx @eventmodelers/cli init-config --board-id <uuid>     # non-interactive, just overrides one field
+npx @eventmodelers/cli init-config --credentials "token=...,boardId=...,organizationId=...,baseUrl=..."  # configure ONE board (~/.eventmodelers/boards/<board>.json), no prompts
+npx @eventmodelers/cli init-config --credentials -        # same, read from stdin (keeps the token out of shell history)
 ```
 
 ### Env vars and `--config` (scripted/CI installs)

package/RELEASE_NOTES.md

@@ -1,3 +1,15 @@
+## v1.0.56
+
+### Features
+- `run --standalone` no longer needs a modeling kit installed in the current directory. With none there, it falls back to a single global install under `~/.eventmodelers/kit`, initialized on first use and refreshed when the CLI version changes — so `npx @eventmodelers/cli run --standalone --board-id <uuid>` works from anywhere and writes nothing into the directory it was started from. `--global` selects that install explicitly even when a local kit exists.
+- `--standalone` now implies `--modeling` — it already refused every other runner, so requiring both flags only made the shorter command fail.
+- `run` accepts `--token`/`--board-id`/`--organization-id`/`--base-url`, the same credential flags `init` and `init-config` take, so credentials can be given per agent run rather than per directory. They're stored per board in `~/.eventmodelers/boards/<board>.json` (`0600`) together with a stable agent id, so later runs for the same board need only `--board-id`. One machine can drive several boards across several accounts at once.
+- The first run for a board asks once whether it should have credentials of its own or use the account-wide ones, and remembers the answer — either the credentials or a `useGlobal` marker is written to `~/.eventmodelers/boards/<board>.json`. The question is skipped when credentials are given on the command line, under `--print`, or when stdin is not interactive, so CI and process supervisors never block on it.
+- `init-config --credentials "token=...,boardId=...,organizationId=...,baseUrl=..."` configures a single board non-interactively from the blob app.eventmodelers.ai/account hands out. The equivalent JSON works too, and `-` reads either from stdin so a token need not appear in shell history or `ps`. `run --credentials` takes the same value, for configuring and starting in one command.
+
+### Fixes
+- `init --modeling` no longer runs `npm install` in the kit dir — modeling-kit's `package.json` declares no dependencies and exists only for its `"type": "module"`.
+
 ## v0.0.38
 
 ### Features