harborloop 0.6.4 → 0.6.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 +13 -13
- package/bin/checksums.json +7 -7
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -24,16 +24,16 @@ Then `/harbor:login` in Claude Code, or `$harbor:login` in Codex. See
|
|
|
24
24
|
|
|
25
25
|
| | |
|
|
26
26
|
|---|---|
|
|
27
|
-
| `harbor init` | Sign in, install the hooks,
|
|
27
|
+
| `harbor init` | Sign in, install the hooks, turn Harbor on in this repo (in its Space; `--no-bind` leaves it off). Idempotent. Wires every agent it finds; `--cursor` / `--no-cursor` and `--codex` / `--no-codex` override detection. Asks before sending the repo's committed `CLAUDE.md` / `AGENTS.md` to your team's review queue, once per file; `--import-rules` sends without asking, `--no-import-rules` never sends, and `harbor update` never sends. `--headless` is for a cloud agent's setup script, see below. |
|
|
28
28
|
| `harbor doctor` | Is it actually working? `--offline`, `--json`, `--days N` |
|
|
29
29
|
| `harbor status` | This repo, from local files only. No network. |
|
|
30
|
-
| `harbor bind [
|
|
30
|
+
| `harbor bind [Space]` | Turn Harbor on in this repo, in a Space: the only one, or it asks. On a bound repo, `harbor bind --project <Space>` moves it (an owner, admin or curator can). Harbor stays off in every repo you do not bind. |
|
|
31
31
|
| `harbor workspaces` | Which workspaces you can reach, and the one this machine uses. `--json` |
|
|
32
32
|
| `harbor daily` | What the hooks run once a day in the background: renew the sign-in, send each connected repo's facts, report this machine's harborloop version, check for a newer release. |
|
|
33
33
|
| `harbor off` | Pause this repo. `--capture` keeps recall. `--global` for the machine. |
|
|
34
34
|
| `harbor on` | Resume. `--global` clears a machine-wide pause. |
|
|
35
35
|
| `harbor login` | Re-authenticate. `--no-browser` to paste a code instead. `--workspace <id>` switches workspace **without** the browser. |
|
|
36
|
-
| `harbor logout` |
|
|
36
|
+
| `harbor logout` | Sign this machine out: removes `~/.harbor/auth.json` and the MCP entry (and its bearer) from each agent's config. The hooks stay installed and do nothing until you sign in again. |
|
|
37
37
|
| `harbor uninstall` | Take Harbor off this machine: the hooks, the MCP entries and `~/.harbor`. |
|
|
38
38
|
|
|
39
39
|
There is deliberately no `ask`, no `learnings`, no `sources`. Your agent reaches
|
|
@@ -54,7 +54,7 @@ Create a workspace agent key in Harbor's settings, then give the environment
|
|
|
54
54
|
this setup script:
|
|
55
55
|
|
|
56
56
|
```
|
|
57
|
-
HARBOR_AGENT_KEY=<your key> npx -y harborloop@
|
|
57
|
+
HARBOR_AGENT_KEY=<your key> npx -y harborloop@latest init --headless
|
|
58
58
|
```
|
|
59
59
|
|
|
60
60
|
The key goes on the line itself. Claude Code on the web does not pass the
|
|
@@ -70,7 +70,7 @@ If the setup script runs inside a repo that has its own package named
|
|
|
70
70
|
`harborloop`, `npx` picks that one up instead. Install it globally there:
|
|
71
71
|
|
|
72
72
|
```
|
|
73
|
-
npm i -g harborloop@
|
|
73
|
+
npm i -g harborloop@latest && HARBOR_AGENT_KEY=<your key> harbor init --headless
|
|
74
74
|
```
|
|
75
75
|
|
|
76
76
|
`init --headless` wires Claude Code with the key: the MCP entry, the hooks, the
|
|
@@ -105,7 +105,7 @@ In the Codex environment's settings, add the key as a secret named
|
|
|
105
105
|
then use this setup script:
|
|
106
106
|
|
|
107
107
|
```
|
|
108
|
-
npx -y harborloop@
|
|
108
|
+
npx -y harborloop@latest init --headless --codex --origin https://github.com/<owner>/<repo>
|
|
109
109
|
```
|
|
110
110
|
|
|
111
111
|
- **Agent internet access** must be On, with `app.gethrbr.com` and
|
|
@@ -168,9 +168,9 @@ tells you how much of what gets injected is actually used.
|
|
|
168
168
|
fails with the fix on the next line. A health check that only ever prints green
|
|
169
169
|
is not a health check.
|
|
170
170
|
|
|
171
|
-
**A partial install is one of the things it says no to.** `init` registers
|
|
172
|
-
events; a hand-edited `settings.json` that kept one of them gets
|
|
173
|
-
`Hooks ⚠ 1 of
|
|
171
|
+
**A partial install is one of the things it says no to.** `init` registers seven
|
|
172
|
+
events in Claude Code; a hand-edited `settings.json` that kept one of them gets
|
|
173
|
+
`Hooks ⚠ 1 of 7 events registered — capture, the end-of-session report and tool
|
|
174
174
|
context are not wired`, not a tick over a count. Counting what is there answers
|
|
175
175
|
a narrower question than the one you are asking it.
|
|
176
176
|
|
|
@@ -274,12 +274,12 @@ one never re-mints another:
|
|
|
274
274
|
|
|
275
275
|
```
|
|
276
276
|
~/.claude.json `mcpServers.harbor` — the MCP entry and its bearer
|
|
277
|
-
~/.claude/settings.json
|
|
277
|
+
~/.claude/settings.json seven hook events (NOT the MCP entry: Claude Code
|
|
278
278
|
reads `mcpServers` from `~/.claude.json` only)
|
|
279
|
-
~/.codex/config.toml the MCP server
|
|
280
|
-
~/.codex/hooks.json
|
|
279
|
+
~/.codex/config.toml the MCP server, plus the trust stamps Codex will not run hooks without
|
|
280
|
+
~/.codex/hooks.json six hook events (Codex has no SessionEnd)
|
|
281
281
|
~/.cursor/mcp.json `mcpServers.harbor`, Cursor's `{url, headers}` shape
|
|
282
|
-
~/.cursor/hooks.json
|
|
282
|
+
~/.cursor/hooks.json seven events, in Cursor's own event and tool names
|
|
283
283
|
```
|
|
284
284
|
|
|
285
285
|
Nothing else. Until 0.6.0 a background job wrote the team's skills, documents and
|
package/bin/checksums.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "0.6.
|
|
2
|
+
"version": "0.6.6",
|
|
3
3
|
"algorithm": "sha256",
|
|
4
4
|
"binaries": {
|
|
5
|
-
"@gethrbr/harborloop-darwin-arm64": "
|
|
6
|
-
"@gethrbr/harborloop-darwin-x64": "
|
|
7
|
-
"@gethrbr/harborloop-linux-x64": "
|
|
8
|
-
"@gethrbr/harborloop-linux-arm64": "
|
|
9
|
-
"@gethrbr/harborloop-linux-x64-musl": "
|
|
10
|
-
"@gethrbr/harborloop-win32-x64": "
|
|
5
|
+
"@gethrbr/harborloop-darwin-arm64": "2a6a397313690927a31aa52dce7d912e06d38a8da8f309bfa30be4bebb751a2b",
|
|
6
|
+
"@gethrbr/harborloop-darwin-x64": "52d1e8e629622365ce8ad6f00015601e326e0308e61133ba29c5b1ac7f5102f9",
|
|
7
|
+
"@gethrbr/harborloop-linux-x64": "61fdc3c5ec191fd8767775a29cb4915354454caff1d280c6053b6ab411727589",
|
|
8
|
+
"@gethrbr/harborloop-linux-arm64": "5944f1843d52c598a8425af777943f2fa5e524aae510dc78b0890291cacaa3f9",
|
|
9
|
+
"@gethrbr/harborloop-linux-x64-musl": "bad5790b56e61cea7d26fe2495ef0c676ce2e5164af2d0b40de68e4b74a1cff8",
|
|
10
|
+
"@gethrbr/harborloop-win32-x64": "5c96f83454873b6f232eafad18d9709910e8da2fd30b9655fd18a2387ddec12d"
|
|
11
11
|
}
|
|
12
12
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "harborloop",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.6",
|
|
4
4
|
"description": "Install and health-check the harbor knowledge loop in your terminal. Recall in Claude Code, Codex and Cursor; a doctor that can say no.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -26,12 +26,12 @@
|
|
|
26
26
|
"agents.md"
|
|
27
27
|
],
|
|
28
28
|
"optionalDependencies": {
|
|
29
|
-
"@gethrbr/harborloop-darwin-arm64": "0.6.
|
|
30
|
-
"@gethrbr/harborloop-darwin-x64": "0.6.
|
|
31
|
-
"@gethrbr/harborloop-linux-x64": "0.6.
|
|
32
|
-
"@gethrbr/harborloop-linux-arm64": "0.6.
|
|
33
|
-
"@gethrbr/harborloop-linux-x64-musl": "0.6.
|
|
34
|
-
"@gethrbr/harborloop-win32-x64": "0.6.
|
|
29
|
+
"@gethrbr/harborloop-darwin-arm64": "0.6.6",
|
|
30
|
+
"@gethrbr/harborloop-darwin-x64": "0.6.6",
|
|
31
|
+
"@gethrbr/harborloop-linux-x64": "0.6.6",
|
|
32
|
+
"@gethrbr/harborloop-linux-arm64": "0.6.6",
|
|
33
|
+
"@gethrbr/harborloop-linux-x64-musl": "0.6.6",
|
|
34
|
+
"@gethrbr/harborloop-win32-x64": "0.6.6"
|
|
35
35
|
},
|
|
36
36
|
"publishConfig": {
|
|
37
37
|
"//": "A scoped package defaults to RESTRICTED, and `npm publish` on a scope with no paid plan fails outright rather than publishing privately. This is the whole difference between a wedge anybody can `npx` and a 402.",
|