AgenticNetOS 2.42.0

The persona-first release: for judgment-heavy goals every surface now proposes a named specialist or team before exposing workflow machinery, and a persona can keep its full bounded agent loop while reasoning through a local headless Claude Code or Codex session — unattended, with no server LLM provider. Proven end to end before shipping: a bash-mode developer persona on a provider-less master answered a task with nobody connected, input consumed exactly once.

Added

• Persona-first authoring across MCP, CLI, integrations, and Desktop. Newcomer guidance now starts with named specialists (developer, health coach, domain expert) and specialist teams, then teaches the Agentic-Net beneath them: charter, inbox/outbox, durable context, deterministic review hand-offs, context playbooks via typed link transitions, and reviewable learning that can crystallize into tool-nets. MCP adds agenticnets://docs/personas and the design-persona-team prompt; the tray manual teaches the same model in both Desktop editions.
• Explicit persona execution backends (agentic-net-mcp). spawn_persona accepts server, claude-code, codex, connected-client, or health-aware auto; add_transition kind:"agent" exposes llmMode:"bash" and binary:"claude"|"codex". Every persona creation result names its backend and whether it runs while disconnected.

Changed

• Persona agents are the default product language. MCP instructions, CLI agent knowledge, the OpenCode integration, and the Claude control skill now proactively translate judgment-heavy goals into a specialist or team and reserve naked workflows for deterministic routing and bookkeeping.

Fixed

• Provider-disabled master no longer strands CLI-backed agent transitions (agentic-net-master). The scheduler, direct dispatcher, start warnings, external-fire roster, and runtime status now distinguish provider-backed AI lanes from agent lanes that reason through a local headless Claude Code/Codex process. CLI-backed personas stay master-owned and schedulable; diagnostics expose executionBackend and requiresServerLlmProvider so clients do not race or misreport them. The explicit bash backend is now honored even when an agent declares no tier, and Codex sessions run ephemerally in a read-only sandbox with the non-repository prompt directory handled explicitly.
• CLI availability is probed, never assumed (agentic-net-master, agentic-net-mcp, agentic-net-desktop). Three layers of the same honesty gap, found in review. (1) Master now probes each headless CLI by actually running it — command -v alone passes a wrapper whose vendor payload is broken, seen live — and reports llm_health.headlessCliBinaries; a bash-backed lane whose binary is unreachable is skipped by the scheduler and refused by explicit fires (tokens preserved, preset locks released) instead of flapping through exit-127 → error → RestartBackoff, and the servable verdict returns a new stranded reason CLI_BINARY_MISSING naming the actual repair. (2) spawn_persona execution:"claude-code"|"codex" fails fast against that probe rather than building a persona that could never fire; readiness.capabilities.headlessCliAgents and the youAreTheRuntime guidance now reflect the probe instead of asserting support; scheduler_status marks a scheduled CLI-backed lane with an unreachable binary willNotFireUnattended. (3) The desktop launcher appends ~/.local/bin, /opt/homebrew/bin and /usr/local/bin to its children's PATH — a tray-launched app inherits launchd's minimal PATH, so master could not see the claude that works in every terminal, which would have made the flagship backend fail with exit 127 on the flagship platform.
• A bash-mode persona without tier config no longer inherits the API provider's model name (agentic-net-master — AgentSessionService). With a provider configured (say Ollama) and llmMode:"bash", the tier resolver's fallback handed the provider's default model to the CLI — claude --model <ollama-model> fails. The CLI now receives a model only when the inscription explicitly names a tier or model; otherwise it uses its own default.

---

AgenticNetOS Desktop Lite

The fast local creator/operator profile: node, deterministic master, gateway,
executor, encrypted local credential vault (no OpenBao), MCP endpoint, and
Studio — supervised by a tray app on bundled Java/Node runtimes. No Docker,
host Java/Node installation, API key, or server-side LLM is required. Connect
an MCP client and let its model build, schedule, inspect, and execute nets.
This loopback-only profile is not the recommended production deployment.

macOS: open the .dmg, accept the license, drag AgenticNetOS to Applications.
First launch of this unsigned build: right-click the app and choose "Open", or allow
it under System Settings → Privacy & Security → "Open Anyway". Verify the download
against SHA256SUMS.txt first.

Linux (Debian/Ubuntu): sudo apt install ./AgenticNetOS-<version>-linux-<arch>.deb,
then run /opt/agenticnetos/bin/AgenticNetOS. An
.rpm is provided for Fedora/RHEL. On servers without a desktop the app runs headless;
the tray is optional.

Windows: run AgenticNetOS-<version>-windows-x64.msi (unsigned; SmartScreen may
warn on first run). Upgrades install over the old version in place; the upgrade path
is CI-tested against the previous published release. Data in ~/.agenticos is never
touched by the installer, including by a failed one.

Build it yourself: agentic-net-desktop/scripts/build.sh (or build-windows.ps1)
in the repository bundles an installer for your machine from this release's
standalone binaries (agentic-net-node-*.jar, agentic-net-master-*.jar,
agentic-net-gui-*.zip below — EULA applies), no Docker needed.

Connect an MCP client: the tray copies a ready Codex config.toml block,
Claude Code command, or generic MCP URL + bearer token. Studio: tray menu →
"Open Studio" signs you in automatically (a single-use link exchanges the admin
secret server-side; it never reaches the browser).
Server-run AI lanes can be enabled later, but fresh installs use
llm.provider=disabled, so new AI lanes default to MCP external fires and need
no server model.

Data lives in ~/.agenticos/ and survives updates. The bundled node, master and
gui binaries are covered by the EULA shown at install (also in the app dir);
everything else is BSL 1.1.