@rnbsolucoes/axion-code 0.1.20 → 0.1.21

package/README.md

@@ -287,8 +287,10 @@ 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. When approved, the TUI executes
 supported guarded-dispatcher tools and prints the bounded result in the
-timeline. Unsupported tools remain explicitly pending until a dedicated adapter
-exists.
+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
@@ -361,8 +363,8 @@ This is a functional direction MVP, not the full harness:
 - 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`; the TUI executes these after approval and shows
-  the result, but the result is not yet fed back into the provider as an
-  iterative `tool_result` turn;
+  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;

package/package.json

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