genaicode 2.46.0 → 2.47.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 (44) hide show
  1. package/dist/agents/session.d.ts +6 -0
  2. package/dist/agents/session.js +15 -0
  3. package/dist/agents/session.js.map +1 -1
  4. package/dist/agents/sessions/codex.d.ts +11 -0
  5. package/dist/agents/sessions/codex.js +42 -2
  6. package/dist/agents/sessions/codex.js.map +1 -1
  7. package/dist/agents/sessions/group.d.ts +4 -0
  8. package/dist/agents/sessions/group.js +8 -0
  9. package/dist/agents/sessions/group.js.map +1 -1
  10. package/dist/agents/sessions/hooks.d.ts +5 -0
  11. package/dist/agents/sessions/hooks.js +11 -2
  12. package/dist/agents/sessions/hooks.js.map +1 -1
  13. package/dist/agents/sessions/index.d.ts +6 -3
  14. package/dist/agents/sessions/index.js +3 -2
  15. package/dist/agents/sessions/index.js.map +1 -1
  16. package/dist/agents/sessions/send-tool.d.ts +50 -0
  17. package/dist/agents/sessions/send-tool.js +114 -0
  18. package/dist/agents/sessions/send-tool.js.map +1 -0
  19. package/dist/agents/sessions/send.d.ts +2 -0
  20. package/dist/agents/sessions/send.js +1 -1
  21. package/dist/agents/sessions/send.js.map +1 -1
  22. package/dist/agents/sessions/stores.js +6 -0
  23. package/dist/agents/sessions/stores.js.map +1 -1
  24. package/dist/agents/sessions/topics.d.ts +22 -5
  25. package/dist/agents/sessions/topics.js +53 -9
  26. package/dist/agents/sessions/topics.js.map +1 -1
  27. package/dist/agents.d.ts +2 -2
  28. package/dist/agents.js +1 -1
  29. package/dist/agents.js.map +1 -1
  30. package/dist/cli/args.d.ts +2 -0
  31. package/dist/cli/args.js +2 -0
  32. package/dist/cli/args.js.map +1 -1
  33. package/dist/cli/main.d.ts +1 -1
  34. package/dist/cli/main.js +93 -15
  35. package/dist/cli/main.js.map +1 -1
  36. package/dist/ui/index.js +103 -100
  37. package/dist/ui/sessions.d.ts +17 -0
  38. package/dist/ui/sessions.js +30 -1
  39. package/dist/ui/sessions.js.map +1 -1
  40. package/dist/ui/web-client.js +17 -17
  41. package/docs/CHANGELOG.md +19 -0
  42. package/docs/agents.md +18 -2
  43. package/docs/cli.md +26 -9
  44. package/package.json +1 -1
package/docs/CHANGELOG.md CHANGED
@@ -8,6 +8,25 @@ fails. Merging to master refreshes the `release` PR; merging that publishes to n
8
8
 
9
9
  ## Unreleased
10
10
 
11
+ ## 2.47.0 — 2026-11-21
12
+
13
+ ### Added
14
+
15
+ - `sessions_send` in `chat --sessions` and `ui --sessions` (the desktop app): ask the agent to tell another session something and it sends it there; the first message to each session waits for your approval in the chat, and the chat shows the answer (#253)
16
+ - `genaicode sessions send` refuses in a shell that a coding agent runs, so prompts to other sessions come from a person; `--force` sends anyway (#247)
17
+ - The desktop app starts its chat with the session tools (`ui --sessions`), so the agent answers what goes on in a project from the session index (#251)
18
+ - `genaicode ui` and the desktop app fold a turn's tool calls into one "N steps" line that opens on click; the answer, errors and open approvals stay in view (#251)
19
+ - The browser's Sessions view groups sessions by topic once `genaicode topics refresh` has sorted them (those that ask for you first; **By directory** brings projects back), and the header shows the chosen agent's plan limits as `genaicode limits` last saw them, without a price when a plan limit is known (#251)
20
+ - `genaicode sessions --waiting --json --watch` carries the topics: each session the name of its `topic`, and the line `topics` (name, sessions, asking, active). The desktop app's menu names a waiting session by its topic and lists the topics agents work on now (#250)
21
+ - `genaicode topics refresh` puts the sessions that worked in a directory of a Codex desktop app project in a topic named as that project, whichever agent they were in (`codexProjects()`, `folderTopics()`), after the claude.ai projects and before any agent is asked; the agent is told to keep topics few and broad (#248)
22
+
23
+ ### Fixed
24
+
25
+ - `sessions --waiting --json --watch` (the desktop app's menu bar) lists only the sessions that ask now, not every session whose turn ended; `hooks status` says `broken` when the Node its hook was installed with is gone (#252)
26
+ - `genaicode hooks install` gives Codex's `SessionEnd` hook the three seconds Codex allows, so Codex no longer warns about it in every session (#251)
27
+ - `genaicode topics` lists topics without their directories, and with names up to 48 characters (#248)
28
+ - Threads the Codex desktop app's server ran for another program, and Muse Code's probes and test-provider sessions, count as automated (#248)
29
+
11
30
  ## 2.46.0 — 2026-11-21
12
31
 
13
32
  ### Added
package/docs/agents.md CHANGED
@@ -353,7 +353,8 @@ statement is not seen.
353
353
  Sessions nobody typed into are left out of every listing: scheduled tasks and notifications in
354
354
  Claude Code (every prompt has `origin.kind` or `turnOrigin` other than `human`, or the session
355
355
  opens with a scheduled task nobody answered), headless runs of it with a single prompt (a program
356
- driving it through more prompts is somebody's chat) and `codex exec` runs. They carry `automated: true`;
356
+ driving it through more prompts is somebody's chat), `codex exec` runs, threads the Codex desktop
357
+ app's server ran for another program, and Muse Code's probes. They carry `automated: true`;
357
358
  `sessions --automated`, or `{ automated: true }` in the query, lists them too.
358
359
 
359
360
  **Topics.** Sessions can be kept as pieces of work that cross agents and directories
@@ -396,6 +397,10 @@ only the agent, project and tool name. The user answers these requests in the na
396
397
  Copilot records the decision as soon as it is made. Gemini CLI 0.70 reports the result when
397
398
  the tool finishes, so a refresh can still show its last request while the command runs.
398
399
 
400
+ The hook is declared with the Node that installed it. When that Node goes (a version manager
401
+ removed it), the hook fails without a word; `genaicode hooks status` says `broken` then (`missing`
402
+ in `hooksStatus()`), and `genaicode hooks install` writes it again.
403
+
399
404
  In code: `installHooks('claude')`, `hooksStatus()`, `uninstallHooks()`, and `recordHook(agent,
400
405
  input)` with `readLive()` and `withLive(sessions, records)` to do the same for an agent of your
401
406
  own whose hooks give the same JSON (`session_id`, `hook_event_name`, `cwd`); `hookInput(agent,
@@ -539,7 +544,7 @@ app-server protocol (`codex app-server generate-ts`) no longer has a field that
539
544
 
540
545
  ### Asking an agent about the sessions: `sessions mcp`
541
546
 
542
- The session index provides four read-only MCP tools. In `genaicode chat --sessions`, ask
547
+ The session index provides four read-only MCP tools (and, in a chat, `sessions_send`, below). In `genaicode chat --sessions`, ask
543
548
  "Which sessions need my attention?" to see which project needs a decision or a reply.
544
549
 
545
550
  | tool | what it returns |
@@ -565,6 +570,17 @@ The [session tower](cli.md#open-the-session-tower) opens an indexed chat with a
565
570
  of the queue. Its `/waiting [project]` and `/read <id>` commands call the same read-only
566
571
  operations and display the results to the user. A regular chat message starts an agent turn.
567
572
 
573
+ In `chat --sessions` and `ui --sessions` (the desktop app) the agent also gets `sessions_send`:
574
+ ask it "tell Codex in knights that the bakery is done" and it finds the session and sends the
575
+ message there as a new turn, with that session's own agent in its own directory. The first
576
+ message to each session shows as an approval in the chat, with the recipient and the exact
577
+ text; once allowed, later messages to that session go without asking until the chat closes.
578
+ With auto-approve on (`--yes`, `/auto`) nothing is asked. The tool returns once the message is
579
+ sent, and the chat shows the session's answer when its turn ends. Only a waiting or unfinished
580
+ local session takes a message, as with `sessions send`; closing the chat stops a turn still
581
+ running there. In code: `sessionSendTool(agents, gate)` with a `SessionSendGate` the chat
582
+ attaches to, and `AgentSession.ask()` for the question.
583
+
568
584
  When the tower runs a pack, its lead also receives `propose_session_message` on the pack MCP
569
585
  server. It takes the full session `id`, the exact `text` and an optional `source`. A successful
570
586
  call queues a draft in the operator's inbox. The operator can dismiss it or send it once,
package/docs/cli.md CHANGED
@@ -93,6 +93,10 @@ You can pipe the prompt on stdin or use `-a <agent>` to search one agent's store
93
93
  stays in the native conversation. The driver uses its default permissions unless you select
94
94
  `--sandbox read-only|workspace-write|unrestricted`. Each driver accepts its supported modes.
95
95
 
96
+ Prompts to other sessions are sent by a person. In a shell that a coding agent runs (the agent's
97
+ CLI marks it with a variable such as `CLAUDECODE` or `GEMINI_CLI`) the command refuses unless you
98
+ pass `--force`. This stops an agent sending by accident; it is not a security boundary.
99
+
96
100
  In the browser, choose **Sessions → Reply**, enter the message and choose **Send**. The reply appears
97
101
  in the Sessions view. Both entry points require a local session that is waiting for a reply or
98
102
  stopped mid-turn, with a driver that supports resuming. A running turn or pending tool approval
@@ -120,11 +124,14 @@ the browser's Sessions view has Approve and Deny (see
120
124
 
121
125
  A program that shows what waits (a menu bar, a status line) can keep one process open instead of
122
126
  asking again and again: `npx genaicode sessions --waiting --json --watch` prints one line
123
- `{"sessions":[...]}` at once and another whenever the waiting sessions or their open questions
124
- change. With `--exit-with-stdin` it ends when its stdin closes, so it cannot outlive its parent.
127
+ `{"sessions":[...]}` at once and another whenever they or their open questions change. The
128
+ watch lists only the sessions that ask now: an approval, or a last message that asked something
129
+ in the last three days, not every session whose turn ended. With `--exit-with-stdin` it ends when its stdin closes, so it cannot outlive its parent.
125
130
  It looks every 3 seconds: a question or anything else a hook reports shows at once, a session
126
131
  that only finished its turn within 15 seconds. Once limits are known, the line also carries them
127
- as `"limits":[...]`.
132
+ as `"limits":[...]`. Once there are [topics](#your-work-as-topics-topics), each session carries the name
133
+ of its topic as `"topic"`, and the line the topics of the listed week as
134
+ `"topics":[{"id","name","sessions","asking","active"}]`, at most 12, those that ask first.
128
135
 
129
136
  ### How much of your plans is used: `limits`
130
137
 
@@ -157,9 +164,9 @@ with several agents and from several directories. `npx genaicode topics` shows t
157
164
  agents as topics, what asks for you first:
158
165
 
159
166
  ```
160
- ● Pack mode t1 claude 9, codex 3 12m ago 1 ask you src/genaicode
161
- ▶ Desktop app t2 claude 6 1h ago 1 working src/genaicode, src/site
162
- YouTube pins t3 codex 2 2d ago src/site
167
+ ● Pack mode t1 claude 9, codex 3 12m ago 1 ask you
168
+ ▶ Desktop app t2 claude 6 1h ago 1 working
169
+ YouTube pins t3 codex 2 2d ago
163
170
  14 sessions not sorted yet: "genaicode topics refresh" sorts them.
164
171
  ```
165
172
 
@@ -172,7 +179,9 @@ otherwise); `--since` looks further back than the 30 days it and `topics` cover
172
179
 
173
180
  Sessions that Claude Code ran for a claude.ai project (Remote Control) say which project in their
174
181
  first message. Those go to a topic named as the project, before any agent is asked and at no
175
- cost, so the topics start from the projects you already have. `topics refresh --again` drops the
182
+ cost, so the topics start from the projects you already have. What is left and worked in a
183
+ directory of a project of the Codex desktop app goes to a topic named as that project, whichever
184
+ agent it was. Only the rest is given to an agent. `topics refresh --again` drops the
176
185
  topics there are, corrections included, and sorts every session anew.
177
186
 
178
187
  A topic asks for you (`●`) when a session waits for an approval, or when its last message asked
@@ -199,7 +208,9 @@ In `npx genaicode chat --sessions`, ask "Which sessions need my attention?" The
199
208
  `sessions_waiting` tool shows the same sessions as `genaicode sessions --waiting`, including
200
209
  the project, open approval questions and the latest reply. `npx genaicode sessions mcp` serves
201
210
  the same read-only tools over stdio. The agent can read what the other sessions said and what
202
- their open questions ask. See [session tools](agents.md#asking-an-agent-about-the-sessions-sessions-mcp).
211
+ their open questions ask. Ask it to pass something to another session ("tell Codex in
212
+ knights that...") and it sends it with `sessions_send`; you allow the first message to each
213
+ session in the chat. See [session tools](agents.md#asking-an-agent-about-the-sessions-sessions-mcp).
203
214
 
204
215
  ### Open the session tower
205
216
 
@@ -242,7 +253,13 @@ In the browser, **Sessions** in the header shows what every agent on this machin
242
253
  the same list as `genaicode sessions`, by project, with search over titles, prompts, directories
243
254
  and branches, and filters by agent, state and period. A local session gives the command that
244
255
  continues it in a terminal, and **Continue here** when it is from this directory; a cloud session
245
- links to its page.
256
+ links to its page. Once [`genaicode topics refresh`](#your-work-as-topics-topics) has sorted
257
+ your sessions, the view groups them by topic instead (those that ask for you first), and
258
+ **By directory** brings the projects back.
259
+
260
+ The header shows how much of the chosen agent's plan is used (`7d 19%`): what the session's runs
261
+ report, and before that what `genaicode limits` last saw. With a plan limit known, the price of
262
+ the session's tokens is left out: on a plan it would be an estimate nobody pays.
246
263
 
247
264
  The terminal and the browser can show one session. `/web` in the terminal chat opens it in
248
265
  the browser (`/web off` stops the server), and Enter in the terminal that runs
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "genaicode",
3
- "version": "2.46.0",
3
+ "version": "2.47.0",
4
4
  "description": "Drive the coding-agent CLIs you already have (Claude Code, Codex, Copilot, Cursor, Gemini, opencode...) behind one API and one CLI, plus a thin provider-neutral LLM layer.",
5
5
  "author": "Grzegorz Tańczyk",
6
6
  "repository": {