@rnbsolucoes/axion-code 0.1.83 → 0.1.85

package/README.md

@@ -19,9 +19,10 @@ This MVP follows the PREVC-P documentation package in `.context/`:
 - Axion Desktop fallback provider presets, including OpenAI-compatible and Anthropic-compatible endpoints;
 - shared Axion Desktop/CLI provider, model and permission stores under `%USERPROFILE%\.axion`;
 - Pi Agent assets in inspect/import-only mode;
-- native dotcontext and MCP management posture;
-- plan-scoped PREVC + A learning consolidation through `/learn`;
-- shared plugin and native isolated subagent catalogs.
+- native dotcontext and MCP management posture;
+- plan-scoped PREVC + A learning consolidation through `/learn`;
+- shared plugin and native isolated subagent catalogs;
+- native localhost browser control and Windows computer-use inspection commands.
 
 ## MVP Commands
 
@@ -43,9 +44,17 @@ axion-code remote-control events --json
 axion-code remote-control seal --json < payload.json
 axion-code remote-control open --json < secure-frame.json
 axion-code remote-control relay --listen 127.0.0.1:8787 --json
+axion-code browser dev start --command "npm run dev" --cwd . --json
+axion-code browser open http://127.0.0.1:5173 --json
+axion-code browser logs --duration 5s --json
+axion-code browser eval --expr "document.title" --json
+axion-code browser click --selector "button[type=submit]" --json
+axion-code browser screenshot --path .context/runtime/browser/screenshot.png --json
+axion-code computer-use status --json
+axion-code computer-use screenshot --path .context/runtime/computer-use/screenshot.png --json
 axion-code provider list --json
-axion-code provider profile init
-axion-code provider profile list --json
+axion-code provider profile init
+axion-code provider profile list --json
 axion-code provider profile add or-free --catalog openrouter --model openrouter/free --credential-ref env:OPENROUTER_API_KEY
 axion-code provider profile set or-free
 axion-code provider profile delete or-free
@@ -108,9 +117,46 @@ The relay exposes `GET /remote-control/sessions`, `POST /remote-control/pair`,
 It is loopback-only, keeps provider/tool execution in the CLI and accepts mobile
 intents only after SAS pairing.
 
+## Native Browser And Computer-Use
+
+`axion-code browser` is the native localhost navigation plugin. It can start a
+workspace-contained dev server, open a localhost URL in a supervised Chrome/Edge
+instance, inspect console logs, evaluate JavaScript, click/type by CSS selector
+and save page screenshots.
+
+Browser control is intentionally local-only: accepted hosts are `localhost`,
+`127.0.0.1` and `[::1]`, with `localhost` normalized to `127.0.0.1` for Windows
+dev-server reliability. CDP binds to `127.0.0.1` and uses an isolated profile
+under `%USERPROFILE%\.axion\browser-control\profile`.
+
+```powershell
+axion-code browser dev start --command "npm run dev" --cwd . --json
+axion-code browser open http://127.0.0.1:5173 --json
+axion-code browser logs --duration 5s --json
+axion-code browser eval --expr "document.title" --json
+axion-code browser click --selector "button[type=submit]" --json
+axion-code browser type --selector "input[name=q]" --text "Axion" --json
+axion-code browser screenshot --path .context/runtime/browser/screenshot.png --json
+axion-code browser dev stop --json
+axion-code browser stop --json
+```
+
+`axion-code computer-use` is a guarded Windows MVP for desktop screenshot,
+absolute-coordinate click, text entry and hotkeys. Mutating actions are
+classified as high-risk browser-action tools and require approval unless the
+active permission mode is `YOLO`.
+
+```powershell
+axion-code computer-use status --json
+axion-code computer-use screenshot --path .context/runtime/computer-use/screenshot.png --json
+axion-code computer-use click --x 100 --y 200 --json
+axion-code computer-use type --text "hello" --json
+axion-code computer-use hotkey --keys ctrl+l --json
+```
+
 ## Install
-
-Official install, after the package is published to the public npm registry:
+
+Official install, after the package is published to the public npm registry:
 
 ```powershell
 npm install -g @rnbsolucoes/axion-code
@@ -390,16 +436,17 @@ 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 guarded dispatcher surface. The CLI and TUI
-currently support workspace-local `Read`, `Glob`, `Grep`, `Write` and `Edit`,
-governed `Shell`/`Bash`/`PowerShell` commands that run from a workspace
-directory with timeout and bounded output, and enabled stdio MCP tools named as
-`mcp__<server-id>__<tool-name>`. Provider tool aliases such as `read_file`,
-`write_file` and `run_command` are normalized to 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. Remote MCP transports, browser, process and
-unknown tools remain unsupported even when an approval exists.
+`axion tool run` exposes the guarded dispatcher surface. The CLI and TUI
+currently support workspace-local `Read`, `Glob`, `Grep`, `Write` and `Edit`,
+governed `Shell`/`Bash`/`PowerShell` commands that run from a workspace
+directory with timeout and bounded output, enabled stdio MCP tools named as
+`mcp__<server-id>__<tool-name>`, native localhost `browser_*` tools and guarded
+Windows `computer_*` tools. Provider tool aliases such as `read_file`,
+`write_file` and `run_command` are normalized to 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. Remote MCP transports, arbitrary process tools and
+unknown tools remain unsupported even when an approval exists.
 
 Examples:
 
@@ -491,12 +538,14 @@ This is a functional direction MVP, not the full harness:
   placeholders; real CLI media generation remains deferred;
 - 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`, governed workspace-scoped shell commands and
-  enabled stdio MCP tools;
-  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;
-- remote MCP transports, browser, process and unknown tools remain blocked;
+- guarded dispatcher execution includes workspace-local `Read`, `Glob`,
+  `Grep`, `Write` and `Edit`, governed workspace-scoped shell commands, enabled
+  stdio MCP tools, native localhost `browser_*` tools and guarded Windows
+  `computer_*` tools;
+  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;
+- remote MCP transports, arbitrary process control and unknown tools remain
+  blocked;
 - no executable Pi RPC bridge yet;
 - native subagent execution is prompt-isolated and provider/model-inherited; `agents run-many` provides parallel fan-out, compact comparison, aggregate usage, a token budget ceiling and streamed lifecycle/telemetry events. Provider/model cost ceilings are enforced by the shared Axion cost policy.

package/package.json

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