@nexus-cortex/cli 4.108.5 → 4.108.8
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/.env.defaults +29 -0
- package/package.json +2 -2
package/.env.defaults
CHANGED
|
@@ -756,6 +756,10 @@ CORTEX_ENDTURN_GATE=true
|
|
|
756
756
|
# ROLLED forward with the dropped messages (memorySource `rolled`); the rung RE-ARMS after each compaction so the last band before the
|
|
757
757
|
# threshold refires every cycle (one whole-conversation helper call per cycle). Live: 28 compactions / 28 fresh covering checkpoints /
|
|
758
758
|
# 0 stale replays (proof run 6). The v2 rule (token distance) replayed ONE stale memory into 27 compactions — never ship a reuse test on tokens.
|
|
759
|
+
# [LEDGER 2026-09-13 @4.108.8] R132 HB-COMPACTION-ESTIMATE: the estimator is now ANCHORED on the provider's last reported prompt_tokens
|
|
760
|
+
# (+ chars/4 of what was appended since; proportional shrink after a drop) — the chars/4-of-the-JSON-envelope heuristic (R129-scaled) is only
|
|
761
|
+
# the fallback before the first usage arrives. Field read on the TB4.0 definitive run (4.108.5): heat-pump-warranty compacted at "760K-1.0M"
|
|
762
|
+
# vs an API max of 151,763 prompt tokens (5-7x over). Compaction rows now bank estimateSource usage-anchored|heuristic + anchorTokens.
|
|
759
763
|
#CORTEX_COMPACTION_CHECKPOINT_PCT=
|
|
760
764
|
#CORTEX_COMPACTION_CHECKPOINT_STEP=
|
|
761
765
|
# CORTEX_COMPACTION_THRESHOLD_TOKENS — TEST/OPS OVERRIDE of the compaction threshold (4.108.3). Unset (default) = the threshold is derived
|
|
@@ -768,6 +772,15 @@ CORTEX_ENDTURN_GATE=true
|
|
|
768
772
|
# proof (/tmp/claude-1000/cmp-test/run.sh, deepseek-flash, threshold 14000, rung 0.6): checkpoint fired, 6 proactive compactions in 17
|
|
769
773
|
# iterations (5 reused the checkpoint at $0), task pinned verbatim in every reminder, final answer 4/4 planted facts — mechanism proven.
|
|
770
774
|
#CORTEX_COMPACTION_THRESHOLD_TOKENS=
|
|
775
|
+
# CORTEX_STATE_DIR — explicit runtime-state root (4.108.6, HB-READONLY-WORKDIR / R131). Unset (default) = <project>/.cortex, but the root
|
|
776
|
+
# is PROBED for writability once per project: a read-only or foreign-owned working directory (a task image that runs the agent as `nobody`
|
|
777
|
+
# in a root-owned /app) falls back to ~/.cortex/projects/<hash>, then <tmpdir>/nexus-cortex/<hash>, with ONE warning. Every runtime writer
|
|
778
|
+
# (tmux metadata/locks, artifact registry, sessions, decisions.jsonl, training samples, resume memory) routes through it, so state
|
|
779
|
+
# persistence is never a boot precondition. Set it to pin the root explicitly (containers, benches, shared checkouts).
|
|
780
|
+
# [LEDGER 2026-09-12 @4.108.6] BUILT + unit-tested (utils/__tests__/stateDir.test.ts); field cause = TB4.0 risk-scorer-replay: cortex-server
|
|
781
|
+
# died at boot (EACCES mkdir /app/.cortex/tmux-sessions/metadata) → empty session. Verify = boot the server as an unprivileged user in a
|
|
782
|
+
# root-owned cwd (docker probe) → boots with the fallback warning.
|
|
783
|
+
#CORTEX_STATE_DIR=
|
|
771
784
|
|
|
772
785
|
# CORTEX_DELEGATION_HINT — DARK (4.108.1, HB-DELEGATION-DOCTRINE). true = the boot-minimal prompt gains ONE clause naming the Task tool for
|
|
773
786
|
# large / independent / output-heavy sub-tasks (delegate with a self-contained prompt, continue from the summary). The Task tool is
|
|
@@ -776,6 +789,18 @@ CORTEX_ENDTURN_GATE=true
|
|
|
776
789
|
# [LEDGER 2026-09-12 @4.108.1] BUILT + unit-tested (delegationHint.test.ts); DARK — prompt mass on the narrow door is a measured lever, so it
|
|
777
790
|
# needs an A/B on the long-horizon population (TB4.0) before any default. Field read = task_spawn count per session.
|
|
778
791
|
#CORTEX_DELEGATION_HINT=
|
|
792
|
+
# CORTEX_SUBAGENT_TIMEOUT_MS / CORTEX_SUBAGENT_TIMEOUT_MAX_MS — R133 HB-SUBAGENT-TIMEOUT (4.108.8). The Task sub-agent's wall-clock limit was a
|
|
793
|
+
# hardcoded 300 s regardless of the parent's budget: on the TB4.0 definitive run 3 of 6 delegates were cut at 300.0 s (one after 62 turns and
|
|
794
|
+
# 6 files modified, the parent redid the work). Now: the Task input `timeout_ms` wins (clamped to [60 s, remaining-30 s]); else a parent turn
|
|
795
|
+
# deadline (CORTEX_TURN_DEADLINE_MS, set per task by the bench adapter) gives 90% of the REMAINING budget minus 30 s, capped by
|
|
796
|
+
# CORTEX_SUBAGENT_TIMEOUT_MAX_MS if set; else CORTEX_SUBAGENT_TIMEOUT_MS; else 300000. The child receives the same limit as ITS turn deadline
|
|
797
|
+
# only when a real deadline exists. A TIMEOUT result still carries the partial response + Files Modified (inspect on-disk state, don't redo).
|
|
798
|
+
# The outer per-batch abort now honors the resolved Task/Browse limit (it was a Bash-only 150 s cap that killed delegates first).
|
|
799
|
+
# task_spawn decision rows bank timeoutMs[] + remainingMs. Unset = derived as above.
|
|
800
|
+
# [LEDGER 2026-09-13 @4.108.8] BUILT + unit-tested (subAgentTimeout.test.ts, outerToolTimeout.test.ts); validation cell = the 3 TB4.0 tasks
|
|
801
|
+
# whose delegates timed out (mp-checkpoint-consolidation, retro-console-soc, vllm-deepseek-streaming) — PENDING.
|
|
802
|
+
#CORTEX_SUBAGENT_TIMEOUT_MS=
|
|
803
|
+
#CORTEX_SUBAGENT_TIMEOUT_MAX_MS=
|
|
779
804
|
# Stage 4 (4.70.0, requires the gate ON): task-requirements attestation —
|
|
780
805
|
# enumerate each stated requirement with what satisfies it + how it was
|
|
781
806
|
# verified; mutating turns with no checks are challenged. Default OFF.
|
|
@@ -871,6 +896,10 @@ CHROMIUM_BIN=
|
|
|
871
896
|
# Alternate Chromium path honored by Playwright
|
|
872
897
|
PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH=
|
|
873
898
|
# Override the tmux binary used by visual agent monitoring (auto-detected if unset)
|
|
899
|
+
# [LEDGER 2026-09-13 @4.108.8] R134 HB-TMUX-FALLBACK: when tmux is ABSENT, Bash `persistentSession` and CreateArtifactTool persistent/dev
|
|
900
|
+
# process artifacts no longer refuse — they degrade to a detached background process (BackgroundProcessRegistry; poll with BashOutput) with a
|
|
901
|
+
# `[WARN] tmux not available: ...` first line naming the lost semantics (state/cwd/env persistence, attach/reconnect, dashboard restart).
|
|
902
|
+
# Field read: TB4.0 ctr-optimization (no tmux in the image) lost its long-running monitor after 16 refused CreateArtifactTool calls.
|
|
874
903
|
TMUX_BIN=
|
|
875
904
|
# Google Vertex AI project (only when using Vertex instead of the Gemini API)
|
|
876
905
|
GOOGLE_CLOUD_PROJECT=
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@nexus-cortex/cli",
|
|
3
|
-
"version": "4.108.
|
|
3
|
+
"version": "4.108.8",
|
|
4
4
|
"description": "Nexus Cortex CLI - Terminal interface for multi-provider LLM orchestration",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"type": "module",
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"prepack": "node ../../scripts/copy-pkg-cortex-scaffold.mjs"
|
|
20
20
|
},
|
|
21
21
|
"dependencies": {
|
|
22
|
-
"@nexus-cortex/core": "4.108.
|
|
22
|
+
"@nexus-cortex/core": "4.108.8",
|
|
23
23
|
"chalk": "^4.1.2",
|
|
24
24
|
"cli-spinners": "^2.9.0",
|
|
25
25
|
"commander": "^11.0.0",
|