Add Mitos to Runtimes, Harnesses & Reference Implementations - #49
Open
stubbi wants to merge 1 commit into
Open
Conversation
Mitos is a snapshot-fork microVM sandbox runtime for AI agents: it forks a warm environment per session so each run starts from a clean, isolated state. That maps directly onto two harness primitives the list already covers: per-session clean state and isolated parallel execution. Placed next to SWE-ReX as sandboxed execution infrastructure. Signed-off-by: Jannes Stubbemann <jannes@mitos.run>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Mitos to the Runtimes, Harnesses & Reference Implementations section, next to SWE-ReX as sandboxed execution infrastructure.
Harness angle: Mitos is a snapshot-fork microVM sandbox runtime for AI agents. It forks a warm environment per session so each run starts from a clean, isolated state, with declarative lifecycle control and a client SDK. That maps onto two harness primitives this list already covers: per-session clean state and isolated parallel execution.
Checklist