Skip to content

Stage explicit public inputs for isolated agents - #105

Closed
dmorosanu wants to merge 2 commits into
feat/agent-grader-isolationfrom
feat/agent-public-input-bundle
Closed

Stage explicit public inputs for isolated agents#105
dmorosanu wants to merge 2 commits into
feat/agent-grader-isolationfrom
feat/agent-public-input-bundle

Conversation

@dmorosanu

Copy link
Copy Markdown
Contributor

Summary

  • Add sandbox.docker.agent_input_patterns as an explicit public-file allowlist.
  • Stage matching plugin and template files into a temporary public bundle instead of mounting their source directories.
  • Rewrite agent-visible plugin and template paths to the staged bundle and leave original sources host-only.
  • Document the end-to-end isolation architecture, lifecycle, and boundary between public inputs and private grading data.

Why

Sanitizing the task alone was not enough: mounting whole plugin or template roots could still reveal evaluation files stored beside the agent-visible assets. This change gives each test an intentionally small, declared public input set.

Validation

  • Ruff and whitespace checks passed.
  • Podman probes verified that allowlisted public files are available while adjacent private files are absent.
  • Two unchanged skills tasks completed end-to-end in Podman using their original turn limits: Automation Discovery intake and UiPath Tasks negative guards.

Stacked on

This draft is intentionally based on the agent/grader isolation branch so it can be reviewed as the second, narrower boundary-tightening step.

@dmorosanu

Copy link
Copy Markdown
Contributor Author

Parking with #104: superseded by the container UID/GID isolation in #87. Branch stays parked for potential later reuse.

@dmorosanu dmorosanu closed this Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant