harborloop 0.5.23 → 0.6.0
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 +12 -9
- package/bin/checksums.json +7 -7
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -29,12 +29,12 @@ Then `/harbor:login` in Claude Code, or `$harbor:login` in Codex. See
|
|
|
29
29
|
| `harbor status` | This repo, from local files only. No network. |
|
|
30
30
|
| `harbor bind [project]` | Tie this repo to a project. |
|
|
31
31
|
| `harbor workspaces` | Which workspaces you can reach, and the one this machine uses. `--json` |
|
|
32
|
-
| `harbor
|
|
33
|
-
| `harbor unbind` | Take those files back off this machine. Local only — the repo stays bound, and a file you edited stays put. |
|
|
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. |
|
|
34
33
|
| `harbor off` | Pause this repo. `--capture` keeps recall. `--global` for the machine. |
|
|
35
34
|
| `harbor on` | Resume. `--global` clears a machine-wide pause. |
|
|
36
35
|
| `harbor login` | Re-authenticate. `--no-browser` to paste a code instead. `--workspace <id>` switches workspace **without** the browser. |
|
|
37
36
|
| `harbor logout` | Forget this machine's credential. Leaves the config alone. |
|
|
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
|
|
40
40
|
those over MCP and you reach them in the webapp; a second copy of the product in
|
|
@@ -72,8 +72,7 @@ the parent of the clone (`/home/user`, with the repo at `/home/user/<repo>`),
|
|
|
72
72
|
so it uses the repo it is standing in, or else every repo directly under it.
|
|
73
73
|
`--repo <path>` names one instead.
|
|
74
74
|
|
|
75
|
-
It never opens a browser
|
|
76
|
-
schedules the daemon. It prints one line and exits 0 whatever happens, so a
|
|
75
|
+
It never opens a browser and never writes `~/.harbor/auth.json`. It prints one line and exits 0 whatever happens, so a
|
|
77
76
|
Harbor problem cannot stop the session. With no `HARBOR_AGENT_KEY` it prints
|
|
78
77
|
`Harbor: no HARBOR_AGENT_KEY, skipping` and changes nothing.
|
|
79
78
|
|
|
@@ -86,7 +85,7 @@ argument. If Harbor cannot be reached, the record waits for the next turn.
|
|
|
86
85
|
fetches the workspace's guardrails again in the background, at most every 30
|
|
87
86
|
seconds, so a rule armed mid-session blocks within a minute. The tool call
|
|
88
87
|
never waits for that fetch, and it sends only the key. The same holds on a
|
|
89
|
-
laptop
|
|
88
|
+
laptop.
|
|
90
89
|
|
|
91
90
|
**A repo that commits its own hooks.** If the repo's `.claude/settings.json`
|
|
92
91
|
already runs Harbor's hooks, add `--no-hooks`. It sets up everything else and
|
|
@@ -250,7 +249,7 @@ spends two of them, so a switch that went through the browser would let you
|
|
|
250
249
|
change your mind about twice.
|
|
251
250
|
|
|
252
251
|
If the list says you are signed in to a workspace that is not on it, you were
|
|
253
|
-
removed from it. Every
|
|
252
|
+
removed from it. Every request and mint against it will fail until you switch.
|
|
254
253
|
|
|
255
254
|
## What it writes
|
|
256
255
|
|
|
@@ -259,6 +258,7 @@ removed from it. Every sync and mint against it will fail until you switch.
|
|
|
259
258
|
~/.harbor/synced-origins.json which repos are yours, and what is paused
|
|
260
259
|
~/.harbor/bin/*.mjs the hook scripts
|
|
261
260
|
~/.harbor/cli-sessions/ per-session bookkeeping
|
|
261
|
+
~/.harbor/daily-at when the hooks last started `harbor daily`
|
|
262
262
|
```
|
|
263
263
|
|
|
264
264
|
Then one entry per agent you actually have — **its own bearer, in its own file,
|
|
@@ -275,9 +275,12 @@ one never re-mints another:
|
|
|
275
275
|
~/.cursor/hooks.json five events, in Cursor's own event and tool names
|
|
276
276
|
```
|
|
277
277
|
|
|
278
|
-
|
|
279
|
-
|
|
280
|
-
your
|
|
278
|
+
Nothing else. Until 0.6.0 a background job wrote the team's skills, documents and
|
|
279
|
+
memories into `~/.claude`, `~/.codex`, `~/.cursor` and your checkouts every 15
|
|
280
|
+
minutes. That job is retired: your agent gets the same knowledge through recall.
|
|
281
|
+
The first `harbor init` or `harbor update` on 0.6.0 unloads the job and takes back
|
|
282
|
+
the files it wrote, only where the bytes still match what it wrote. A file you
|
|
283
|
+
edited stays, and the command names it.
|
|
281
284
|
|
|
282
285
|
⚠️ **Cursor recalls at session start, not on every prompt.** Its prompt event has
|
|
283
286
|
no field to inject context into, so a Cursor session gets the bundle when it
|
package/bin/checksums.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "0.
|
|
2
|
+
"version": "0.6.0",
|
|
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": "83ef9152cedb7ea4f463a6b3dcea3836b66b99bb87705b84923c7e72d77c048d",
|
|
6
|
+
"@gethrbr/harborloop-darwin-x64": "c588d54e76a06d1b81f005becf30815c36ec067e5c61802209c8de19ae7e31b9",
|
|
7
|
+
"@gethrbr/harborloop-linux-x64": "7f45a4fcb36128de743e40bda6e6b25ec3ffb836baab33842c0e5730eed11441",
|
|
8
|
+
"@gethrbr/harborloop-linux-arm64": "00afdc0d3d9ea93fd7ee77a4d838edc0e5841a450a1473bae315d6f3fbe3c9cb",
|
|
9
|
+
"@gethrbr/harborloop-linux-x64-musl": "d73ea4086575277e63d19d87fc9f55ee02a9be59ceaa511645ae3a7b9925fd46",
|
|
10
|
+
"@gethrbr/harborloop-win32-x64": "697f97aae477faf8b57c448b6cc9f2b238271c132e9c99423cdc6203146ddfd5"
|
|
11
11
|
}
|
|
12
12
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "harborloop",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.6.0",
|
|
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.
|
|
30
|
-
"@gethrbr/harborloop-darwin-x64": "0.
|
|
31
|
-
"@gethrbr/harborloop-linux-x64": "0.
|
|
32
|
-
"@gethrbr/harborloop-linux-arm64": "0.
|
|
33
|
-
"@gethrbr/harborloop-linux-x64-musl": "0.
|
|
34
|
-
"@gethrbr/harborloop-win32-x64": "0.
|
|
29
|
+
"@gethrbr/harborloop-darwin-arm64": "0.6.0",
|
|
30
|
+
"@gethrbr/harborloop-darwin-x64": "0.6.0",
|
|
31
|
+
"@gethrbr/harborloop-linux-x64": "0.6.0",
|
|
32
|
+
"@gethrbr/harborloop-linux-arm64": "0.6.0",
|
|
33
|
+
"@gethrbr/harborloop-linux-x64-musl": "0.6.0",
|
|
34
|
+
"@gethrbr/harborloop-win32-x64": "0.6.0"
|
|
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.",
|