@akanjs/cli 3.2.0-rc.21 → 3.2.0-rc.23

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/.build-stamp CHANGED
@@ -1,2 +1,2 @@
1
- 0474fbf53ddbc090a2ab91eedf6a2fe0250a06594cdf5028738bf1b37222cbbc
2
- 8f7a3e07-5e28-43d8-8272-9e6ef6864daf
1
+ 453653a82e17f6d621f9b780ce9abf46be6943bf11498171f1ecc6df5b88d5a9
2
+ fcddfd18-304c-4a25-a9ea-0a160d001c94
@@ -69,7 +69,7 @@ pages declaring one name never clash, and a registry kept outside the surface re
69
69
  panel the app already titles, and `defaultDraft` opens the composer with text in it without sending it. A panel driven by a
70
70
  controlled `open` with **no** `onOpenChange` draws no close button at all rather than an inert one. Then the
71
71
  slots: `AgentLauncher`, `AgentSteps`, `AgentBubble`, `AgentComposer`, `AgentApproval`,
72
- `AgentQuestion`, `AgentToolCard`, `AgentQueued`, `AgentMenu`, `AgentMarkdown` and `AgentCode` each replace one part in `_overrides.tsx`, and
72
+ `AgentQuestion`, `AgentToolCard`, `AgentToolRow`, `AgentQueued`, `AgentMenu`, `AgentMarkdown` and `AgentCode` each replace one part in `_overrides.tsx`, and
73
73
  `akanjs/ui` exports every default beside them (`DefaultBubble`, `DefaultComposer`, …) so a skin composes the
74
74
  one it is replacing. **`AgentSteps` is one agent turn** — the messages between the user message that opened it
75
75
  and the next one, with `isRunning` saying whether more are still coming — which is the grain a chat needs to
@@ -791,7 +791,9 @@ pages declaring one name never clash, and a registry kept outside the surface re
791
791
  keeps a free-text row either way, because the model wrote the options and only the user knows whether the answer
792
792
  is among them. The loop parks on the question exactly as it parks on an approval, a dismissal is the tool's
793
793
  error result rather than a silent empty answer, and the settled exchange renders as question-and-answer instead
794
- of a tool row. **Never re-implement it per screen** — a `st.tool("askAboutX")` that opens a modal is the same
794
+ of a tool row. A restored transcript that ends on an unanswered `askUser` — a server run that parked on it while
795
+ no chat was open, or a reload mid-question — opens on that question, and settling it runs the turn on through the
796
+ runner; a turn started first closes it as unanswered instead. **Never re-implement it per screen** — a `st.tool("askAboutX")` that opens a modal is the same
795
797
  thing with a worse transcript — and a hook tool named `askUser` shadows it like any other built-in. The line
796
798
  between it and a `.card()` tool is what the answer *is*: a sentence or a pick off a list is `askUser` and belongs
797
799
  to the conversation, while a shape the model must not invent — fields, a form, a signature — is a card the screen
@@ -49,7 +49,9 @@ export class FileSlice extends slice(srv.file, {
49
49
  - **`mcp: "agent"` keeps it off `/mcp` and on the in-process agent.** It goes wherever `mcp: false` goes, a slice
50
50
  map key included. `/mcp` neither lists nor runs it and `listingCost` leaves it out, while `AgentToolsRole` and
51
51
  `agentService.loop` list it under the same guards and exclusions. Use it when the listing's size, not the step,
52
- keeps an entry off. A lib's slice and the app's keep the narrowest: `false`, then `"agent"`, then listed.
52
+ keeps an entry off. A lib's slice and the app's keep the narrowest: `false`, then `"agent"`, then listed. Code
53
+ that reads `signalOption.mcp` to tell whether an entry is listed tests `(mcp ?? true) === true`, never
54
+ `mcp !== false`.
53
55
  - **`mcp: true` is the default and is a no-op**; write it only to say out loud that an entry is deliberately on
54
56
  the shelf. It does not override a shape refusal (an `Any` return stays refused) and it cannot publish something
55
57
  the guard rules keep out.
@@ -544,6 +546,10 @@ at every event.
544
546
  (`akanjs/ui`), sent over your own transport. It is client input, and a name an endpoint holds is dropped. The run
545
547
  never runs one: `approve` is asked, then the run ends `awaiting` with `client: true`. Have the page `run(call)`,
546
548
  append its result — or your own error when no page answers — and resume.
549
+ - **Asking the member.** `ask: true` lists `askUser({ question, choices?, multiple? })`, the in-page chat's own tool.
550
+ A call ends the run `awaiting` with `question: true`; put the question to the member, append
551
+ `{ id, name: "askUser", result }` — or an `error` when they dismiss it — and resume. It never reaches `approve`,
552
+ counts as no tool call, and `untrusted` never sees the answer. A `clientTools` entry by that name is dropped.
547
553
  - **Writes after untrusted input.** `untrusted(result)` marks a result third parties wrote, and every later call
548
554
  reaches `approve(call, { tainted, tool })` with `tainted` set. A batch is judged before it runs, since the model
549
555
  wrote it before reading its results. Without `approve`, a `needsConfirm` tool — on this catalogue, a mutation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@akanjs/cli",
3
- "version": "3.2.0-rc.21",
3
+ "version": "3.2.0-rc.23",
4
4
  "sourceType": "module",
5
5
  "type": "module",
6
6
  "publishConfig": {
@@ -39,7 +39,7 @@
39
39
  "@earendil-works/pi-tui": "1.3.0",
40
40
  "@inquirer/prompts": "^8.7.3",
41
41
  "@tailwindcss/node": "^4.3.3",
42
- "akanjs": "3.2.0-rc.21",
42
+ "akanjs": "3.2.0-rc.23",
43
43
  "chalk": "^6.0.1",
44
44
  "commander": "^15.0.0",
45
45
  "dayjs": "^1.11.23",
@@ -40,7 +40,8 @@ an endpoint with a real guard is published, one with none is refused, and so is
40
40
  runs a model over those tools until it answers; `option.setAgentAccountResolver` resolves a stored `principal`
41
41
  before every round. Each round is metered as its own turn with `turn.loop` and `turn.meta`. `toolkits` holds named
42
42
  groups of `allow` back until the model calls `openToolkit`; `clientTools` (from `AgentClientTools` on an open page)
43
- parks a call as `awaiting { client: true }` for the page to run.
43
+ parks a call as `awaiting { client: true }` for the page to run; `ask: true` lists `askUser`, which parks as
44
+ `awaiting { question: true }` until you append the member's answer.
44
45
 
45
46
  ## Verify
46
47