Skip to content

Add SandBase Harness - #46

Open
liyangbing wants to merge 2 commits into
bradvin:mainfrom
liyangbing:add-sandbase-harness
Open

liyangbing wants to merge 2 commits into
bradvin:mainfrom
liyangbing:add-sandbase-harness

Conversation

@liyangbing

Copy link
Copy Markdown

Summary

  • add SandBase Harness to Compute & Sandboxes
  • document its local-first runtime, MCP governance, sessions, audit/replay, and deployment backends

Verification

Disclosure: this PR was submitted by a SandBase Harness maintainer. Isolation wording is explicitly dependent on the selected backend.

@github-actions

Copy link
Copy Markdown
Contributor

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '6cf84c70a4b3a1d6977e5933513e9cfa3949eb00'
git worktree add --detach '../agentfirst-base-46' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-46' --submitted-by 'liyangbing' --slug 'sandbase-harness'
npm run enrich:tool-assets -- --write --slug 'sandbase-harness'
git worktree remove '../agentfirst-base-46'

Then commit the updated files to this PR branch.

@liyangbing

Copy link
Copy Markdown
Author

Updated the fork branch with the requested generated metadata: tool-submitters.json, logoUrl, and ogImageUrl. The Enrich Tool Assets check now passes; local content tests and required-submitters validation also pass. Ready for maintainer review.

@liyangbing

Copy link
Copy Markdown
Author

Rechecked the repository-maintained metadata instructions on the current PR branch.

  • sync:tool-submitters --base-root-dir ... --submitted-by liyangbing --slug sandbase-harness completed with metadataChanged=0.
  • enrich:tool-assets --write --slug sandbase-harness completed with logoUrl and ogImageUrl already present and changed=0.
  • The branch already contains commit cf412e0 (Auto-fill tool media and submitter metadata), with tool-submitters.json mapping sandbase-harness to liyangbing and the tool page containing both media URLs.

No additional generated diff is required, and git diff --check passes.

@bradvin

bradvin commented Aug 31, 2026

Copy link
Copy Markdown
Owner

@liyangbing pls change classification from agent-enabling to agent-native.

The current policy defines agent-native for products where agents are a core runtime or entity. SandBase Harness is explicitly an AI agent runtime: users create/import agents, attach tools and memory, start persistent agent sessions, and inspect their execution. That matches agent-native directly. agent-enabling is used for supporting infrastructure such as generic sandboxes, testing, or memory services.

Evidence: SandBase repository and usage guide.

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.

2 participants