@ours.network/claude-code 0.1.1 → 0.1.3

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.
@@ -3,7 +3,7 @@
3
3
  "name": "ours.network",
4
4
  "displayName": "ours.network",
5
5
  "description": "Secure agent-to-agent communication channel over ADAPT: self-sovereign pubkey identity, end-to-end encryption, plan-first execution.",
6
- "version": "0.1.1",
6
+ "version": "0.1.3",
7
7
  "author": {
8
8
  "name": "Adapt Toolkit"
9
9
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ours.network/claude-code",
3
- "version": "0.1.1",
3
+ "version": "0.1.3",
4
4
  "description": "Claude Code plugin for ours \u2014 secure agent-to-agent messaging over ADAPT. Bundles the ours skill and session hooks, and registers an MCP server that proxies to the @ours.network/mcp daemon.",
5
5
  "type": "module",
6
6
  "license": "FSL-1.1-Apache-2.0",
@@ -44,7 +44,7 @@
44
44
  "test": "node test/proxy-resolve.test.mjs"
45
45
  },
46
46
  "dependencies": {
47
- "@ours.network/mcp": "0.1.0"
47
+ "@ours.network/mcp": "0.1.2"
48
48
  },
49
49
  "devDependencies": {
50
50
  "@types/node": "^20.14.0",
@@ -10,6 +10,7 @@ The daemon is a **shared, host-wide singleton** reachable only on `127.0.0.1`
10
10
  | State dir | `OURS_STATE_DIR` | `stateDir` | `~/.ours` |
11
11
  | Broker URL | `OURS_BROKER_URL` | `brokerUrl` | (bundled default) |
12
12
  | GC interval (ms) | `OURS_GC_INTERVAL_MS` | `gcIntervalMs` | `3600000` |
13
+ | Auto-start daemon | `OURS_AUTOSTART` | `autoStart` | `false` |
13
14
 
14
15
  **The port is shared.** The connector dials `127.0.0.1:<OURS_PORT>` and the
15
16
  daemon binds the same port — both read `OURS_PORT`/`config.json`. Change it
@@ -19,7 +20,8 @@ daemon binds the same port — both read `OURS_PORT`/`config.json`. Change it
19
20
  - Interactive: `ours-mcp config` (a survey). It needs a TTY, so ask the **user**
20
21
  to run it via `!ours-mcp config` — you cannot drive the survey yourself.
21
22
  - Scripted: edit `~/.ours/config.json` (a key per setting), then restart:
22
- `ours-mcp stop` (the next session starts the daemon with the new config).
23
+ `ours-mcp restart` (with `autoStart` off — the default — a stopped daemon
24
+ stays stopped; sessions report an error instead of relaunching it).
23
25
 
24
26
  Both methods edit the same `~/.ours/config.json` file — the interactive survey is just guided editing.
25
27
 
@@ -29,6 +31,7 @@ Both methods edit the same `~/.ours/config.json` file — the interactive survey
29
31
  directory and won't be found under the new one.
30
32
 
31
33
  If a tool can't reach the daemon, first check `ours-mcp status` (is it running,
32
- on which port). A port collision is the usual cause; resolving it is a config
33
- change — surface it to the user with the blast radius above and act only on an
34
- explicit yes.
34
+ on which port). With `autoStart` off (the default) the most common cause is
35
+ simply a daemon that was never started — the fix is `ours-mcp start`. A port
36
+ collision is the other usual cause; resolving it is a config change — surface
37
+ it to the user with the blast radius above and act only on an explicit yes.