@rnbsolucoes/axion-code 0.1.19 → 0.1.21

package/README.md

@@ -285,15 +285,21 @@ dispatcher before mutating filesystem, shell or MCP tools are enabled.
 
 Provider stream `tool_call` events now open the TUI approval menu when the
 active permission mode requires review. Approve/Deny records the audited
-decision and returns focus to the chat input. Actual tool execution remains
-limited to the guarded dispatcher allow-list.
-
-`axion tool run` exposes the first guarded dispatcher surface. It currently
-supports `Read`, `Glob`, `Grep`, `Write` and `Edit` inside the active workspace.
-When the active permission mode requires approval, execution is allowed only if
-the supplied approval is already approved and matches the exact redacted tool
-request. Shell, MCP, browser, process and unknown tools remain unsupported even
-when an approval exists.
+decision and returns focus to the chat input. When approved, the TUI executes
+supported guarded-dispatcher tools and prints the bounded result in the
+timeline. Successful supported tool results are then sent back into the active
+provider as a follow-up `tool_result` continuation turn, so the agent can use
+the evidence before answering. Unsupported tools remain explicitly pending until
+a dedicated adapter exists.
+
+`axion tool run` exposes the first guarded dispatcher surface. The CLI and TUI
+currently support `Read`, `Glob`, `Grep`, `Write` and `Edit` inside the active
+workspace. Provider tool aliases such as `read_file` and `write_file` are
+normalized to the native tool names before approval/execution. When the active
+permission mode requires approval, execution is allowed only if the supplied
+approval is already approved and matches the exact redacted tool request.
+Shell, MCP, browser, process and unknown tools remain unsupported even when an
+approval exists.
 
 Examples:
 
@@ -356,8 +362,10 @@ This is a functional direction MVP, not the full harness:
 - terminal logo uses Sixel when available and falls back to width-bounded ANSI/block rendering;
 - initial chat splash shows the Axion logo and system name until the first interaction;
 - guarded dispatcher execution is limited to workspace-local `Read`, `Glob`,
-  `Grep`, `Write` and `Edit`; shell, MCP, browser, process and unknown tools
-  remain blocked;
+  `Grep`, `Write` and `Edit`; the TUI executes these after approval and shows
+  the result, then feeds successful supported results back into the provider as
+  an iterative `tool_result` continuation turn;
+- shell, MCP, browser, process and unknown tools remain blocked;
 - no executable Pi RPC bridge yet;
 - no MCP transport execution yet;
 - native subagent execution is prompt-isolated and provider/model-inherited; richer multi-subagent orchestration, streaming and budget telemetry remain next-cycle items.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rnbsolucoes/axion-code",
-  "version": "0.1.19",
+  "version": "0.1.21",
   "description": "Axion Code CLI harness for the Axion ecosystem.",
   "type": "module",
   "repository": {