@rnbsolucoes/axion-code 0.1.16 → 0.1.18

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 CHANGED
@@ -280,8 +280,20 @@ guarded dispatcher must use.
280
280
  Requests are persisted in the shared session database under
281
281
  `%USERPROFILE%\.axion\sessions\axion.db` with the redacted decision, risk class,
282
282
  permission mode, impact summary and pending/approved/denied state. This is the
283
- headless contract that the TUI approval modal and guarded dispatcher will use
284
- before mutating filesystem, shell or MCP tools are enabled.
283
+ headless contract used by the TUI approval menu and the future guarded
284
+ dispatcher before mutating filesystem, shell or MCP tools are enabled.
285
+
286
+ Provider stream `tool_call` events now open the TUI approval menu when the
287
+ active permission mode requires review. Approve/Deny records the audited
288
+ decision and returns focus to the chat input. Actual tool execution remains
289
+ limited to the guarded dispatcher allow-list.
290
+
291
+ `axion tool run` exposes the first guarded dispatcher surface. It currently
292
+ supports `Read`, `Glob`, `Grep`, `Write` and `Edit` inside the active workspace.
293
+ When the active permission mode requires approval, execution is allowed only if
294
+ the supplied approval is already approved and matches the exact redacted tool
295
+ request. Shell, MCP, browser, process and unknown tools remain unsupported even
296
+ when an approval exists.
285
297
 
286
298
  Examples:
287
299
 
@@ -292,6 +304,8 @@ axion permission inspect mcp__serena__replace_symbol_body "{}" --mode full_permi
292
304
  axion permission request Bash "{\"command\":\"npm install left-pad\"}" --mode full_permission --session smoke --turn turn-1 --json
293
305
  axion permission approvals --session smoke --decision pending --json
294
306
  axion permission resolve <approval-id> --deny --reason "not needed" --json
307
+ axion tool run Read "{\"path\":\"README.md\"}" --mode full_permission --json
308
+ axion tool run Write "{\"path\":\"notes/out.txt\",\"content\":\"approved\"}" --session smoke --turn turn-1 --approval <approval-id> --mode request_permission --json
295
309
  ```
296
310
 
297
311
  Security invariants:
@@ -341,7 +355,9 @@ This is a functional direction MVP, not the full harness:
341
355
  deferred until the Nexus beta handoff;
342
356
  - terminal logo uses Sixel when available and falls back to width-bounded ANSI/block rendering;
343
357
  - initial chat splash shows the Axion logo and system name until the first interaction;
344
- - no mutating tool execution yet; the approval/sandbox classification and persisted approval queue contracts are implemented and inspectable;
358
+ - guarded dispatcher execution is limited to workspace-local `Read`, `Glob`,
359
+ `Grep`, `Write` and `Edit`; shell, MCP, browser, process and unknown tools
360
+ remain blocked;
345
361
  - no executable Pi RPC bridge yet;
346
362
  - no MCP transport execution yet;
347
363
  - native subagent execution is prompt-isolated and provider/model-inherited; richer multi-subagent orchestration, streaming and budget telemetry remain next-cycle items.
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rnbsolucoes/axion-code",
3
- "version": "0.1.16",
3
+ "version": "0.1.18",
4
4
  "description": "Axion Code CLI harness for the Axion ecosystem.",
5
5
  "type": "module",
6
6
  "repository": {