@rnbsolucoes/axion-code 0.1.43 → 0.1.44
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
|
@@ -390,15 +390,16 @@ Maestro/workers loop from the new Desktop Nexus provider:
|
|
|
390
390
|
|
|
391
391
|
```powershell
|
|
392
392
|
axion provider nexus status --profile nexus
|
|
393
|
-
axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --judge sakana:fugu --image-model image-default --video-model video-pro --exec3 mock:mock/worker --exec3-instruction "general text worker"
|
|
393
|
+
axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --judge sakana:fugu --image-provider imagehub --image-model image-default --video-provider videohub --video-model video-pro --exec3 mock:mock/worker --exec3-instruction "general text worker"
|
|
394
394
|
```
|
|
395
395
|
|
|
396
|
-
PCP in the CLI
|
|
397
|
-
`
|
|
398
|
-
for Fusion and PCP phases; internal
|
|
399
|
-
not surface as app-level tool
|
|
400
|
-
|
|
401
|
-
|
|
396
|
+
PCP in the CLI supports Maestro tool-calling with text workers `exec3` and
|
|
397
|
+
`exec4`, plus image/video slots exposed as internal PCP workers. Nexus streams
|
|
398
|
+
normalized lifecycle telemetry to the TUI for Fusion and PCP phases; internal
|
|
399
|
+
PCP worker dispatches stay private and do not surface as app-level tool
|
|
400
|
+
approvals. Image/video dispatch is refused unless permission mode is `yolo`;
|
|
401
|
+
even in `yolo`, the CLI currently returns a structured "media runtime
|
|
402
|
+
unavailable" tool result until the local media runtime lands.
|
|
402
403
|
|
|
403
404
|
## Build
|
|
404
405
|
|
|
@@ -415,10 +416,10 @@ This is a functional direction MVP, not the full harness:
|
|
|
415
416
|
|
|
416
417
|
- direct provider streaming exists for OpenAI-compatible chat completions,
|
|
417
418
|
OpenAI Responses and Anthropic Messages;
|
|
418
|
-
- Nexus supports the legacy Fusion engine and the new PCP
|
|
419
|
-
|
|
420
|
-
|
|
421
|
-
|
|
419
|
+
- Nexus supports the legacy Fusion engine and the new PCP Maestro/workers
|
|
420
|
+
engine with stream normalization, redacted audit surfacing, TUI Nexus
|
|
421
|
+
configuration, text workers and permission-gated image/video worker
|
|
422
|
+
placeholders; real CLI media generation remains deferred;
|
|
422
423
|
- terminal logo uses Sixel when available and falls back to width-bounded ANSI/block rendering;
|
|
423
424
|
- initial chat splash shows the Axion logo and system name until the first interaction;
|
|
424
425
|
- guarded dispatcher execution is limited to workspace-local `Read`, `Glob`,
|
|
Binary file
|
|
Binary file
|