@vectorize-io/hindsight-coding-agents 0.5.1 → 0.5.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.
- package/README.md +84 -9
- package/dist/antigravity-hook.js +424 -81
- package/dist/antigravity-statusline.js +56 -11
- package/dist/antigravity-stop-hook.js +515 -134
- package/dist/claude-hook.js +424 -81
- package/dist/claude-sessionstart-hook.js +392 -98
- package/dist/claude-stop-hook.js +515 -134
- package/dist/cline.js +218 -73
- package/dist/codex-hook.js +424 -81
- package/dist/codex-sessionstart-hook.js +392 -98
- package/dist/codex-stop-hook.js +515 -134
- package/dist/copilot-hook.js +424 -81
- package/dist/copilot-sessionstart-hook.js +392 -98
- package/dist/copilot-stop-hook.js +515 -134
- package/dist/cursor-hook.js +424 -81
- package/dist/cursor-sessionstart-hook.js +392 -98
- package/dist/cursor-stop-hook.js +515 -134
- package/dist/daemon-start.js +50 -9
- package/dist/dcode-hook.js +424 -81
- package/dist/dcode-sessionstart-hook.js +392 -98
- package/dist/dcode-stop-hook.js +515 -134
- package/dist/deepen.js +164 -27
- package/dist/devin-hook.js +424 -81
- package/dist/devin-sessionstart-hook.js +392 -98
- package/dist/devin-stop-hook.js +515 -134
- package/dist/droid-hook.js +2920 -0
- package/dist/droid-sessionstart-hook.js +3487 -0
- package/dist/droid-stop-hook.js +3188 -0
- package/dist/dsh.js +260 -109
- package/dist/grok-hook.js +424 -81
- package/dist/grok-sessionstart-hook.js +392 -98
- package/dist/grok-stop-hook.js +515 -134
- package/dist/hindsight-seed.js +56 -11
- package/dist/index.js +257 -110
- package/dist/installer.js +530 -223
- package/dist/kilo.js +257 -110
- package/dist/mcp-server.js +537 -146
- package/dist/opencode2.js +257 -110
- package/dist/pi.js +256 -109
- package/dist/prime-agent.js +256 -109
- package/dist/qwen-hook.js +424 -81
- package/dist/qwen-sessionstart-hook.js +392 -98
- package/dist/qwen-stop-hook.js +515 -134
- package/dist/status.js +128 -20
- package/dist/zcode-hook.js +2920 -0
- package/dist/zcode-sessionstart-hook.js +3487 -0
- package/dist/zcode-stop-hook.js +3188 -0
- package/package.json +11 -5
- package/plugin.json +1 -1
- package/skill/SKILL.md +42 -8
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vectorize-io/hindsight-coding-agents",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.3",
|
|
4
4
|
"repository": {
|
|
5
5
|
"type": "git",
|
|
6
6
|
"url": "https://github.com/vectorize-io/hindsight.git",
|
|
@@ -31,7 +31,13 @@
|
|
|
31
31
|
"hindsight-devin-hook": "dist/devin-hook.js",
|
|
32
32
|
"hindsight-qwen-hook": "dist/qwen-hook.js",
|
|
33
33
|
"hindsight-qwen-sessionstart-hook": "dist/qwen-sessionstart-hook.js",
|
|
34
|
-
"hindsight-qwen-stop-hook": "dist/qwen-stop-hook.js"
|
|
34
|
+
"hindsight-qwen-stop-hook": "dist/qwen-stop-hook.js",
|
|
35
|
+
"hindsight-zcode-hook": "dist/zcode-hook.js",
|
|
36
|
+
"hindsight-zcode-sessionstart-hook": "dist/zcode-sessionstart-hook.js",
|
|
37
|
+
"hindsight-zcode-stop-hook": "dist/zcode-stop-hook.js",
|
|
38
|
+
"hindsight-droid-hook": "dist/droid-hook.js",
|
|
39
|
+
"hindsight-droid-sessionstart-hook": "dist/droid-sessionstart-hook.js",
|
|
40
|
+
"hindsight-droid-stop-hook": "dist/droid-stop-hook.js"
|
|
35
41
|
},
|
|
36
42
|
"exports": {
|
|
37
43
|
".": {
|
|
@@ -90,12 +96,12 @@
|
|
|
90
96
|
"@types/node": "^26.1.0",
|
|
91
97
|
"tsup": "^8.3.0",
|
|
92
98
|
"typescript": "^5.6.0",
|
|
93
|
-
"vitest": "^
|
|
99
|
+
"vitest": "^4.1.11"
|
|
94
100
|
},
|
|
95
101
|
"overrides": {
|
|
96
102
|
"esbuild": ">=0.25.0 <1.0.0",
|
|
97
|
-
"fast-uri": ">=3.1.
|
|
98
|
-
"hono": ">=4.
|
|
103
|
+
"fast-uri": ">=3.1.6 <4.0.0",
|
|
104
|
+
"hono": ">=4.13.5 <5.0.0",
|
|
99
105
|
"ip-address": ">=10.3.1 <11.0.0",
|
|
100
106
|
"postcss": ">=8.5.23 <9.0.0",
|
|
101
107
|
"vite": ">=6.4.3 <7.0.0"
|
package/plugin.json
CHANGED
package/skill/SKILL.md
CHANGED
|
@@ -209,15 +209,15 @@ hook by Codex...), so one shared config serves several agents side by side:
|
|
|
209
209
|
| `reflectBudget` | `"high"` | reflect budget for the `hindsight_reflect` tool: `"low"`, `"mid"` or `"high"`. Drop it on a large bank where high-budget synthesis exceeds the server's wall timeout. The automatic session-start reflect always uses `"low"` to fit its hook window and is unaffected |
|
|
210
210
|
| `autoReflect` | `true` | inject a one-time reflect synthesis on the session's **first prompt**. `false` = tool-only reflect: nothing is injected; the agent searches knowledge pages first and reflects only when they are too shallow |
|
|
211
211
|
| `pageRefreshEveryTurns` | `10` | refetch the knowledge pages and re-inject the page roster + tool guide every N user turns |
|
|
212
|
-
| `pageTriggerType` | `"
|
|
213
|
-
| `pageTriggerCron` |
|
|
212
|
+
| `pageTriggerType` | `"cron"` | when NEW knowledge pages refresh, i.e. what keeping them current costs — `"cron"` (default) on `pageTriggerCron` only and only when actually stale, `"auto-refresh"` after every consolidation that produced new material, `"manual"` never on their own. Auto-refresh is the most current and by far the most expensive: one synthesis per page per consolidation. Maps to the page's `trigger.refresh_cron`, or `trigger.refresh_after_consolidation` in the Hindsight API (`true` for auto-refresh, `false` for manual) |
|
|
213
|
+
| `pageTriggerCron` | `"H * * * *"` | schedule for `pageTriggerType: "cron"` — UTC, standard 5-field cron, e.g. `"0 3 * * *"`. The default is hourly, each page on its own hashed minute. Sets the page's `trigger.refresh_cron`, which the API treats as mutually exclusive with `refresh_after_consolidation`; a scheduled refresh is skipped when nothing changed. Write a field as `H` to give each page its own value there — see **Spreading refreshes with `H`** below |
|
|
214
214
|
| `autoSeed` | `true` | SessionStart: auto-seed a cold repo's bank from git history |
|
|
215
215
|
| `seedLimit` | `300` | auto-seed: most-recent-N-commits cap |
|
|
216
216
|
| `codebaseSurvey` | `true` | SessionStart: headless survey of a cold repo's structure, run under the current harness's own CLI (claude/codex/antigravity/opencode), falling back to any available agent |
|
|
217
217
|
| `surveyModel` | `haiku` | model for the survey — Claude recipe only (`claude -p --model`); other agents use their configured default |
|
|
218
218
|
| `surveyBudgetUsd` | `2` | survey spend cap — Claude recipe only (`claude -p --max-budget-usd`); other agents rely on their read-only sandbox |
|
|
219
219
|
| `surveyRefreshCommits` | `20` | re-run the survey at SessionStart once this many commits have accrued since the last one, so the structural pages track an architecture that keeps moving (`0` = survey a cold repo only, never again) |
|
|
220
|
-
| `retainSessions` | `true` | session write-back, honored by every harness: hook harnesses write the transcript on Stop, plugin harnesses (opencode, opencode 2, Kilo) upsert it every turn plus an idle flush that captures the reply the per-turn pass can't see. Set `false`
|
|
220
|
+
| `retainSessions` | `true` | session write-back, honored by every harness: hook harnesses write the transcript on Stop, Factory Droid also writes on its cancellation notification, and plugin harnesses (opencode, opencode 2, Kilo) upsert it every turn plus an idle flush that captures the reply the per-turn pass can't see. Set `false` - globally, per harness, or per bank - to stop writing transcripts (the background history import stops with it) while recall, git ingest and the memory tools keep working |
|
|
221
221
|
| `maxParallelRetains` | `10` | cap on concurrent retain-related requests: drain()'s per-op polls plus deepen's chat/git retain pools. The API rate-limits bursts, not single requests — if you see 429s, lower this rather than raising it |
|
|
222
222
|
| `logLevel` | `"info"` | plugin-log verbosity (`"debug"` \| `"info"` \| `"warn"` \| `"error"`); `HINDSIGHT_LOG_LEVEL` env overrides |
|
|
223
223
|
| `autoUpdate` | `true` | keep the installed runtime current by itself: once a day a session start asks npm for the published version and, when it is newer, re-stages `~/.hindsight/coding-agents` in the background. It rewires no host config, so a release adding a **new** hook entry point still needs a manual `install`. Set `false` to pin the installed version; `disabled` stops it too, since an inert plugin should stay inert. Only ever replaces a runtime installed the documented way, via `npx` — a copy installed with `npm i -g`, vendored as a project dependency, or built from a checkout is left to whoever manages it (update those the way you installed them), and it needs `npx` on `PATH` |
|
|
@@ -225,16 +225,50 @@ hook by Codex...), so one shared config serves several agents side by side:
|
|
|
225
225
|
| `harnesses.<name>` | — | per-harness override of any field above |
|
|
226
226
|
| `harness` | `opencode` | **deepen engine only**: which session format `--conversations` is read as |
|
|
227
227
|
|
|
228
|
+
By default a page refreshes **hourly, staggered**: `pageTriggerCron` is `"H * * * *"`, so every
|
|
229
|
+
page gets its own minute of the hour (see below) and a tick with nothing new to fold in is skipped
|
|
230
|
+
server-side. That keeps pages within an hour of the repo without paying auto-refresh's price — one
|
|
231
|
+
LLM synthesis per page per consolidation, on a repo that consolidates all day. Set
|
|
232
|
+
`pageTriggerType: "auto-refresh"` to go back to refreshing on every consolidation.
|
|
233
|
+
|
|
228
234
|
`pageTriggerType`/`pageTriggerCron` decide only **when** a page refreshes. **How** it refreshes
|
|
229
235
|
belongs to the server: Hindsight creates a knowledge page with a delta refresh (each pass edits the
|
|
230
236
|
page instead of rebuilding it) that doesn't reflect over sibling pages, and these settings merge
|
|
231
237
|
over those defaults rather than replacing them.
|
|
232
238
|
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
`
|
|
236
|
-
|
|
237
|
-
|
|
239
|
+
### Spreading refreshes with `H`
|
|
240
|
+
|
|
241
|
+
One `pageTriggerCron` is shared by every page in every repo you point this plugin at. So a literal
|
|
242
|
+
`"0 3 * * *"` does not schedule _a_ refresh at 03:00 — it schedules **all** of them at 03:00, five
|
|
243
|
+
pages per bank, on the same worker pool that serves retain. A session ingesting at 03:0x queues
|
|
244
|
+
behind the pile, and moving the hour just moves the pile.
|
|
245
|
+
|
|
246
|
+
Write a field as `H` and it is replaced, per page, by a value hashed from the bank id and the page
|
|
247
|
+
name. Each page gets its own slot, the same slot on every run:
|
|
248
|
+
|
|
249
|
+
| `pageTriggerCron` | what each page gets |
|
|
250
|
+
| ------------------ | ------------------------------------------------------ |
|
|
251
|
+
| `"H H * * *"` | once a day, at its own minute and hour |
|
|
252
|
+
| `"H * * * *"` | once an hour, at its own minute |
|
|
253
|
+
| `"H 3 * * *"` | daily at 03:MM — spread inside the hour you chose |
|
|
254
|
+
| `"H H(0-5) * * *"` | daily, spread across 00:00–05:59 only |
|
|
255
|
+
| `"0 3 * * *"` | no `H`, no hashing — exactly what it says, all at once |
|
|
256
|
+
|
|
257
|
+
`H` is [Jenkins' syntax](https://www.jenkins.io/doc/book/pipeline/syntax/#cron-syntax) for the same
|
|
258
|
+
problem. It never reaches the API: the plugin resolves it to an ordinary cron expression
|
|
259
|
+
(`"41 17 * * *"`) when it creates the page, so the schedule you see in the control plane is a plain
|
|
260
|
+
one you can edit. Hashing spreads pages out, it does not partition them — two pages can still land
|
|
261
|
+
on the same minute, just not all of them.
|
|
262
|
+
|
|
263
|
+
**These settings apply to the pages a repo already has, too.** Every session compares each page
|
|
264
|
+
this plugin created — the seeded taxonomy and every captured initiative — against the config and
|
|
265
|
+
re-syncs the ones that differ, so a bank seeded before this default changed moves onto the hourly
|
|
266
|
+
schedule by itself, and a page you retriggered by hand in the control plane is put back on the
|
|
267
|
+
configured policy the next time an agent runs. The config
|
|
268
|
+
file is the source of truth for these pages: to give one a different schedule, change
|
|
269
|
+
`pageTriggerType`/`pageTriggerCron` (per bank, if it is only that repo) rather than editing the
|
|
270
|
+
page. Only the fields this plugin states are touched — a page's `mode`, its excluded siblings and
|
|
271
|
+
its minimum refresh interval are left exactly as they are.
|
|
238
272
|
|
|
239
273
|
### A bank you shape yourself — `manageBankConfig`
|
|
240
274
|
|