omniharness-cli 0.1.41 → 0.1.42

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 (2) hide show
  1. package/README.md +37 -39
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,54 +1,52 @@
1
1
  # omniharness-cli
2
2
 
3
- **OmniHarness** — a local-first agent orchestration harness that sits above
4
- [OmniRoute](https://omniroute.ai). It analyzes tasks, picks a strategy, selects
5
- models, drives capability-based agents, verifies results, repairs failures, and
6
- learns from past outcomes — while OmniRoute stays responsible for routing model
7
- requests to providers.
3
+ **OmniHarness** — the agent harness built for [OmniRoute](https://omniroute.ai).
4
+ Route once, run anywhere: plan, build, research, or turn a swarm loose.
8
5
 
9
- This package installs the TypeScript/Ink OmniHarness terminal UI; the `omniharness` command launches the bundled CLI.
6
+ This package ships the interactive **terminal UI** (Ink/React). The orchestration
7
+ core and a headless CLI live in the [Go source tree](https://github.com/mattycigemp-crypto/omniharness).
10
8
 
11
- ## Install
12
-
13
- ```sh
9
+ ```bash
14
10
  npm install -g omniharness-cli
15
- # If PowerShell still cannot find it, open a new terminal so npm's global bin
16
- # directory is reloaded into PATH.
17
- ```
18
-
19
- ## Quick start
20
-
21
- ```sh
22
- omniharness doctor # verifies endpoint + auth status, safely
23
- omniharness run "add a README" --headless # runs in the current directory
24
- omniharness # interactive cockpit (TUI)
25
- omniharness sessions # persisted sessions
26
- omniharness models # provider/model catalog from OmniRoute
27
- omniharness update # check npm and self-update to the latest release
11
+ omniharness # launch the TUI in the current working directory
28
12
  ```
29
13
 
30
- The harness treats the **current working directory** as the workspace.
14
+ `omniharness update` self-updates to the latest release; `omniharness --version`
15
+ prints the installed version. Everything else happens inside the TUI.
31
16
 
32
- ## Configuration
17
+ ## Connect to OmniRoute
33
18
 
34
19
  | Variable | Meaning |
35
20
  |---|---|
36
- | `OMNIROUTE_URL` | OmniRoute endpoint (default `http://127.0.0.1:20128`, the HTTP API port) |
37
- | `OMNIROUTE_API_KEY` | OmniRoute API key — `Authorization: Bearer <key>` on every request |
38
- | `OMNIROUTE_MGMT_TOKEN` | OmniRoute management token (`manage` scope) — when set, OmniRoute's MCP tools are discovered and exposed to the agent |
21
+ | `OMNIROUTE_URL` | Gateway endpoint (default `http://127.0.0.1:20128`) |
22
+ | `OMNIROUTE_API_KEY` | `Authorization: Bearer <key>` on every request — held **in memory only**, never written to config, sessions, logs, or telemetry |
23
+ | `OMNIROUTE_MGMT_TOKEN` | Management token (`manage` scope) — when set, OmniRoute's MCP tools are discovered and offered to the agent |
24
+
25
+ If `OMNIROUTE_API_KEY` is unset, the TUI asks for it on launch and keeps it in
26
+ memory only. It is redacted from all output.
27
+
28
+ ## Inside the TUI
29
+
30
+ - **Modes** (`Ctrl+E` cycles): `plan` · `build` · `research` · `crazy`. Crazy mode
31
+ auto-approves every call and fans an independent plan out across parallel
32
+ worker agents.
33
+ - **Native scrollback is the history** — settled turns flow into your terminal's
34
+ own buffer; the full transcript is restored on exit.
35
+ - **Route ribbon** — every reply is labelled with the provider it came from;
36
+ failovers appear inline.
37
+ - **Context meter**, per-tool cards with diffs, scoped-trust approvals, input
38
+ queued during a run, `Ctrl+Y` clipboard copy over OSC 52, session resume,
39
+ prompt history, `/find`, `/chapters`.
39
40
 
40
- If `OMNIROUTE_API_KEY` is unset, the harness asks you to paste the key on
41
- interactive launch and holds it **in memory only** — it is never written to
42
- config, sessions, logs, or telemetry. The key is redacted from all output;
43
- `doctor` masks it as `key_<last4>`.
41
+ Slash commands: `/help` `/clear` `/sessions` `/save <name>` `/forget <name>`
42
+ `/attach <files>` `/find <text>` `/chapters`.
44
43
 
45
44
  ## Notes
46
45
 
47
- - Node.js 20 or newer is required to run the CLI.
48
- - Publishing is automatic: every push to `main` on GitHub runs
49
- `.github/workflows/publish.yml`, which bumps the version, verifies
50
- (vet + tests), builds, and publishes via **npm trusted publishing (OIDC)**
51
- — no npm token is stored anywhere, and provenance is attached automatically.
52
- Locally, `scripts/release-npm.sh` (or `scripts\release-npm.ps1`) does the
53
- same; add `--dry-run` to skip the publish, or pass `--minor`/`--major`/an
54
- explicit version to control the bump.
46
+ - Node.js 20 or newer.
47
+ - Publishing is automatic: every push to `main` runs
48
+ `.github/workflows/publish.yml`, which verifies both the Go and TypeScript
49
+ suites, builds, and publishes via **npm trusted publishing (OIDC)** — no token
50
+ is stored, provenance is attached automatically. Locally,
51
+ `scripts/release-npm.sh` does the same (`--dry-run` to skip publish;
52
+ `--minor` / `--major` / an explicit version to control the bump).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "omniharness-cli",
3
- "version": "0.1.41",
3
+ "version": "0.1.42",
4
4
  "description": "OmniHarness — local-first agent orchestration harness for OmniRoute.",
5
5
  "license": "MIT",
6
6
  "type": "module",