Repository navigation
Open
Description
move the openshell agent runtime to OpenShell 0.1.2 and expand the scope through a stack of focused PRs, without blocking parallel streams.
M1: the OpenShell runtime works correctly on 0.1.2 (unblocks the Claude Code hooks on OpenShell) — done in #157 (PR 1 and PR 2 combined so the examples work at every merge)
- PR 1: Upgrade to OpenShell 0.1.2 (pin, exec by name and workspace, new logs request fields)
- PR 2: Evidence correct on 0.1.2 (0.1 event formats, process evidence from network callers, log sync barrier, policy-generation interruptions)
- Exit check: scripted agent plus the full weather and document_assistant suites on a 0.1.2 gateway (results in Move to stable Openshell 0.1.x version #157)
M2: hardening and different modes (parallel, order flexible)
- Drop community-image expansion (Move to stable Openshell 0.1.x version #157); images rebuilt with the session SDK (Update suites to use agent runtimes #139)
- Move the example images off the retired OpenShell-Community pi base
- Snapshot integrity (no login shell, content hashes)
- Four-outcome grading with Inconclusive; reachability exposure labels
- Unrecognized OCSF lines make an evaluation Inconclusive; switch to structured OCSF once feat(observability): include the structured OCSF event in sandbox log lines served by the gateway API NVIDIA/OpenShell#4080 lands
- Session token as an OpenShell provider credential; append-only in-sandbox callbacks
- L7 predicates; readiness failure reasons
- Confine SDK internals to
private_api.py - Policy as YAML file; suite linting
- Wait for policy-generation settle before launching the agent
- Service agents in a sandbox with fake MCP interception
- Middleware interception and canaries
- Policy self-escalation and credential-placeholder theft scenarios
reference:
Metadata
Metadata
Assignees
Labels
No labels
Activity
docs: record M1 as done and align the plan with #154