docs: bound SafeMini execution claims - #5
Merged
JustinJLeopard merged 1 commit intoAug 10, 2026
Conversation
Describe host-process policy guards and in-memory transcripts accurately. Preserve the distinction between explicit executor isolation and the built-in runner. Co-Authored-By: Codex <noreply@openai.com>
JustinJLeopard
deleted the
desktop-codex/docs/safe-mini-execution-claims
branch
August 10, 2026 13:55
There was a problem hiding this comment.
Pull request overview
This PR tightens and corrects SafeMini’s documentation and public metadata to match the actual execution/isolation boundary: built-in executors run in the host process context with policy guards, while isolation is only guaranteed when an injected executor boundary is used.
Changes:
- Updated type/protocol docstrings to describe
RunResultas carrying an in-memory transcript (not a persisted trajectory/audit artifact). - Revised README claims to remove standalone sandbox/incident/ledger assertions and clarify the supported isolation boundary.
- Adjusted package description/keywords in
pyproject.tomlto match the bounded, policy-guarded execution model.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| safe_mini/types.py | Updates RunResult docstring to reflect in-memory transcript semantics. |
| safe_mini/protocol.py | Reframes AgentRunner contract language from “sandboxed” to “policy-guarded” and aligns return expectations with transcript-based results. |
| safe_mini/policies/executor.py | Narrows SafeExecutor docstring to “restrictive policy” wording consistent with host-context execution. |
| README.md | Removes/clarifies overstated isolation and artifact claims; documents injected-executor boundary as the isolation guarantee. |
| pyproject.toml | Aligns package description/keywords with bounded local execution + policy guards. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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.
Summary
Align source documentation and package metadata with the actual executor boundary.
Validation
Non-goals
No executor behavior, runtime activation, package release, tag, or publication change.