AstraBox 0.1.14 was released on 2026-11-06. colton-z/astrabox is an open-source self-hosting alternative to Claude Managed Agents, a project that runs Claude Code, Codex, Hermes, DeepSeek Harness, and Pi as managed agents on your own infrastructure. The focus of this version is the Satori integration. A Satori v1 HTTP and WebSocket endpoint `/api/satori/agents/{agent_id}/v1` was added, so external chat apps can call up an agent and converse with it. The commit touched 30 files and 5,201 lines (4,965 added, 236 deleted).
A channel is a conversation owned by the caller, and a deployment-side identity resolver verifies the caller's identity. A reconnected client can resume receiving events from the shared database on any replica. Attachment transmission came in as well. Satori callers send images and files with the standard `upload.create` and resource elements, and they can also be received in channel messages that carry a built-in Satori adapter such as Discord. Images go in as the engine's image input, and files are stored under `uploads/` in the conversation workspace, limited to at most 10 per message and 25 MiB each.
The release also includes four defects that surfaced in the release tests. The way the Satori event connection locked the feed row with an upsert in its own write transaction every 250 milliseconds, lining up on database locks, was changed to processing the feed once per process. The problem whereby another program occupying the Hermes bridge port would consume the full 300-second startup budget and leave the reason for the failure only in the server log is now reported as a recovery requirement that shows the received HTTP status and what to do about it. The lock that made message transmission wait up to 5 minutes during a runtime attach was narrowed in scope to the judgment and result posting, and the problem of Hermes deleting the profile file during storage and thereby failing to save state (the case where WAL SQLite deletes it after a checkpoint) is also gone. For a conversation whose owner of model credential delivery changed, the replacement runtime takes over the native conversation, preserving the messages waiting in the queue, and the previous response is recorded as a `MODEL_DELIVERY_CHANGED` failure. In the conversation list and header, the Agent name appears next to the title and links to the Agent page.
That said, there are prerequisites ahead of the upgrade. The server image and the Assistant (Hermes) sandbox image must be rolled out together, while the other sandbox runtime images stay at 0.1.13. External persistence providers must apply the Satori event location and the staged input / channel message attachment schema themselves. The Satori endpoint relies on a `WebIdentityResolver` that validates delegated execution identity, and it explicitly states that the built-in single-user resolver must not be exposed to untrusted callers. There are no performance figures or scale comparisons in the release notes, so it is still too early to gauge the extent of the improvement. It is close to an environment for running several coding agents as managed agents on your own infrastructure and connecting them to external chat apps, but to widen it into multi-user operation, the identity resolver configuration must come first.