@rnbsolucoes/axion-code 0.1.29 → 0.1.32
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
|
@@ -66,6 +66,7 @@ axion-code agents run bug-hunter "review this login flow"
|
|
|
66
66
|
axion-code agents run-many bug-hunter,performance-reviewer "review this login flow" --budget-tokens 2000 --stream
|
|
67
67
|
axion-code learn --json
|
|
68
68
|
axion-code package inspect <path>
|
|
69
|
+
axion-code package self-check --json
|
|
69
70
|
```
|
|
70
71
|
|
|
71
72
|
## Install
|
|
@@ -105,6 +106,18 @@ current platform into the local Axion Code bin directory and then executes it. I
|
|
|
105
106
|
a source clone only, if no packaged binary exists, the wrapper can build from Go
|
|
106
107
|
as a development fallback.
|
|
107
108
|
|
|
109
|
+
To classify the currently executed binary for support or security review, run:
|
|
110
|
+
|
|
111
|
+
```powershell
|
|
112
|
+
axion package self-check --json
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
The self-check reports the executable path, real path, runtime version,
|
|
116
|
+
SHA-256, file size, package cache marker when present and a provenance
|
|
117
|
+
classification such as `npm-wrapper-cache`, `npm-package-release`,
|
|
118
|
+
`source-build` or `unknown-local-binary`. It is deterministic local
|
|
119
|
+
provenance, not a replacement for future Authenticode signing.
|
|
120
|
+
|
|
108
121
|
Requirements:
|
|
109
122
|
|
|
110
123
|
- Node.js 18+ for the npm wrapper.
|
|
@@ -368,6 +381,23 @@ axion provider profile set or-free
|
|
|
368
381
|
axion
|
|
369
382
|
```
|
|
370
383
|
|
|
384
|
+
Nexus profiles share the same `%USERPROFILE%\.axion\harness\nexus-config.json`
|
|
385
|
+
used by Axion Desktop. The default `fusion` engine runs the existing
|
|
386
|
+
panel -> judge -> final flow. The `pcp` engine enables the text-only
|
|
387
|
+
Maestro/workers loop from the new Desktop Nexus provider:
|
|
388
|
+
|
|
389
|
+
```powershell
|
|
390
|
+
axion provider nexus status --profile nexus
|
|
391
|
+
axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --judge sakana:fugu --exec3 mock:mock/worker --exec3-instruction "general text worker"
|
|
392
|
+
```
|
|
393
|
+
|
|
394
|
+
PCP in the CLI currently supports Maestro tool-calling with text workers
|
|
395
|
+
`exec3` and `exec4`. Nexus streams normalized lifecycle telemetry to the TUI
|
|
396
|
+
for Fusion and PCP phases; internal PCP worker dispatches stay private and do
|
|
397
|
+
not surface as app-level tool approvals. Image/video generative slots are
|
|
398
|
+
preserved in the shared schema for Desktop compatibility but are not executed
|
|
399
|
+
by the CLI yet.
|
|
400
|
+
|
|
371
401
|
## Build
|
|
372
402
|
|
|
373
403
|
```powershell
|
|
@@ -382,8 +412,11 @@ If Go is not on PATH, use a verified local Go toolchain and keep generated binar
|
|
|
382
412
|
This is a functional direction MVP, not the full harness:
|
|
383
413
|
|
|
384
414
|
- direct provider streaming exists for OpenAI-compatible chat completions,
|
|
385
|
-
OpenAI Responses and Anthropic Messages;
|
|
386
|
-
|
|
415
|
+
OpenAI Responses and Anthropic Messages;
|
|
416
|
+
- Nexus supports the legacy Fusion engine and the new PCP text-only
|
|
417
|
+
Maestro/workers engine with initial stream normalization; richer judge
|
|
418
|
+
telemetry, redaction/audit surfacing, TUI Nexus configuration and image/video
|
|
419
|
+
workers remain deferred;
|
|
387
420
|
- terminal logo uses Sixel when available and falls back to width-bounded ANSI/block rendering;
|
|
388
421
|
- initial chat splash shows the Axion logo and system name until the first interaction;
|
|
389
422
|
- guarded dispatcher execution is limited to workspace-local `Read`, `Glob`,
|
|
Binary file
|
|
Binary file
|