The validated configuration
The most recent live-validated configuration is the one recorded forv0.1.0-beta:
Sage
v0.2.0 passed its offline suite, repository-boundary guards, and scripted tests of the
assembled chat path, but the clean-clone Docker qualification and live-range runs were not
repeated for it. The table above is therefore the latest live-validated configuration, not a
validation of v0.2.0. The release notes record what changed since.
What is not validated
Other operating systems and architectures; other Mythic, Apollo, BloodHound CE, or BloodHound MCP revisions; other model providers, direct-provider routes, and models; and payload types other than Apollo are not validated for this beta. Sage has code paths for several of them (four model providers, a generic payload adapter), and those code paths are not evidence that the configuration works.Known limits
- Auto mode is experimental. It has been exercised against the GOAD lab only. That does not establish reliability or generalization on another range or on a production network.
- Assisted operation memory is narrowly proven. The acceptance case covers one shape of
finding: credential material in a downloaded file from a completed Apollo
downloadtask. It does not show that a consultant would have missed the finding, acted on it, or gained value from it. - Erasure is per owner. An operation-memory wipe removes Sage-derived state for one operation and leaves Mythic records, LangGraph checkpoints, Phoenix traces, provider retention, and Slack records to their own retention policies. See Runtime state and resets.
- Slack delivery is a notice, not a finding. When configured, Slack receives only a generic change notice; review the finding inside Mythic. See Background findings watcher.
- Restarts drop conversational scope. After a Sage restart, supervised chat does not restore prior scope and evidence. The engagement ledger survives; restate scope in a fresh channel.
- macOS Docker Desktop and OrbStack need a database override. See SQLite on macOS.