@honcho-ai/claude-honcho 0.3.3 → 0.4.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.
Files changed (36) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/README.md +111 -335
  3. package/dist/hooks/pre-tool-honcho.js +551 -605
  4. package/dist/hooks/pre-tool-honcho.js.map +11 -9
  5. package/dist/hooks/save-user-message.js +1741 -1057
  6. package/dist/hooks/save-user-message.js.map +24 -19
  7. package/dist/hooks/session-end.js +559 -617
  8. package/dist/hooks/session-end.js.map +11 -9
  9. package/dist/hooks/session-start.js +1938 -1304
  10. package/dist/hooks/session-start.js.map +31 -22
  11. package/dist/hooks/stop.js +1785 -1157
  12. package/dist/hooks/stop.js.map +25 -19
  13. package/dist/hooks/user-prompt.js +696 -16571
  14. package/dist/hooks/user-prompt.js.map +13 -90
  15. package/dist/mcp-server.js +1689 -1676
  16. package/dist/mcp-server.js.map +23 -20
  17. package/dist/skills/backfill-runner.js +1824 -911
  18. package/dist/skills/backfill-runner.js.map +27 -20
  19. package/dist/skills/{setup-runner.js → pane-runner.js} +1910 -1020
  20. package/dist/{hooks/pre-compact.js.map → skills/pane-runner.js.map} +28 -24
  21. package/dist/skills/status-runner.js +1568 -753
  22. package/dist/skills/status-runner.js.map +23 -19
  23. package/hooks/hooks.json +10 -42
  24. package/hooks/register.tsx +574 -0
  25. package/package.json +1 -1
  26. package/skills/insights/SKILL.md +3 -7
  27. package/dist/hooks/post-tool-use.js +0 -16905
  28. package/dist/hooks/post-tool-use.js.map +0 -97
  29. package/dist/hooks/pre-compact.js +0 -17087
  30. package/dist/skills/setup-runner.js.map +0 -95
  31. package/scripts/honcho-statusline.sh +0 -101
  32. package/skills/briefing/SKILL.md +0 -20
  33. package/skills/config/SKILL.md +0 -288
  34. package/skills/import/SKILL.md +0 -73
  35. package/skills/setup/SKILL.md +0 -60
  36. package/skills/status/SKILL.md +0 -30
@@ -1,101 +0,0 @@
1
- #!/usr/bin/env bash
2
- # Renders honcho memory state as a statusLine segment with a soft truecolor
3
- # glow. The statusline is the one surface the Claude Code TUI re-paints on its
4
- # own refresh cycle, so it is where memory activity can actually animate --
5
- # hooks write ~/.honcho/state.json, this reads it. Motion is slow and
6
- # low-contrast by design (no flashing).
7
- #
8
- # At rest it shows only sync status + a clickable session link. Quantitative
9
- # detail is intentionally omitted; activity (loading/recalling/tool
10
- # calls) animates while it happens.
11
- #
12
- # Visibility via "statusline" in ~/.honcho/config.json:
13
- # "on" (default) · "off" (hidden)
14
- HONCHO_DIR="$HOME/.honcho"
15
- # Read the statusLine JSON Claude pipes in, but never block: time out fast if
16
- # stdin has no EOF, so the bar can't freeze.
17
- INPUT=""
18
- IFS= read -r -t 1 INPUT 2>/dev/null || true
19
-
20
- exec python3 - "$HONCHO_DIR" "$INPUT" <<'PY'
21
- import json, sys, time, os
22
-
23
- honcho_dir, raw = sys.argv[1], sys.argv[2]
24
-
25
- def load(name):
26
- try:
27
- return json.load(open(os.path.join(honcho_dir, name)))
28
- except Exception:
29
- return {}
30
-
31
- # session_id is the one field guaranteed identical between this statusLine
32
- # stdin and the hook stdin -> use it to read THIS window's files, with a
33
- # global-file fallback for back-compat.
34
- sess_id = ""
35
- try:
36
- sess_id = (json.loads(raw).get("session_id") or "") if raw.strip() else ""
37
- except Exception:
38
- pass
39
-
40
- def keyed(base):
41
- if sess_id and os.path.exists(os.path.join(honcho_dir, f"{base}-{sess_id}.json")):
42
- return f"{base}-{sess_id}.json"
43
- return f"{base}.json"
44
-
45
- # --- visibility toggle ------------------------------------------------------
46
- if (load("config.json").get("statusline") or "on").lower() == "off":
47
- sys.exit(0)
48
-
49
- # --- connection + session link ----------------------------------------------
50
- synced = bool((load("context-cache.json").get("userContext", {}) or {}).get("data"))
51
- link_url = (load(keyed("session")).get("url") or "")
52
-
53
- # --- live phase from the hooks ----------------------------------------------
54
- TTL = {"loading": 40, "compacting": 40, "recalling": 6, "querying": 8}
55
- phase, detail = "idle", ""
56
- s = load(keyed("state"))
57
- ph = s.get("phase", "idle")
58
- since = (s.get("since", 0) or 0) / 1000
59
- if ph in TTL and (time.time() - since) <= TTL[ph]:
60
- phase, detail = ph, (s.get("detail") or "")
61
-
62
- # --- styling: glyph animates while working, fixed colors, no flashing -------
63
- # (The statusLine is registered with refreshInterval, so Claude Code re-runs
64
- # this script on a timer even at rest. Active phases advance a slow moon-phase
65
- # frame off the wall clock; idle stays a single static marker. Only the glyph
66
- # shape rotates -- colors are constant, ~1 Hz, well under any flicker threshold.)
67
- def fg(rgb):
68
- return f"\x1b[38;2;{rgb[0]};{rgb[1]};{rgb[2]}m"
69
-
70
- R = "\x1b[0m"
71
- DIM = "\x1b[38;2;120;120;128m"
72
- CALM = (130, 200, 225) # synced / resting
73
- WORK = (230, 175, 110) # memory actively working
74
- SEP = f"{DIM} · {R}"
75
-
76
- # Slow clockwise moon rotation while working; a gentle two-frame pulse for
77
- # point queries. Frame advances ~1 Hz off the wall clock so each repaint moves.
78
- SPIN = ["◐", "◓", "◑", "◒"]
79
- SPARK = ["✦", "✧"]
80
- LABEL = {"loading": "loading memory", "compacting": "anchoring memory",
81
- "recalling": "recalling"}
82
-
83
- def osc8(url, text): # clickable link, no raw URL shown
84
- return f"\x1b]8;;{url}\x07{text}\x1b]8;;\x07"
85
-
86
- if phase == "idle":
87
- color = CALM if synced else (120, 120, 128)
88
- glyph = f"{fg(color)}{'◆' if synced else '◇'}{R}"
89
- if not link_url:
90
- out = f"{glyph}{DIM} honcho{R}"
91
- else:
92
- out = f"{glyph} {DIM}{osc8(link_url, 'honcho ↗')}{R}"
93
- else:
94
- frames = SPARK if phase == "querying" else SPIN
95
- char = frames[int(time.time()) % len(frames)]
96
- glyph = f"{fg(WORK)}{char}{R}"
97
- label = detail if phase == "querying" else LABEL.get(phase, phase)
98
- out = f"{glyph}{DIM} honcho{R}{SEP}{fg(WORK)}{label or 'memory'}{R}"
99
-
100
- sys.stdout.write(out)
101
- PY
@@ -1,20 +0,0 @@
1
- ---
2
- description: Load the Honcho session briefing (session summary + peer card) via a visible tool call
3
- user-invocable: true
4
- ---
5
-
6
- # Honcho Briefing
7
-
8
- Load the stored session summary and the user's peer card through the `get_briefing` MCP tool.
9
-
10
- ## Usage
11
-
12
- Run `/honcho:briefing` at any point to load (or reload) the briefing. The session-start directives may also ask for this automatically on the first turn when the `briefing` component is configured.
13
-
14
- ## Implementation
15
-
16
- Call the `get_briefing` tool from the honcho MCP server (`mcp__plugin_honcho_honcho__get_briefing`). No arguments.
17
-
18
- ## Presentation
19
-
20
- The payload is already visible in the expandable tool row — do NOT repeat it back. After the call, reply with at most two sentences: confirm the briefing is loaded and name where the session left off (from the summary). If the tool reports no briefing available, say so in one line.
@@ -1,288 +0,0 @@
1
- ---
2
- description: Configure Honcho memory plugin settings interactively
3
- allowed-tools: get_config, set_config
4
- user-invocable: true
5
- ---
6
-
7
- # Honcho Configuration
8
-
9
- Interactive configuration for the Honcho memory plugin. Uses AskUserQuestion for all menus and selections — never dump numbered text lists.
10
-
11
- ## Step 1: Status Header
12
-
13
- Call `get_config` to load the current state. The response includes a `card` field — a pre-rendered box-drawing card with perfect alignment.
14
-
15
- **Output the `card` value exactly as-is inside a code fence.** Do not modify it, re-render it, or add any formatting. Just wrap it in triple backticks:
16
-
17
- ````
18
- ```
19
- {card value here, verbatim}
20
- ```
21
- ````
22
- - Do NOT show cache info, config paths, or raw JSON.
23
- - Do NOT show warnings unless they indicate something is broken (skip env var shadowing warnings where the values match what's configured).
24
- - If `configExists` is false, tell the user no config exists and offer to create one.
25
-
26
- ## Step 2: Menu
27
-
28
- Present ONE question with these options (the user can select "Other" to reach advanced settings):
29
-
30
- ```
31
- AskUserQuestion:
32
- question: "What would you like to configure?"
33
- header: "Config"
34
- options:
35
- - label: "Peers"
36
- description: "Your name and AI name (currently: {resolved.peerName} / {resolved.aiPeer})"
37
- - label: "Session mapping"
38
- description: "How sessions are named — per directory, git branch, or per chat (currently: {resolved.sessionStrategy})"
39
- - label: "Workspace"
40
- description: "Data space and session scope (currently: {resolved.workspace})"
41
- - label: "Memory injection"
42
- description: "What Honcho injects at session start and per turn (currently: start [{resolved.injection.sessionStart}], turn [{resolved.injection.perTurn}], shown in UI [{resolved.injection.showContents}])"
43
- ```
44
-
45
- For the "Memory injection" description, use the *effective* values: if `injection.sessionStart` is unset it is `["directives", "summary", "peerCard"]`, and if `injection.perTurn` is unset it is `["userContext"]` (user conclusions on). A stored perTurn value of `"context"` is the legacy name for `"userContext"` — treat them as the same. `injection.showContents` is `[]` when unset — render that as `none`.
46
-
47
- If the user selects "Other", present advanced options:
48
-
49
- ```
50
- AskUserQuestion:
51
- question: "Advanced settings:"
52
- header: "Advanced"
53
- options:
54
- - label: "Host"
55
- description: "Platform / local / custom URL (currently: {current.host})"
56
- - label: "Context refresh"
57
- description: "TTL, message threshold, dialectic settings"
58
- - label: "Message upload"
59
- description: "Token limits, summarization settings"
60
- - label: "Statusline"
61
- description: "Memory statusLine visibility — on / off (currently: {resolved.statusline})"
62
- ```
63
-
64
- Always include current values in the description so the user can see what's set.
65
-
66
- ## Step 3: Handle Selection
67
-
68
- ### Peers
69
-
70
- When selected, use `AskUserQuestion` to ask which peer to change:
71
-
72
- ```
73
- AskUserQuestion:
74
- question: "Which peer to change?"
75
- header: "Peers"
76
- options:
77
- - label: "Your name"
78
- description: "Currently: {resolved.peerName}"
79
- - label: "AI name"
80
- description: "Currently: {resolved.aiPeer}"
81
- ```
82
-
83
- Then ask for the new value. Call `set_config` with `peerName` or `aiPeer`.
84
-
85
- ### Simple fields (Logging, etc.)
86
-
87
- Use `AskUserQuestion` to ask for the new value if there are known options, otherwise ask the user to type it. Call `set_config` with the appropriate field. Show the result.
88
-
89
- ### Session mapping
90
-
91
- ```
92
- AskUserQuestion:
93
- question: "Which session mapping strategy?"
94
- header: "Sessions"
95
- options:
96
- - label: "per-directory (Recommended)"
97
- description: "{peer}-{repo} — one session per project"
98
- - label: "git-branch"
99
- description: "{peer}-{repo}-{branch} — session follows branch"
100
- - label: "chat-instance"
101
- description: "chat-{id} — fresh each launch"
102
- ```
103
-
104
- Do NOT use markdown previews for this menu — descriptions are sufficient and previews truncate in narrow terminals.
105
-
106
- After strategy selection, ask about peer prefix:
107
-
108
- ```
109
- AskUserQuestion:
110
- question: "Include your name in session names?"
111
- header: "Prefix"
112
- options:
113
- - label: "Yes — {peerName}-{repoName}"
114
- description: "For teams sharing a workspace"
115
- - label: "No — {repoName} only"
116
- description: "Cleaner for solo use"
117
- ```
118
-
119
- ### Workspace
120
-
121
- When selected, present a sub-menu:
122
-
123
- ```
124
- AskUserQuestion:
125
- question: "Workspace settings?"
126
- header: "Workspace"
127
- options:
128
- - label: "Rename workspace"
129
- description: "Change workspace name (currently: {resolved.workspace})"
130
- ```
131
-
132
- #### Workspace > Rename
133
-
134
- Dangerous field — requires confirmation. First call `set_config` WITHOUT `confirm: true`. The tool will return a description of what will happen. Use `AskUserQuestion` to confirm:
135
-
136
- ```
137
- AskUserQuestion:
138
- question: "Switch workspace to '{value}'?"
139
- header: "Confirm"
140
- options:
141
- - label: "Yes, switch"
142
- description: "Change to the new workspace"
143
- - label: "Cancel"
144
- description: "Keep current workspace"
145
- ```
146
-
147
- If confirmed, call `set_config` again WITH `confirm: true`.
148
-
149
- ### Memory injection
150
-
151
- Ask all three questions in a SINGLE `AskUserQuestion` call — multi-select each — so the user configures every surface at once. Always include all three, each offering all of its options: the "Show in UI" answers arrive in the same response as "Per turn", so there is no way to narrow them to what the user just enabled. A "Show in UI" pick for a component that is off is harmless — it's stored and takes effect if that component is enabled later. This is the only injection prompt; do not add follow-ups.
152
-
153
- ```yaml
154
- AskUserQuestion:
155
- questions:
156
- - question: "What should Honcho inject at the start of each session?"
157
- header: "On start" # ≤12 chars
158
- multiSelect: true
159
- options:
160
- - label: "Memory directives"
161
- description: "How to use memory — treat as background, search, save insights"
162
- - label: "Session summary"
163
- description: "Rolling long summary of prior sessions"
164
- - label: "Peer card"
165
- description: "Your identity + attributes list"
166
- - label: "Representation"
167
- description: "Honcho's derived prose profile of you"
168
- - question: "What should Honcho inject on each user turn?"
169
- header: "Per turn"
170
- multiSelect: true
171
- options:
172
- - label: "User conclusions"
173
- description: "Fresh, prompt-scoped memory about you pulled every turn"
174
- - label: "Assistant conclusions"
175
- description: "Same fetch, but for the AI peer — what Honcho knows about the assistant"
176
- - label: "Session messages"
177
- description: "Recent raw messages from the mapped Honcho session — useful when other instances share the session"
178
- - label: "Dialectic recall"
179
- description: "A reasoned answer over your history each turn — richer but slower (off by default)"
180
- - question: "Which of those should print what they injected to the terminal?"
181
- header: "Show in UI"
182
- multiSelect: true
183
- options: # same four labels as "Per turn"
184
- - label: "User conclusions"
185
- description: "List each injected conclusion instead of just the count"
186
- - label: "Assistant conclusions"
187
- description: "List each injected conclusion instead of just the count"
188
- - label: "Session messages"
189
- description: "List each injected message, one truncated line each"
190
- - label: "Dialectic recall"
191
- description: "Print the full reasoned answer — prose, can be long"
192
- ```
193
-
194
- Map the selections to component names, then call `set_config` once per field:
195
- - Session start → `injection.sessionStart`, mapping "Memory directives"→`directives`, "Session summary"→`summary`, "Peer card"→`peerCard`, "Representation"→`peerRepresentation`.
196
- - Per turn → `injection.perTurn`, mapping "User conclusions"→`userContext`, "Assistant conclusions"→`assistantContext`, "Session messages"→`sessionContext`, "Dialectic recall"→`dialectic`.
197
- - Show in UI → `injection.showContents`, same mapping as per turn.
198
-
199
- Pass the value as a JSON array (e.g. `["directives","summary","peerCard"]`). An empty selection means `[]`: for `injection.sessionStart` and `injection.perTurn` that surface then injects nothing, and for `injection.showContents` (the default) every enabled per-turn component still injects — it just reports a one-line summary (count, tokens, timing) instead of printing its payload.
200
-
201
- `showContents` is display-only. It never changes what reaches the model.
202
-
203
- Retrieval tuning is intentionally NOT asked here. `injection.searchTopK` (default 10), `injection.maxConclusions` (15), `injection.searchMaxDistance` (0.6, cosine — lower is stricter), and `injection.searchQuerySource` ("prompt" | "topics", default "prompt") are all configurable via `set_config`, but keep the defaults; only mention they're tunable if the user brings it up, and never prompt for them.
204
-
205
- If the user enables "Dialectic recall", note the two knobs that shape it — `injection.dialecticTemplate` (the query, with a `%{user_query}` placeholder) and `injection.dialecticReasoning` (tier, default "low") — both via `set_config`. Flag the trade-off: it fires a `chat()` call every non-trivial turn (~12s at medium), on its own budget under the 30s hook ceiling, so it adds real per-turn latency. Keep it off unless the user wants it.
206
-
207
- ### Dangerous fields (Host)
208
-
209
- Host changes require confirmation. First call `set_config` WITHOUT `confirm: true`. The tool will return a description of what will happen. Use `AskUserQuestion` to confirm, then call again WITH `confirm: true`.
210
-
211
- ### Context refresh
212
-
213
- Use `AskUserQuestion` to pick which setting to change:
214
-
215
- ```
216
- AskUserQuestion:
217
- question: "Which context refresh setting?"
218
- header: "Refresh"
219
- options:
220
- - label: "TTL"
221
- description: "Cache lifetime — currently {contextRefresh.ttlSeconds}s (default: 300)"
222
- - label: "Message threshold"
223
- description: "Refresh every N messages — currently {contextRefresh.messageThreshold} (default: 30)"
224
- - label: "Skip dialectic"
225
- description: "Skip chat() in prompt hook — currently {contextRefresh.skipDialectic} (default: false)"
226
- ```
227
-
228
- Then ask for the new value and call `set_config`.
229
-
230
- ### Statusline
231
-
232
- ```
233
- AskUserQuestion:
234
- question: "Memory statusLine visibility?"
235
- header: "Statusline"
236
- options:
237
- - label: "on (Recommended)"
238
- description: "Sync status, clickable session link, and live activity"
239
- - label: "off"
240
- description: "Hidden"
241
- ```
242
-
243
- Call `set_config` with field `statusline` and the chosen value. Takes effect on the next statusLine repaint.
244
-
245
- ### Message upload
246
-
247
- Use `AskUserQuestion` to pick which setting to change:
248
-
249
- ```
250
- AskUserQuestion:
251
- question: "Which message upload setting?"
252
- header: "Upload"
253
- options:
254
- - label: "Max user tokens"
255
- description: "Truncate user messages — currently {messageUpload.maxUserTokens || 'no limit'}"
256
- - label: "Max assistant tokens"
257
- description: "Truncate assistant messages — currently {messageUpload.maxAssistantTokens || 'no limit'}"
258
- - label: "Summarize assistant"
259
- description: "Use summary instead of full text — currently {messageUpload.summarizeAssistant}"
260
- ```
261
-
262
- Then ask for the new value and call `set_config`.
263
-
264
- ## Step 4: Loop
265
-
266
- After handling a selection, call `get_config` again to refresh state. Use `AskUserQuestion` to ask if they want to configure more:
267
-
268
- ```
269
- AskUserQuestion:
270
- question: "Configuration updated. What next?"
271
- header: "Next"
272
- options:
273
- - label: "Configure more"
274
- description: "Return to settings menu"
275
- - label: "Done"
276
- description: "Exit configuration"
277
- ```
278
-
279
- If "Configure more", go back to Step 2. If "Done", show the final status header and exit.
280
-
281
- ## Guardrails
282
-
283
- - ALWAYS use AskUserQuestion for menus and confirmations. Never present numbered text lists.
284
- - Always show the result of `set_config` including any cache invalidation that occurred.
285
- - If a warning about env var shadowing is returned, explain that the env var takes precedence at runtime.
286
- - Never guess values — always ask the user.
287
- - Include current values in option descriptions so the user sees what's set without expanding anything.
288
- - If `get_config` returns `configExists: false`, guide the user to set HONCHO_API_KEY first.
@@ -1,73 +0,0 @@
1
- ---
2
- description: Import past local Claude Code sessions into Honcho memory (backfill history)
3
- user-invocable: true
4
- ---
5
-
6
- # Honcho Import
7
-
8
- Backfill the user's existing local Claude Code session transcripts into Honcho so
9
- past work becomes apart of Honcho's memory. It uploads real conversation content, so it
10
- always previews first and requires explicit confirmation.
11
-
12
- Transcripts live at `~/.claude/projects/<cwd-as-dashes>/<session-uuid>.jsonl`. The
13
- importer reconstructs each conversation, names sessions using the user's configured
14
- `sessionStrategy`, and uploads with the original message timestamps into the user's
15
- configured workspace.
16
-
17
- ## Prerequisite
18
-
19
- Honcho must already be configured (`HONCHO_API_KEY` set or `~/.honcho/config.json`
20
- present). If not, tell the user to run `/honcho:setup` first and stop here.
21
-
22
- ## Optional arguments
23
-
24
- The user may specify scope in natural language; translate it to flags:
25
- - window → `--days N` (default 30)
26
- - a specific workspace → `--workspace NAME` (default: their configured workspace)
27
-
28
- ## Steps
29
-
30
- ### 1. Preview (safe — no upload)
31
-
32
- Run the importer in dry-run mode and show the user the plan:
33
-
34
- ```bash
35
- node "${CLAUDE_PLUGIN_ROOT}/dist/skills/backfill-runner.js" --dry-run
36
- ```
37
-
38
- If `CLAUDE_PLUGIN_ROOT` isn't set, the plugin lives here (find the version
39
- directory inside and run the importer from there):
40
-
41
- ```bash
42
- echo "$HOME/.claude/plugins/cache/honcho/honcho"
43
- ```
44
-
45
- Report the workspace, session count, and message count. Note that any sessions
46
- already imported are skipped automatically (the importer is idempotent).
47
-
48
- ### 2. Confirm
49
-
50
- Ask the user to confirm before uploading. **Do not upload without an explicit yes**
51
- — this sends real conversation content to Honcho.
52
-
53
- ### 3. Import
54
-
55
- On confirmation, run the real import (add `--days`/`--workspace` if the user asked):
56
-
57
- ```bash
58
- node "${CLAUDE_PLUGIN_ROOT}/dist/skills/backfill-runner.js" --yes
59
- ```
60
-
61
- ### 4. Report
62
-
63
- Tell the user, honestly and without first-run/restart framing:
64
-
65
- > Imported <N> message(s) across <M> session(s) into `<workspace>`. Honcho will
66
- > start reasoning over them (no restart needed).
67
-
68
- Notes to relay if relevant:
69
- - Idempotent: already-imported transcripts are recorded in
70
- `~/.honcho/backfill-state.json` and skipped on re-run, so it's safe to run again
71
- (e.g. with a wider `--days` window) to pull in more history later.
72
- - Sessions are named by the configured `sessionStrategy`, so imported history lines
73
- up with future live sessions.
@@ -1,60 +0,0 @@
1
- ---
2
- description: First-time Honcho configuration -- set API key, validate connection, create config
3
- user-invocable: true
4
- ---
5
-
6
- # Honcho Setup
7
-
8
- Walk the user through first-time Honcho configuration so persistent memory works in Claude Code.
9
-
10
- ## Steps
11
-
12
- ### 1. Validate the connection
13
-
14
- Run the setup runner. It's a committed script (`src/skills/setup-runner.ts`) that
15
- checks for an API key (env var, then `~/.honcho/config.json`), validates the
16
- connection, writes the config, and installs the memory statusLine:
17
-
18
- ```bash
19
- node "${CLAUDE_PLUGIN_ROOT}/dist/skills/setup-runner.js"
20
- ```
21
-
22
- If `CLAUDE_PLUGIN_ROOT` isn't set, the plugin lives here (find the version
23
- directory inside and run the runner from there):
24
-
25
- ```bash
26
- echo "$HOME/.claude/plugins/cache/honcho/honcho"
27
- ```
28
-
29
- **If the runner reports "No API key found"**, it prints how to set one and exits.
30
- Relay that to the user:
31
-
32
- - Get a free key at https://app.honcho.dev
33
- - **macOS / Linux:** add to `~/.zshrc` (or `~/.bashrc`): `export HONCHO_API_KEY="your-key-here"`
34
- - **Windows (PowerShell):** `setx HONCHO_API_KEY "your-key-here"`
35
- - Then restart Claude Code and run `/honcho:setup` again.
36
-
37
- Do NOT ask the user to paste their key into the chat — it must be set as an
38
- environment variable outside Claude Code. Stop here and wait for them to come back.
39
-
40
- **If the runner succeeds**, the key is valid and the config file has been created.
41
- The statusLine renderer is copied to `~/.honcho/honcho-statusline.sh` and registered
42
- in `~/.claude/settings.json` (only when no `statusLine` is already configured — an
43
- existing one is left untouched and the path is printed for manual use). Toggle
44
- visibility later with the `statusline` key in `~/.honcho/config.json`: `on`
45
- (default) or `off`.
46
-
47
- If it fails for another reason:
48
- - Authentication error: key may be invalid — get a new one at https://app.honcho.dev
49
- - Network error: check the internet connection
50
-
51
- ### 2. Confirm setup
52
-
53
- Tell the user that Honcho is configured and memory will be active on their next session. Suggest they restart Claude Code to see the memory context load.
54
-
55
- If the setup runner (step 1) reported that past local sessions are available to
56
- import, mention it as an optional next step — do **not** import here. Point them to
57
- the dedicated command:
58
-
59
- > You also have past Claude Code sessions that can be imported into Honcho.
60
- > Run `/honcho:import` whenever you'd like to backfill them.
@@ -1,30 +0,0 @@
1
- ---
2
- description: Show current Honcho memory status and configuration
3
- user-invocable: true
4
- ---
5
-
6
- # Honcho Status
7
-
8
- Display the current Honcho memory system status: connection health, workspace, peers, observation queue, and conclusion count.
9
-
10
- ## What It Shows
11
-
12
- 1. **Connection** - Live connection health and latency
13
- 2. **Workspace** - Current workspace and endpoint URL
14
- 3. **Peers** - User peer and AI peer names
15
- 4. **Observing** - Queue processing status (messages observed, active, sessions)
16
- 5. **Conclusions** - Total conclusion/memory count for the user peer
17
-
18
- ## Usage
19
-
20
- Run `/honcho:status` to see the current state of the Honcho memory system.
21
-
22
- ## Presentation
23
-
24
- After running the script, present a concise status card echoing the runner output. Do NOT add prose commentary — the output speaks for itself. Only add a one-line note if something looks wrong (e.g. auth failed, unreachable, 0 conclusions).
25
-
26
- ## Implementation
27
-
28
- ```bash
29
- node ${CLAUDE_PLUGIN_ROOT}/dist/skills/status-runner.js
30
- ```