sandbase-harness/docs/promotion.md

Promotion status

Last checked: 2026-08-31

The latest official Discussion #116 promotion checkpoint records the new Awesome Harness Engineering PR #226, which proposes a source-backed Security, Sandbox & Permissions reference and is open/mergeable with maintainer review pending (verification). The weekly mcp-catalog PR #2 also lists SandBase Harness as a discovery candidate; its maintainer review and final categorization remain pending (verification). New review requests are open at MCP-SecurityTools #5, Awesome Agent Harness #30, and Awesome Agent Sandbox #3, with source verification supplied and maintainer decisions pending (MCP-SecurityTools verification, Agent Harness verification, Agent Sandbox verification). The new awesome-agent-runtimes PR #2 proposes a source-backed entry in a dedicated Agent Runtime comparison, with backend-dependent isolation explicitly stated (verification). A new awesome-ai-agents-2026 PR #542 proposes a factual SandBase Harness entry under Self-Hosted Agents and UIs, with the target's requested pricing and dynamic-stars fields; maintainer review is pending (verification). The new Awesome DeepSeek Agent PR #412 adds bilingual installation/configuration/first-run guides for using SandBase Harness with DeepSeek Harness; maintainer review is pending (verification). The duplicate awesome_ai_agents PR #469 is closed in favor of the canonical PR #467. It is a factual discovery update; no ranking, endorsement, security certification, or social publication is claimed.

The canonical Awesome Agent OS PR #3 remains open and mergeable; older duplicate PR #2 was closed to leave one review path. The directory workflow still requires maintainer approval for the external check, so no inclusion or endorsement is claimed.

The Hugging Face agent-harness registry PR #2432 is now merged at 56e5168, and the public main source includes the SandBase Harness entry. The integration is backed by SandBase's default AI_AGENT=sandbase-harness child-process marker across local, Docker, Kubernetes, and self-hosted worker paths, with explicit nested-agent markers preserved (implementation, maintainer confirmation). This is an attribution integration, not an endorsement or security certification; isolation remains backend/deployment dependent.

The corresponding official Discussion #116 merge announcement records the public registry merge and links the implementation and attribution-only boundary. X, LinkedIn, and Discord remain review-ready drafts; no social account publication is claimed.

The new DSH Plugin Market metadata issue #1839 generated PR #1847 for the SandBase Harness metadata entry. Its validate-submission check passes; the maintainer verification links v0.3.8, Apache-2.0/self-hosted distribution, the GHCR MCP bridge, and backend-dependent isolation. The PR remains open and publication is maintainer-controlled; no endorsement or security certification is claimed (verification).

The canonical Picrew Awesome Agent Harness PR #86 remains open and mergeable after a current v0.3.8 source-verification follow-up. Conflicting duplicate PR #85 was closed to leave one maintainer-review path; the catalog entry remains pending and is not an endorsement or security certification.

The new gVisor DeepSeek Harness integration guide PR #14517 documents an explicit Docker → runsc → gVisor execution path for selected Harness commands. A maintainer-facing follow-up links SandBase Harness as a complementary Harness-side reference for governed sessions, MCP admission/approvals, credential scoping, audit/replay, and selectable backends. The note explicitly does not claim that SandBase replaces gVisor or provides universal kernel isolation; the PR remains open and maintainer review is pending.

The new Awesome-LLMSecOps PR #66 adds one source-linked SandBase Harness entry under Agentic security. The description is limited to documented sandboxed tools, credential boundaries, policy controls, audit logs, event replay, and the MCP bridge; it explicitly says isolation and security posture depend on deployment/backend selection and makes no certification or endorsement claim. GitHub reports the PR as open, clean, and mergeable with no automated checks reported; maintainer review is pending. The verification note is here. The review-gated channel drafts were recorded in merged Daily Ops PR #284, and the status is summarized in Discussion #116.

The new Awesome Agent Runtime Security PR #30 adds one source-linked SandBase Harness entry under Sandboxing & Isolation. The entry describes the runtime's sandboxed tools, credential boundaries, policy controls, persistent sessions, audit/replay, and MCP bridge without claiming universal microVM or kernel isolation; deployment/backend dependence is explicit. GitHub reports the PR as open, clean, and mergeable with no automated checks reported; maintainer review is pending. The verification note records the source boundary.

The new Awesome LLM Security PR #313 adds one source-linked SandBase Harness line under Tools. The description is limited to runtime governance, sandboxed tools, credential scoping, approvals, audit/replay, and the MCP bridge; it explicitly avoids presenting SandBase as a vulnerability scanner and retains the deployment/backend-dependent isolation boundary. GitHub reports the PR as open, clean, and mergeable with no automated checks reported; maintainer review is pending. The verification note records the scope.

The new Jenqyang Awesome AI Agents PR #460 adds one neutral, source-linked SandBase Harness line under Applications → Tools. It follows the destination's standard OSS and maintainability requirements, contains no pricing or hosted-upsell language, and describes only independently self-hostable runtime capabilities. GitHub reports the PR as open, clean, and mergeable with no automated checks reported; maintainer review is pending. The verification note records the scope and deployment qualification.

The existing Slava Awesome AI Agents PR #403 adds a SandBase Harness entry to a 2,195-star AI-agent directory. GitHub reports it open, clean, and mergeable; maintainer review is pending. A verification follow-up links the current installation guide, v0.3.8 release, MCP Registry entry, and deployment-dependent isolation boundary. This follow-up advances the existing PR and does not create a duplicate contribution.

The existing E2B Awesome AI SDKs PR #344 is the canonical Harness entry for E2B's SDK/framework/tool directory; it is mergeable and has a source-linked description of the runtime/MCP bridge. A maintainer verification follow-up records the current project sources and the backend-dependent boundary; the remaining CLA check requires contributor action, so no merge or directory endorsement is claimed. The merged Daily Ops PR #275 queues this review path in the X, LinkedIn, and Discord drafts, which remain NEEDS REVIEW.

The new Awesome AI Agents 2026 PR #240 adds the current SandBase Harness runtime beside the existing, separate SandBase CLI entry under Agent Tooling and Infrastructure. It follows the destination's required tier/language/type format and keeps the backend-dependent isolation boundary explicit; maintainer review is pending and no endorsement or security certification is claimed. The latest link-check job fails only on the destination's pre-existing ofekron/better-agent 404 outside this PR's diff; the follow-up records the finding. The initial and link-check follow-up drafts are recorded in merged Daily Ops PR #274 and PR #283, which remain NEEDS REVIEW.

The new E2B Awesome AI Agents Issue #1468 asks the high-traffic directory to evaluate SandBase Harness as a distinct runtime entry from the closed SandBase CLI PR #1457. A source-backed follow-up comment clarifies the separate repositories, self-hostable value, current runtime capabilities, and backend-dependent isolation. A direct PR #1473 now carries the factual entry in the directory's requested format; it is open and mergeable, but the required CLA check remains failed until the contributor signs the agreement. The request explicitly leaves scope and inclusion to the maintainer; no listing, endorsement, or security certification is claimed. The merged Daily Ops PR #273 queues this scope-review path in the X, LinkedIn, and Discord drafts, which remain NEEDS REVIEW.

The new NipunaRanasinghe Awesome AI Agents PR #184 adds SandBase Harness to Core Frameworks using the destination's dynamic GitHub stars badge and concise table format. The directory is actively maintained with CI and accepts maintained AI-agent resources; review is pending and no directory endorsement or security certification is claimed. The merged Daily Ops PR #272 queues this review path in the X, LinkedIn, and Discord drafts, which remain NEEDS REVIEW.

The new Zients Awesome Agent Harness PR #10 adds SandBase Harness to Agent Systems & Harnesses. The entry follows the destination's contribution rules, links the official installation path, and states model-provider requirements plus backend/deployment-dependent isolation. GitHub review is pending; no directory endorsement or security certification is claimed. The merged Daily Ops PR #271 queues this review path in the X, LinkedIn, and Discord drafts, which remain NEEDS REVIEW.

The canonical Awesome Agent Harnesses PR #2 remains open and mergeable, adding SandBase Harness to Platforms & Frameworks with a factual one-line description and current star count. A duplicate PR #3 was closed to avoid duplicate maintainer work. The merged Daily Ops PR #270 queues this review path in the X, LinkedIn, and Discord drafts; they remain NEEDS REVIEW, with no social-account publication, directory endorsement, or security certification claimed.

The new Awesome MCP DevTools PR #13 adds SandBase Harness to Proxies and Gateways. The one-line entry describes the local-first, self-hosted runtime and MCP bridge with sandboxed sessions, memory, credentials, audit/replay, and the local Console; GitHub reports it mergeable with no reported checks, and maintainer review is pending. The verification comment supplies current v0.3.8 and installation/MCP sources.

The new Awesome MCP Collection PR #39 adds SandBase Harness to Development & Version Control. The entry follows the directory's table format and records the TypeScript/Apache-2.0 project, MCP bridge, sandboxed sessions, credentials, approvals, audit, and replay; maintainer review is pending and no directory endorsement or security certification is claimed.

The verification follow-up for PR #39 links v0.3.8, the installation/MCP guide, and the deployment-dependent isolation boundary so the maintainer can review the entry against primary sources.

The merged Daily Ops PR #264 (87f15bee0bcee622b3020fc73dcb54513f9cf405) queues Awesome MCP Collection PR #39 in the Discord, LinkedIn, and X drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The new Awesome MCP Issue #99 requests SandBase Harness for the directory's Aggregators & Gateways section. A normal PR was not possible because the existing personal fork has no comparable upstream history; the public issue workflow was used instead. The request contains one factual entry and remains pending maintainer review; no directory endorsement or security certification is claimed.

The canonical Awesome MCP Gateways PR #77 adds SandBase Harness to Open-source MCP Gateways. The entry meets the directory's stated 200-star/2-contributor threshold; GitHub reports the PR MERGEABLE, with its verification/cla-signed check awaiting a conclusion. Maintainer review is pending and no directory endorsement or security certification is claimed. A later duplicate PR #81 was closed and is not part of the promotion queue.

The new Awesome AI Harness PR #4 adds SandBase Harness to the SDKs & runtimes section. Its one-line entry explains the runtime design surface—session state, governed MCP tools, approvals, credential scoping, audit/replay, and selectable deployment backends—rather than making a generic marketing claim. GitHub reports it MERGEABLE with no reported checks; maintainer review is pending and no directory endorsement or security certification is claimed.

The verification follow-up for PR #4 links v0.3.8, the installation guide, and the harness-design rationale while reiterating that isolation is provider/configuration dependent.

The new Awesome AI Coding Sandboxes PR #15 adds SandBase Harness to the directory's Adjacent section for related runtime/orchestration projects. The entry explicitly says isolation depends on the provider and does not present SandBase as a standalone isolation engine; GitHub reports the README-only PR MERGEABLE with no reported checks, and maintainer review is pending.

The verification follow-up for PR #15 links v0.3.8, the installation guide, and sandbox-backend documentation, and explains why no unsupported isolation, egress, or secret-brokering claims were added to the comparison matrix.

The merged Daily Ops PR #269 (58d8222c9808c2b13932bce18fd8fe971ffa1209) queues Awesome AI Coding Sandboxes PR #15 in the Discord, LinkedIn, and X drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #268 (9ed30afcb5b47e40b49591495aceb1d52dcd2b02) queues Awesome AI Harness PR #4 in the Discord, LinkedIn, and X drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #266 (1e2cdf09535dfc1dd1c9dc17d0d76518c7d8042d) originally queued the duplicate reference. The merged correction PR #267 (1a9258334ab3fcd9cf8d6b925a2c5842cc476def) now points the Discord, LinkedIn, and X drafts to canonical PR #77. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #265 (4d8e05241836f90e419f674923537166afa0ce16) queues Awesome MCP issue #99 in the Discord, LinkedIn, and X drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

Repository discoverability metadata was refreshed on 2026-08-31: the GitHub description now explicitly identifies SandBase Harness as a self-hosted AI agent runtime and MCP bridge. The existing release homepage and 20 relevant GitHub topics were retained.

The published v0.3.8 release notes were also refreshed with the newly verified merged directory entries, the public MCPVault auto-indexed listing, the still-pending HabitoAI/mcpdir review links, and current Hugging Face, Agent Switchboard, and MeshKore review submissions.

This is an operational handoff for maintainers. The repository, release tags, and official MCP Registry remain the source of truth; independent directories do not imply endorsement or security review.

Latest follow-up: Open Source Radar issue #7 remains open with no maintainer reply after the factual evidence update. Docker MCP Registry PR #4841 is the canonical submission; duplicate PR #4838 was closed and its maintainer note records both the repository validator and the v0.3.8 MCP initialize handshake.

The MCP Registry publish workflow was re-run after the metadata description update: image verification, metadata validation, and GitHub OIDC authentication passed, but the Registry rejected the publish because version 0.3.8 already exists (cannot publish duplicate version). The improved server.json will be published with the next genuine release; no artificial version was created (initial validation run, duplicate-version run).

MCP.Directory's submission endpoint reports that this repository has already been submitted; no public detail page is available yet, so it remains review- controlled rather than verified discovery.

The latest public handoff is recorded in Discussion #82.

The latest promotion checkpoint is also summarized in Discussion #94, including the canonical Docker and ToolSDK registry review paths and the TensorBlock metadata gate.

The current official DevOps-focused discovery post is Discussion #116, linking the installation guide, v0.3.8 release, MCP Registry review, and the two DevOps catalog reviews. Its follow-up comment adds the pinned GHCR quick start, current six-tool scope, and security-boundary reminder.

The latest Discussion #116 promotion update records MeshKore submission #14 and explicitly notes that it is directory-only with connect_to_mesh=false; no public profile is claimed before review.

The new Supersynergy/awesome-ai-agents-2026 PR #16 adds SandBase Harness to the agent runtimes and platforms table. The one-line entry uses the project's public local-first/self-hosted runtime description and names session isolation, memory, credentials, audit/replay, and the local Console; maintainer review is pending.

The new NEXUS Algo Awesome AI Agent Engineering PR #1 adds SandBase Harness to the deployment list. The entry is one factual line linking the official repository and describing the documented local-first/self-hosted runtime, MCP tools, sandboxed sessions, memory, approvals, audit, and replay; maintainer review is pending.

The Agentic AI Foundation project proposal was evaluated as a potential high-impact channel but not submitted: its form requests a Contribution Agreement, project governance/adoption evidence, and consent to transfer project trademarks and accounts if accepted. That is a foundation-hosting/legal commitment rather than a routine directory listing and requires an explicit project-owner decision.

The new MyMCPTools issue #8 proposes the published SandBase Harness MCP bridge for the directory. It includes the v0.3.8 release, official installation/MCP documentation, and the pinned GHCR command; the issue is pending maintainer review and makes no claim of a public listing, score, or endorsement.

The mcp.so/mcpso submission thread now contains a direct SandBase Harness listing request through the directory's documented GitHub Issue workflow. It links v0.3.8, the official installation and MCP guides, and the pinned GHCR bridge command; directory publication and review remain pending, with no endorsement or security certification claimed.

The new Collective AI Tools Issue #332 submits SandBase Harness separately from the existing SandBase CLI Issue #323. It follows the directory's contribution template, links v0.3.8 and the official installation/MCP documentation, and records the backend-dependent isolation boundary; directory review and publication remain pending.

The new Awesome Agent Skills PR #79 adds SandBase Harness to the directory's MCP runtime and infrastructure section. It links the official repository and describes the local-first/self-hosted runtime using public project facts; maintainer review is pending and no directory endorsement or security certification is claimed.

The new Awesome MCP List PR #409 adds SandBase Harness to its AI Agents & Frameworks section. GitHub currently reports the focused one-line PR as MERGEABLE with no reported checks; maintainer review is pending and the entry is not an endorsement or security certification.

The new Awesome Agent Runtimes PR #4 proposes SandBase Harness for that project's watchlist, not its active core catalog. The change records current GitHub metadata, the 180-day review date, and the project's explicit 5,000-star/180-day maturity limits; repository checks passed with scripts/update.py --check, and maintainer review is pending. A maintainer verification comment adds current v0.3.8 release, installation, MCP, and API evidence while preserving the watchlist boundary.

The new Awesome Agent Sandbox PR #2 adds SandBase Harness to Related Projects, where the directory places agent frameworks that bundle sandbox execution. The entry uses the requested neutral run-mode/backer badges and explicitly states that isolation depends on deployment; GitHub reports it CLEAN/MERGEABLE, with Sourcery approval and successful GitGuardian checks. A maintainer handoff records that the current account cannot merge the third-party PR; it is approved and awaits target-maintainer merge.

The new Awesome Agent Infra PR #6 adds SandBase Harness to the Runtime and Control Plane table. It follows the directory's infrastructure-focused format and links the public runtime capabilities and deployment-dependent boundary; maintainer review is pending.

The new Awesome CLI Coding Agents PR #314 adds SandBase Harness to a dedicated Runtime & execution backends section. The entry covers the MCP bridge, governed sessions, and selectable backends while preserving the deployment-dependent isolation qualification; GitHub reports it mergeable with no failed checks, and maintainer review is pending.

The new Awesome AI Developer Stack PR #2 adds SandBase Harness to the MCP Servers table. It follows the directory's repository/language/description format and uses the current public project facts; maintainer review is pending and no directory endorsement or security certification is claimed.

The new Awesome Agent Cortex PR #74 adds SandBase Harness to Agent Runtime Infrastructure. The repository's alphabetical-section and internal-link checks passed, and the PR uses a concise infrastructure description with the deployment-dependent qualification; maintainer review is pending.

The Awesome Agentic AI 中文 Stage 7 PR #228 is the conflict-free maintainer integration that superseded PR #213. It merged at 1cb0406, adds the trilingual Track B Harness／Sandbox／Deploy resource, and reports 1,036 script tests, 31 targeted Stage 7 tests, mirror/locale/docs/build checks, and an independent code-reviewer approval. The entry preserves the backend- and deployment-dependent isolation boundary and is a directory resource, not an endorsement or security certification.

The new Awesome Terminal Agents PR #5 adds SandBase Harness to the terminal-agent survey's Harnesses/Runtimes section as an Engineering-Practice-Tool. It links the primary repository and MCP documentation and keeps the entry separate from controlled empirical evidence; maintainer review is pending.

The new Awesome Agent Infrastructure PR #23 adds SandBase Harness to Execution Sandboxes. It follows the destination's entries.yaml format, links the official installation guide, and describes the runtime, MCP bridge, approvals, audit/replay, and selectable execution backends with an explicit backend/deployment-dependent isolation qualification. The PR changes only entries.yaml, is mergeable with no reported checks, and awaits maintainer review; no directory endorsement or security certification is claimed.

An additional verification comment now supplies the v0.3.8 release, installation, sandbox-backend, and API links and reiterates that SandBase is not a standalone microVM engine. The PR remains open for maintainer review.

The new Awesome Agent Sandboxing PR #2 adds SandBase Harness to Self-hosted Agent Runtimes. It follows the destination's one-sentence format and describes the MCP/tool-governance, sessions, approvals, audit/replay, and backend-dependent isolation model without making a universal security-boundary claim. The README-only PR is mergeable with no reported checks and awaits maintainer review; no directory endorsement or security certification is claimed.

An additional verification comment now supplies the v0.3.8 release, installation, backend, and API links, and reiterates that local path isolation and Docker/Kubernetes/worker properties depend on deployment. The PR remains open for maintainer review.

The new Awesome Sandbox PR #27 adds a dedicated SandBase Harness case study to the guide's sandbox-platform section and updates its table of contents. The section links the official installation/backend documentation and describes the self-hosted runtime, persistent sessions, MCP/tool governance, audit/replay, and selectable providers, explicitly distinguishing backend-dependent isolation from microVM/kernel isolation. GitHub reports the README-only PR as MERGEABLE; its GitGuardian check is in progress and maintainer review is pending. No directory endorsement or security certification is claimed.

The new AI Agent Sandboxes PR #3 adds SandBase Harness to an evidence-carrying YAML dataset. It registers official repository, installation, sandbox-backend, and API sources; records the runtime's persistent sessions, MCP/tool governance, approvals, audit/replay, and selectable backends; and explicitly classifies local path isolation and backend-dependent limits without claiming hostile-code protection or universal microVM isolation. The contributor validated the YAML with PyYAML and updated the dataset version to 0.2.7; GitHub reports the PR as MERGEABLE with no reported checks and maintainer review pending.

An additional verification comment now links the v0.3.8 release, installation, sandbox-backend, and API documentation. It also explains the dataset's coarse container facet and repeats the local/provider-specific isolation limitations; the PR remains open for maintainer review.

The merged Daily Ops PR #262 (87a7ca4c63f3104b005ba1d54b3c07f1803b916f) adds AI Agent Sandboxes PR #3 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #263 (19c50e76a2ffa60fbe85529510a6d8c6a81fc0f8) adds Awesome AI Coding Tools PR #665 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

After its GitGuardian check passed, a maintainer-facing verification comment added the official installation, sandbox-backend, and v0.3.8 release links and reiterated the backend-dependent isolation boundary. The PR remains open for destination-maintainer review.

The merged Daily Ops PR #261 (f45f7535ded89266e3440c045b487fe23e27fa10) adds Awesome Sandbox PR #27 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The new Awesome Agent Sandbox PR #2 adds SandBase Harness to the Self-hosted / Open Source sandbox table. It uses the directory's existing concise table format and identifies the MCP governance, persistent sessions, approvals, audit/replay, and selectable sandbox backends; maintainer review is pending and no directory endorsement or security certification is claimed.

The merged Daily Ops PR #260 (08747ec3f4e66e7ceefe3ce1c0ac73acda1b1ff9) adds Awesome Agent Sandbox PR #2 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #259 (ecc6f3e713f55e9a1123bcaf995eb5ac5ca2cf59) adds Awesome Agent Sandboxing PR #2 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The new Awesome Agent Sandboxes PR #9 adds SandBase Harness to the Containers section. The one-line entry describes the MCP/governance and audit surface plus Local, Docker, Kubernetes, and worker backends, explicitly qualifying isolation as backend/deployment dependent. The verification comment confirms v0.3.8 and current source links. The README-only PR is mergeable with no reported checks and awaits maintainer review; no directory endorsement or security certification is claimed.

The new Awesome Agent Sandbox PR #4 adds SandBase Harness to Container Sandboxes and its comparison table. It follows the directory's requested repo-link, isolation-model, feature, and supported-agent format, while stating that isolation depends on the selected backend and deployment configuration. The README-only PR is mergeable with no reported checks and awaits maintainer review; no directory endorsement or security certification is claimed.

The new Awesome Agent Sandboxes PR #59 adds SandBase Harness to a structured sandbox landscape. Its data/sandboxes.yaml entry records the runtime's session/tool-governance surface, Local/Docker/Kubernetes/worker backends, and explicit local/deployment isolation limitations; README, JSON, reference, and chart outputs were regenerated by the repository's validator. GitHub reports the PR as MERGEABLE with no reported checks; maintainer review is pending and no directory endorsement or security certification is claimed.

The merged Daily Ops PR #258 (89d1a6991811c709463ec6b924717d1a5c7bb678) adds Awesome Agent Sandboxes PR #59 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #257 (77d51bcb9a3e29dce5e899d4d203654bf513fae3) adds Awesome Agent Sandbox PR #4 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #256 (c08f7bac0344893cc120a7b65d5ff0b9daf918a6) adds Awesome Agent Sandboxes PR #9 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #255 (e8fbc90ddb08e696bb346b3da75f8d8dca6c64d9) adds the Awesome Agent Infrastructure PR #23 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #254 (5c5c9d0add640adcaf91cea65c4e8559a84c09d4) adds the latest CLI Coding Agents, Chinese Agentic AI, Terminal Agents, Agent Sandbox, and Agent Cortex review paths to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW and require operator/account authorization; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #247 (d75b84ebede271228a37fdaeb1fbc38c30d9acc4) adds the latest Agentic Community Landscape, Awesome AI Agent Engineering, and MyMCPTools review paths to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW; no social-account publication is claimed. The merge was recorded in Discussion #116.

The merged Daily Ops PR #248 (49d950616232556cf952cadfe9a6b99821ead49a) adds the public MCPVault auto-indexed/unclaimed listing to the X, LinkedIn, and Discord drafts. The copy distinguishes automated discovery signals from maintainer certification; the merge is recorded in Discussion #116. The release-note update is recorded in Discussion #116.

The existing AI Native Landscape project submission #18 was rechecked and given a current v0.3.8 / installation-guide follow-up (comment). It remains an open curator review request under platform-infra / sandboxes-runtimes; no inclusion or ranking is claimed.

The same Discussion now has a promotion checkpoint linking the current MCP, runtime, self-hosted, automation, and agent-service review submissions. It explicitly labels them as pending review rather than endorsements or security certifications.

The Show and tell Discussion #94 follow-up now links the live English and Chinese DeepSeek Harness walkthroughs and invites deployment/install feedback. It keeps the backend-dependent isolation and no-security-certification qualification explicit.

The latest Discussion #116 progress comment adds the Awesome MCP Collection, Cue OS Awesome Agent OS, Awesome AI Coding Sandboxes, and Awesome MCP Servers for DevOps PRs. Each remains pending external maintainer review; no merge, endorsement, or security certification is claimed.

The latest directory-state audit found four additional completed public listings: Awesome Agent Runtime PR #15, Awesome Native Agent Platforms PR #1, awesome-mcp-servers PR #45, and Awesome Coding Agents PR #41. Their merged entries use current repository/source links and retain the backend-dependent isolation qualification where applicable; they are directory listings, not endorsements or security certifications.

The new MCP Find PR #171 submits the official SandBase Harness Docker bridge metadata to the directory's community registry. The entry uses ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8, the Apache-2.0 repository, and a factual devtools description; maintainer disclosure and the backend-dependent isolation qualification are included. It remains pending review because the repository reports a Vercel preview authorization failure; no merge or public listing is claimed. A follow-up verification comment supplies current release, Registry, installation, and MCP handshake evidence. The earlier duplicate PR #168 was closed in favor of #171, so #171 is the sole active MCP Find review path.

The Hugging Face agent-harness registry PR #2432 is merged at 56e5168. Its corrective commit 4407827b removes MANAGED_AGENTS_HOME as an identity signal; the final SandBase marker implementation is d4ae4e0. The PR-specific format, lint, node, and Cursor Bugbot checks pass; unrelated browser/e2e failures and their admin-only rerun boundary are documented in the review thread. This integration is attribution-only, not an endorsement or security certification.

The new MCP-Directory PR #5 adds the SandBase Harness MCP bridge to both the interactive index.html catalog and the README table, using the published GHCR 0.3.8 image and a tested Docker command. GitHub reports the PR as clean and mergeable with no failed checks; external maintainer review and merge remain pending. A verification comment supplies the current release, Registry, installation, image, and deployment-boundary evidence.

The canonical Awesome MCP Servers PR #13240 adds SandBase Harness to the Developer Tools list with the official Docker bridge command and backend-dependent isolation qualification. Its check-submission workflow passed and GitHub reports CLEAN/MERGEABLE; the current account cannot execute the upstream merge, so maintainer/Glama review remains pending. The older duplicate PR #13188 was closed with a pointer to #13240, so future tracking and promotion references use #13240 only.

The PR's follow-up automation now requires a Glama listing and score badge before acceptance. The repository's public Docker image is already introspection-tested, but the one-time Glama Add Server flow requires interactive GitHub OAuth and has not been claimed or completed; this is recorded in the maintainer status comment, with no Glama score claimed.

The Sunrisepeak dsh-index PR #43 updates the indexed SandBase Harness descriptor from v0.3.7 to v0.3.8. Its affected-units, descriptor-contract, site-build, and SandBase boot checks passed at the submitted revision, but GitHub currently reports the PR DIRTY; the status follow-up records that a local rebase against current main was reproduced successfully, while the upstream branch requires maintainer write access to update. The handoff is also recorded in merged Daily Ops PR #423 and official Discussion #116. No index publication is claimed until the PR is updated and merged.

The new HabitoAI Awesome MCP Servers PR #37 adds one factual SandBase Harness entry under Developer Tools, linking the official Apache-2.0 repository, v0.3.8 release, installation guide, and published GHCR bridge image. GitHub reports the PR as CLEAN/MERGEABLE; maintainer review is pending.

For release trust and promotion accuracy, security PR #117 is now merged into main. It updates prefix-safe-json to the published 0.4.3 security release, adds post-terminal authority regression coverage, and passed the targeted typecheck, 11 affected tests, runtime/Console build, package check, and release smoke verification. The full-suite environment limitations documented in the PR remain separate and are not hidden.

An independent security-discovery request is now open at MCPRadar Issue #8. It provides the official Registry/source links and the credential-free Docker handshake command, while explaining that session calls may require a user-owned API URL/key. The request is for manual scanning and leaderboard review only; no score, endorsement, or security result is claimed.

The follow-up promotion progress comment also links the Agent Cortex, Autonomous Ops, Agentic Hardening, Agent Harnesses, and X-Ops review paths, with the same pending-review and deployment-dependent isolation qualifications.

On 2026-08-31, the open Platform/DevOps catalog PRs were given a documentation-link correction pointing to docs/installation.md: Platform Engineering #11, Platform Engineering #63, DevOps Platform #4, DevOps AI #54, and Agentic DevOps MCP #42.

An additional submission to the general DevOps catalog is Awesome DevOps PR #30. It adds a dedicated MCP tool entry with installation, release, and security-boundary links; the DCO check passed and maintainer review is pending. The disclosure comment is here, and a follow-up correction replaces an initially incorrect security-document path with the existing Sandbox Backends section.

Awesome Self-Hosted Agents PR #6 adds SandBase Harness to the self-hosted agent frameworks list. The PR is clean and mergeable; the maintainer disclosure links the v0.3.8 release, installation guide, and backend-dependent sandbox boundary. Review is pending.

Awesome Agent Infra PR #2 adds SandBase Harness to a machine-readable runtime catalog with a pinned GHCR command and MCP/audit output description. Its npm run validate, npm test, npm run lint, and git diff --check checks pass; the maintainer disclosure records the backend-dependent isolation boundary. Review is pending.

Awesome AI Agents PR #1 adds SandBase Harness to the Agent infrastructure category. The PR is focused, clean, and mergeable; the maintainer disclosure links the release, installation guide, and backend-dependent sandbox boundary. Review is pending.

Awesome Agent Operating Systems PR #13 merged SandBase Harness into Agent Runtimes with the requested verification date. The merged entry is publicly present; the superseded PR #11 was closed in favor of #13. The maintainer disclosure preserves the source-backed scope and does not imply a security certification. The status correction is recorded in merged Daily Ops PR #280; no social-account publication is claimed.

Awesome Agent Services PR #8 adds SandBase Harness to Sandboxes & Compute. The PR changes only README.md, is clean and mergeable, and has the maintainer disclosure; review is pending.

Awesome AI Automation PR #3 adds SandBase Harness to AI agents & LLM automation with the repository's live star badge format. The PR changes only README.md, is clean and mergeable, and has the maintainer disclosure; review is pending.

Awesome Best Open Source AI Agents 2026 PR #1 adds a GitHub-verified SandBase Harness runtime entry with license, language, Stars, activity date, category, and Best-for metadata. The PR changes only README.md, is clean and mergeable, and has the maintainer disclosure; review is pending.

Awesome AI Agents — Agent Playbook PR #1 adds SandBase Harness to the self-hosted frameworks list. The PR changes only README.md, is clean and mergeable, and has the maintainer disclosure; review is pending.

The same correction was added to the key MCP/DeepSeek review paths: Docker MCP Registry #4841, ToolSDK #488, DeepSeek Agent #411, TensorBlock #2068, and OpenModels #20.

An additional diff audit confirmed that the actual submitted files in all ten active catalog/registry PRs contain no docs/mcp-install.md reference; each current installation link resolves to docs/installation.md.

Channel-native social drafts for the same verified release are now available in the merged Daily Ops PR #238: X, LinkedIn, and Discord. They remain NEEDS REVIEW; no account publication is claimed.

The follow-up merged Daily Ops PR #240 adds the latest ecosystem-review links to the LinkedIn and Discord drafts and records them as pending external review. The drafts remain NEEDS REVIEW; no social account publication is claimed. Its merge commit is f868499b7e039ff9f141c12ad7c54a2831acf203.

The merged Daily Ops PR #241 adds the verified live English and Chinese DeepSeek Harness articles to the LinkedIn and Discord drafts. Both drafts remain NEEDS REVIEW; no social account publication or engagement is claimed.

The merged Daily Ops PR #242 adds the verified English DeepSeek Harness walkthrough to the X draft as a short-form discovery link. The X, LinkedIn, and Discord drafts all remain NEEDS REVIEW; no social account publication or engagement is claimed.

The Daily Ops PR #243 is now merged to sandbase-daily-ops (a8f9fdace9c0933df9003b91d530e2e9d1c39f9e). It adds the newly merged Awesome AI Engineering listing to the X, LinkedIn, and Discord drafts. The drafts retain NEEDS REVIEW and account-authorization requirements; no social publication is claimed.

The follow-up Daily Ops PR #244 is also merged (1ba5f6b481668906c0251d7ed55c611e150f740d), recording the draft-update evidence in the social publication log while preserving the no-publication claim.

The merged Daily Ops PR #245 adds MeshKore submission #14 and Agent Switchboard PR #44 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW; no social account publication or endorsement is claimed.

The merged Daily Ops PR #246 adds Hugging Face agent-harness registry PR #2432 to the X, LinkedIn, and Discord drafts. The copy remains attribution-only and NEEDS REVIEW; no social account publication is claimed.

The merged Daily Ops PR #249 (560805111339fa98d8be9c6cafb758af13c3dc8b) adds Collective AI Tools Issue #332 and Awesome Agent Skills PR #79 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW; no social-account publication, directory endorsement, or security certification is claimed.

The merged Daily Ops PR #250 (f5e854eb65476aa4ed3ebfc47d89c5538c2d78f2) adds Awesome MCP List PR #409 to the same X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW; no social-account publication or directory endorsement is claimed.

The merged Daily Ops PR #251 (d030d695a39563dcc5aa96a4778c7976a70dd8a8) adds Awesome Agent Runtimes PR #4 to the X, LinkedIn, and Discord drafts. The copy preserves that the destination request targets its maturity-gated watchlist rather than core-catalog inclusion; drafts remain NEEDS REVIEW.

The merged Daily Ops PR #252 (eb9219fe3c0ec645a87dcaacdbb222d7359ae930) adds Awesome Agent Infra PR #6 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW; no social-account publication or directory endorsement is claimed.

The merged Daily Ops PR #253 (b70ac1dacc538b1ce2fca078c0abb4e185283a8f) adds Awesome AI Developer Stack PR #2 to the X, LinkedIn, and Discord drafts. The drafts remain NEEDS REVIEW; no social-account publication or directory endorsement is claimed.

The bilingual DeepSeek Harness developer-preview articles were refreshed for SandBase Harness v0.3.8 in merged sandbase-blog PR #273, addressing the DeepSeek portion of blog issue #272. Article quality, 27 tests, Astro checks, and the 1,227-page production build passed; Cloudflare deployment run 33332934282 succeeded, and the English page plus Chinese page return HTTP 200 with v0.3.8. The separate auditable-research article remains pending because its required dedicated durable cover and three evidence screenshots are not yet available.

GitHub repository discovery metadata was refreshed on 2026-08-31: the topic set now explicitly includes devops, docker, and kubernetes while retaining the MCP, sandbox, audit, DeepSeek, and DSH terms; no capability or security claim was changed.

The bilingual Showcase quickstart was locally verified with npm ci and npm run build; runtime, MCP bridge, and Console artifacts all built successfully.

The public OpenSSF Scorecard result for commit 1359394 is now 4.6/10, including full scores for token permissions and SAST after the CodeQL workflow was added. npm audit --omit=dev --audit-level=high still reports 7 production dependency findings (5 low, 2 moderate); the remaining findings require a breaking AI SDK upgrade, so they are not hidden or force-upgraded. Dependabot now tracks npm and GitHub Actions updates weekly so the next upgrade arrives as a reviewable PR.

GitHub distribution snapshot

Owner-only GitHub traffic endpoints were checked on 2026-08-30. The repository had 638 stars and 61 forks. The current GitHub traffic window reports 2,679 repository views from 757 unique visitors and 2,234 clones from 463 unique cloners. The visible popular referrers include github.com, chatgpt.com, Bing, awesome-dsh-plugin.com, and dshbase.com. These figures measure discovery and activity, not conversion, and are not attributed to any single promotion channel.

Verified public discovery

• Official MCP Registry: the registry currently returns v0.3.8 as the active isLatest record and retains v0.3.4 as a non-latest historical record; direct installation should use the current v0.3.8 metadata.
• GitHub repository topics: refreshed with agentic-ai, agent-framework, agent-harness, runtime, MCP, sandbox, and self-hosted discovery terms.
• v0.3.8 Release Notes: now includes verified dshbase discovery, the official Showcase, and community self-hosting guides for release-page visitors.
• Project Discussion #82: latest distribution update records the public OpenSSF Scorecard result, scoped workflow permissions, Dependabot coverage, remaining audit findings, and the distinction between pending and verified discovery.
• Official DeepSeek Harness Showcase: project showcase thread; the latest update records the gVisor integration tutorial, Hugging Face attribution fix, and current v0.3.8 bridge/install links (comment).
• DeepSeek Harness security discussion: answered a user asking how to prevent third-party APIs or plugins from reaching the host filesystem, with factual sandbox, approval, least-privilege, audit, and negative-test guidance plus the Harness reference implementation.
• DeepSeek Harness memory discussion: explained safe separation of imported preferences, workspace context, transcripts, credentials, and tool permissions, and linked the runnable Harness reference for users evaluating memory migration.
• DeepSeek Harness plugin fault-isolation discussion: contributed a two-layer Host/runtime boundary and recovery checklist for users evaluating third-party plugins, with the Harness bundle and installation-recovery references.
• DeepSeek Harness model-vs-runtime discussion: explained how to separate model, tool-contract, runtime, and evidence-boundary failures, using the Harness sessions, sandbox, memory, approvals, audit, and replay layers as a concrete reference.
• DeepSeek Harness Agent scope discussion: shared the Agent-definition and Session-version-snapshot model for independent prompts, tools, skills, MCP servers, and permission boundaries, with API and DeepSeek integration references.
• DeepSeek Harness reasoning-only stop discussion: explained the distinction between provider stop signals and user-visible deliverables, and linked the Harness event model that separates reasoning, messages, tool calls, and replay evidence.
• DeepSeek Harness headless resume discussion: shared the Session resume, event-stream replay, and MCP attachment model with explicit boundaries, while distinguishing the existing Harness API from a future DSH --resume command.
• DeepSeek Harness session-log recovery discussion: shared the durable-seq versus transient-chunk boundary and orphaned-tool recovery model, with architecture and test references for avoiding whole-session failure after interruption.
• DeepSeek Harness MCP reconnect discussion: shared the Harness MCP Manager's stable tool wrappers, connection-error retry, exponential backoff, refreshed tool definitions, and the remaining design recommendation for slow retry after the fast reconnect budget is exhausted.
• DeepSeek Harness sandbox escalation discussion: provided a conservative workaround for redundant/non-widening sandbox_permissions requests and linked the Harness sandbox-backend boundary reference; this is an upstream discussion response, not a claim that SandBase fixes the DSH bug.
• DeepSeek Harness expired-MCP-session discussion: documented the boundary between transport-level reconnect and application-level -32001 session expiry, with a source-backed recovery runbook; this is a related upstream lifecycle case, not a claim that SandBase automatically handles every expired stateful MCP session.
• DeepSeek Harness session export discussion: explained SandBase's stable session, paginated event, resumable stream, and artifact APIs as a format-independent audit/export surface, while clearly distinguishing them from DSH's internal zstd session-file format.
• DeepSeek Harness observability discussion: shared the session usage fields, timestamped events, resumable event collector, Prometheus endpoint, and JSON metrics summary as a source-backed reference for log and token-usage export design.
• DeepSeek Harness streaming-render discussion: clarified the server/UI boundary: transient token deltas do not advance durable replay cursors, while persisted events remain ordered and deduplicated; UI-side frame batching can reduce re-renders without weakening replay correctness.
• DeepSeek Harness sandbox workdir discussion: shared source-backed workspace-root checks and negative tests for local, Kubernetes, artifact, and skill paths, while distinguishing early diagnostics from the OS/container isolation boundary.
• DeepSeek Harness delegated-agent permissions discussion: shared SandBase's same-backend sandbox inheritance, explicit delegation roster/depth checks, child tool-surface rebuild, and the principle that inherited isolation must not imply inherited escalation.
• DeepSeek Harness oversized-prompt discussion: shared SandBase's request-body, structured-event, SDK, and stable-session alternatives for large inputs, while explicitly agreeing that DSH still needs a native --prompt-file/stdin channel and argv preflight.
• DeepSeek Harness torn-session-log discussion: clarified that SandBase uses an append-only SQLite event log with monotonic seq and orphan reconciliation rather than DSH's zstd format, then endorsed preserving confirmed complete records during tail repair.
• dshbase: verified listing; the maintainer marked the plugin test=verified after headless L3 validation.
• deepseek-plugin.org
• DeepseekPlugin
• DSH Plugin Directory
• DSH Plugin Hub
• dsh.so Trust & Discovery Registry: public DSH detail page verified with HTTP 200 and a matching SandBase Harness entry; its trust level is an automated registry signal, not a maintainer security endorsement.
• DeepSeek Harness Hub: newly verified public community detail page; it describes SandBase Harness and the six-tool DSH bridge, but its page still pins v0.3.4 and no public correction/submission channel was found. Use the canonical repository and current installation guide as the source of truth; no current-version listing or endorsement is claimed.
• Duink DSH Universe: public DSH Universe detail page verified with HTTP 200 and a matching sandbaseai/sandbase-harness entry; it is an automated topic-derived catalog and its “outside plugin validation” marker is not a compatibility or security endorsement.
• DSH Plugin Leaderboard: public leaderboard verified with HTTP 200; SandBase Harness is shown as Install verified with an automated rank snapshot. This is a discovery/install signal, not a security or quality endorsement.
• DSH Directory
• DSH Harness
• FindHarness
• DSH Plugin Directory
• DSH Plugin Registry
• DSH Plugin
• dshplugin.dev
• DSH Plugin
• MCP Market
• MCP Repository: independent MCP detail page verified with a current repository/release snapshot; discovery only, with the repository remaining authoritative for installation and version claims.
• Awesome DSH Plugin web catalog: an independent public detail page now exposes the SandBase Harness entry; it is recorded as discovery only, and the repository/release metadata remain authoritative for installation and version claims.
• DSH Market: public detail page verified with HTTP 200 and a matching Harness entry; discovery only, with the repository remaining authoritative for installation and version claims.
• DSH Plugins: public detail page verified with HTTP 200 and a matching Harness entry; discovery only, with the repository remaining authoritative for installation and version claims.
• MCPVault: public automated listing verified; the page reports Apache-2.0 and current repository signals, but its own notice says the grade is computed from public signals and has not been maintainer-reviewed.
• F8W 中文项目档案: public Chinese project profile verified with HTTP 200; its metadata matches the repository and current 638-star snapshot, but it is an independent index and not maintainer-reviewed.
• RepoRank Русский профиль: public Russian-language project profile verified with HTTP 200 and a matching repository/release snapshot; it is an automated index, not maintainer-reviewed evidence.
• SSD Nodes self-hosting guide: independent third-party walkthrough covering installation, MCP servers, sandbox modes, and reverse-proxy deployment; the article demonstrates v0.3.2, so current release instructions remain authoritative.
• SandBase auditable research agent guide: first-party practical guide showing evidence ledgers, sandboxed execution, credentials, audit, and replay.
• OpenAgentSkill
• PluginBench: public MCP listing verified, but its captured installation example still references v0.3.4; use the repository's current v0.3.8 release and installation guide as the source of truth.
• DSH Plugin Store: public DSH plugin detail page verified; its generated content includes SandBase Harness and the official repository link, but version/install snapshots may lag the current release, so the repository remains authoritative.
• abordage/awesome-mcp: the independently maintained MCP catalog publicly lists SandBase Harness under both MCP servers and Sandboxing & Execution, with repository-backed wording for sandboxed execution, approvals, audit, and replay; its star count is an automated snapshot.
• MCP Servers Live
• DSH X-Ray
• Awesome DSH Plugin
• Awesome DeepSeek Harness
• Awesome DeepSeek Harness — ecosystem list
• DSHarness 101 Plugin Radar: independent bilingual DSH plugin radar lists sandbase-harness under Sandbox & Runtime; its directory label is a discovery classification and explicitly asks users to review the original repository before installation.
• DeepSeekDocs Ecosystem
• Awesome Agents
• Sifted Awesome AI Agents — verified Agent Runtime Top 100 entry: SandBase appears in the published Agent Runtime table; the generated snapshot currently shows it at rank 65 with 637 stars.
• Agent Framework Radar — verified automatic discovery: SandBase Harness is included in the published topic:agent-framework radar, currently shown at rank 2 with 638 stars; no manual submission was needed because the index is generated from GitHub Search API results.
• HVTracker — verified public Agent Frameworks profile: public automated profile and ranking snapshot for SandBase Harness; the score and rank are independent signals, not maintainer review or a security certification.
• LLM Agents Radar — verified automatic discovery: after adding the accurate llm-agent topic, SandBase Harness appears in the published radar at rank 1 with 638 stars; the index is generated from GitHub Search API results.
• Anil-matcha Awesome DSH Plugin — verified public entry: the published DSH plugin list includes SandBase Harness and describes its installable managed-agents bundle, six MCP tools, sessions, artifacts, audit/replay, and local/Docker/Kubernetes/worker sandbox options.
• Awesome DeepSeek Harness — verified public entry: the published Apps & Runtimes Built on DSH table includes SandBase Harness with its native DSH bundle, MCP tools, sandboxed sessions, and audit/replay; the table's displayed star count is a historical snapshot.
• Dominic789654 Awesome DeepSeek Harness — verified public entry: the published DSH Apps & Runtime list includes SandBase Harness with the managed-agents bundle, six-tool MCP bridge, persistent sessions, audit/replay, permissions, and local/Docker/Kubernetes/worker sandbox paths; the displayed star count is a live snapshot.
• Zhiyuan-Fan Awesome DeepSeek Harness Plugins — verified runtime entry: the curated Runtime & Sandboxes section publicly lists SandBase Harness with its DSH bridge, sandboxed sessions, durable state, audit trails, and MCP controls; the directory currently shows no external reference pages for the entry.
• Herdeny Awesome DSH Plugins 2026 — verified public entry: the published DSH ecosystem list includes SandBase Harness as an MCP-enabled agent runtime and separately lists the SandBase Skills companion.
• HackSing DSH Plugins — verified public entry: the published plugin directory includes sandbase-harness as a DSH bundle exposing agent runtime management through MCP.
• Awesome DSH Hub: an independently maintained bilingual DSH catalog publicly lists SandBase Harness; the catalog is auto-maintained, so the entry is recorded as discovery only and not as maintainer-reviewed endorsement.
• white0dew Awesome DSH Plugins — verified generated entry: the generated MCP/Skills catalog publicly lists SandBase Harness with its runtime, sandboxed sessions, audit/replay, and DSH install command.
• saltbo Awesome Stars — verified public entry: the public starred-project index includes SandBase Harness with its local-first runtime, MCP, memory, credentials, audit/replay, and Console description.
• GitHub Insight Radar — verified public recommendation: the public daily action report lists SandBase Harness as item 12 under Try today, with score 87.40 and no major risk flag; this is an independent recommendation signal, not a project-quality certification.
• Blue-Whale-Harness — verified public directory entry: the public generated catalog contains sandbaseai/sandbase-harness as a sandbox Runtime/MCP integration; the maintainer confirmed the entry was accepted and published after the catalog-intake review.
• Awesome DeepSeek Harness Top 500 — merged runtime entry: the maintainer confirmed the proposed DSH integration/deployment entry was merged after reviewing the current release, Registry identity, installation, and backend-dependent isolation scope.
• AdamPlatin123 DSH Plugin Radar — verified automatic discovery: the published radar includes sandbase-harness with the current 638-star signal and a DSH-compatible runtime description.
• Awesome DSH Plugin — merged Harness entry: the SandBase Harness submission is merged and present in the public plugin list.
• 0xsline Awesome DeepSeek Harness — merged runtime entry: the SandBase runtime and native DSH bundle entry is merged and present in the public ecosystem list.
• Arnon-hs Open Source / AtlasRepo — verified MCP entry: SandBase appears in the published MCP index at rank 72 with a generated project profile, score, metadata, and Chinese summary.
• Sagargupta16 Awesome MCP Servers — merged entry: the merged developer-tools entry is present on the public README and describes SandBase as a self-hosted MCP runtime with sessions, sandboxing, permissions, and audit/replay.
• mcpHQ Awesome MCP Servers — merged entry: the merged catalog entry is publicly present alongside the SandBase CLI entry, with the Official TypeScript label and self-hosted MCP bridge description; npm run validate, npm run generate, and npm run check-generated passed for 138 servers across 13 categories.
• abordage/awesome-mcp — merged Harness entry: the merged SandBase Harness entry is publicly listed under Sandboxing & Execution.
• kyrolabs/awesome-agents — merged Harness entry: the merged entry is publicly listed in the agent ecosystem catalog.
• Eric-LLMs/Awesome-AI-Engineering — merged Harness entry: the merged entry is publicly listed in the open-source agent engineering project table.
• Anil-matcha/awesome-dsh-plugin — merged Harness entry: the merged runtime entry is publicly listed in the DSH plugin catalog.
• Dominic789654/awesome-deepseek-harness — merged Harness entry: the merged runtime entry is publicly listed in the DeepSeek Harness ecosystem catalog.
• Arnon-hs Open Source — MCP projects
• SandBase Awesome Agent Runtime: public runtime landscape; its SandBase entry now links v0.3.8, the official MCP Registry, verified dshbase discovery, and the client installation guide via merged PR #15.
• Awesome Agent Cortex: SandBase CLI is publicly listed in the MCP ecosystem after merged PR #72.
• Awesome AI Devtools: SandBase CLI is publicly listed in the MCP tooling comparison and catalog after merged PR #33.
• VoltAgent Awesome Agent Skills: the SandBase multi-source-search skill is publicly listed after merged PR #946.
• WalkingLabs Awesome Harness Engineering: SandBase Harness is publicly listed in the Runtimes, Harnesses & Reference Implementations section after merged PR #76.
• abordage/awesome-mcp
• cccakeee/awesome-dsh-plugins
• anbeime/skill — Skills index
• Awesome DeepSeek Harness Plugins
• Hermes Ecosystem — SandBase stack
• AgentStack
• HackSing DSH Plugins
• Awesome DSH Plugins 2026
• Glama: SandBase has a public Glama page, but it is the CLI listing; no separate Harness listing was verified. The repository now declares maintainers in glama.json. Glama's published scoring guidance says organization-owned servers still require GitHub-authenticated authorship claiming, so no separate Harness score badge is claimed until that step is completed.

Pending or review-controlled

• AgentsAI.tools submission: a new public Agent/Framework directory was identified, but its frontend currently points to a Supabase hostname that returns NXDOMAIN from this environment, so the submission request was not sent and no listing is claimed. Recheck the form when the backend is reachable.
• SafeMCP directory: the public directory search was checked for sandbase and sandbase-harness on 2026-08-31; no standalone SandBase Harness listing was returned, so no unverified entry or claim is advertised yet.
• Msyvr Awesome Agent Sandboxes discovery issue #55: proposed SandBase Harness for curator review as a backend-aware agent execution sandbox, with explicit local/Docker/Kubernetes/worker scope and no universal or microVM isolation claim. The proposal now has a corresponding catalog PR #58; the issue follow-up links the review path and keeps the boundary qualification explicit.
• libukai Awesome DeepSeek Harness issue #94: proposed a factual SandBase Harness entry in the curated DSH external integrations/runtime section; the verification comment supplies v0.3.8, installation/MCP, runtime distinction from SandBase CLI, and backend-dependent isolation. Maintainer review remains pending because the available personal fork belongs to another upstream and cannot be used as a PR head.
• Awesome DeepSeek Harness Top 500 issue #3: the issue is closed after the maintainer confirmed the factual SandBase Harness entry was merged into the DSH integration/deployment ranking. The verification comment supplies v0.3.8, Registry, installation, runtime distinction, and backend-dependent isolation; this is a community listing, not a ranking endorsement or security certification.
• Awesome Agentic AI 中文 issue #210: proposed SandBase Harness for the Stage 7 Agent Production Engineering runtime resources; the conflict-free integration PR #228 resolved the earlier PR #213 path and is now merged.
• Jiaaqiliu Awesome Harness Engineering PR #9: added SandBase Harness to the Runtime / Harnesses resource table with persistent sessions, MCP boundaries, permissions, audit/replay, and local/containerized deployment evidence. The PR is clean; the maintainer verification confirms v0.3.8, installation/MCP documentation, and the deployment-dependent/no-benchmark qualification, while review is pending.
• Bureado Awesome Agent Runtime Security PR #29: proposed SandBase Harness for the sandboxing/isolation inventory with MCP, permissions, audit/replay, and deployment paths, explicitly bounded by the selected backend and configuration. The PR is clean; the maintainer verification confirms v0.3.8, installation/MCP documentation, and the non-universal/non-microVM qualification, while review is pending.
• Jiji262 Awesome Harness Engineering PR #10: added SandBase Harness to the Coding & Agent Harnesses section with persistent sessions, MCP boundaries, permissions, audit/replay, and deployment paths. The PR is clean; the maintainer verification confirms v0.3.8, installation/MCP documentation, and the deployment-dependent isolation/no-benchmark qualification, while review is pending.
• Blue-Whale-Harness catalog intake issue #153: closed after the maintainer confirmed SandBase Harness was accepted as a sandbox Runtime/MCP integration (not a cordis.patch.yml plugin), written to catalog/intents.json and repos.txt, and published on the generated site (maintainer confirmation). This is a public directory listing, not an endorsement or security certification.
• Awesome Agent Sandboxes PR #8: closed as a duplicate of the newer PR #9, which is the sole active review path for the Containers entry.
• Vivy Awesome Agent Sandbox PR #1: closed as a duplicate of the newer PR #2, which targets the same three catalog tables and is the sole active review path.
• ScienceAIX Awesome Harness Engineering PR #7: added SandBase Harness to Core Runtimes & Agentic OS with repository-backed wording for sessions, MCP governance, credentials, memory, artifacts, audit/replay, and optional execution backends. The PR is clean; the maintainer verification confirms v0.3.8, installation/MCP documentation, and the deployment-dependent isolation boundary, while review is pending.
• Ivishnuraj Awesome MCP Servers PR #4: added the SandBase Harness MCP bridge to Developer Tools & Infrastructure in the required alphabetical position, with documented sandboxed sessions, credentials, approvals, and audit/replay capabilities. The PR is clean with its security check passed; the maintainer verification records v0.3.8 and the deployment-dependent isolation boundary, while review is pending.
• AgentOps Landscape PR #23: added SandBase Harness to the generated open-source AgentOps tool dataset and regenerated its README, describing sandboxed sessions, MCP governance, credentials, and audit/replay; JSON validation, the repository updater, and diff checks passed. The PR is clean; the maintainer verification confirms v0.3.8, installation/MCP documentation, and the deployment-dependent isolation/no-benchmark qualification, while review is pending.
• Vivy Awesome Agent Orchestration PR #19: added matching English and Chinese entries under Deployment & Infrastructure, covering persistent sessions, MCP tools, sandboxed turns, credentials, and audit/replay. The PR is clean; the maintainer verification confirms v0.3.8, the installation/MCP guides, and the deployment-dependent isolation boundary, while review is pending.
• Awesome Agentic DevOps PR #107: added SandBase Harness to the structured community MCP catalog with action, approval, evidence, risk, and operator-note fields, plus README discovery metadata; YAML validation and README count synchronization passed, while the host Python 3.10 cannot collect the repository's existing Python 3.11+ test import. Maintainer verification and the deployment-dependent isolation boundary are recorded in the follow-up comment; review is pending.
• EvoMap Awesome Agent Evolution issue #53: submitted SandBase Harness through the required project-submission template under Agent Development Platforms, with release, installation, license, MCP, stateful-runtime, and backend-dependent isolation evidence. The verification comment records the current sources and maintainer disclosure; curation remains pending.
• Awesome Agent-Native Services issue #115: proposed a separate SandBase Harness entry under Agent Runtime & Infrastructure Services; the existing merged SandBase CLI entry explicitly excludes the broader Harness runtime. The submission includes all five admission criteria, MCP/installation evidence, backend-dependent isolation wording, and maintainer-affiliation disclosure; curator go/no-go is pending.
• Awesome Agent-Native Services PR #116: opened after the curator approved issue #115 and merged as 09ca7a4; it adds a source-backed SandBase Harness dossier, category/root indexes, and regenerated catalog pages. The verification follow-up confirms v0.3.8, Apache-2.0, installation/MCP/runtime evidence, and backend/deployment-dependent isolation. Inclusion is now publicly merged, but remains a directory listing rather than an endorsement or security certification.
• Fishman Awesome Agent Sandbox issue #3: proposed SandBase Harness as a container-backed runtime reference, explicitly distinguishing its optional backends from microVM isolation; curator review is pending.
• MCP.Directory submission: rechecked on 2026-08-31; after the endpoint's normal 100-character description validation, the URL-only submission API returned HTTP 409 with This repository has already been submitted. We'll review it soon!. A direct API search for sandbase currently returns zero results, so the review queue is confirmed but no public listing URL is available yet.
• Awesome Agentic Open-Source Tools PR #1: submitted a focused one-line entry under Agent Frameworks & Orchestration with current repository/release evidence and backend-aware isolation wording; maintainer-affiliation disclosure was posted and review is pending.
• awesome-ai-agents-2026 PR #2: submitted a focused one-line entry under Local Runtimes & LLM Management with current repository/release evidence and backend-aware isolation wording; maintainer-affiliation disclosure was posted and review is pending.
• AgentFirst directory PR #46: submitted the required tools/sandbase-harness.md entry under Compute & Sandboxes with agent-specific outcomes, GitHub metadata, and backend-aware isolation wording. The repository's sync:tool-submitters and enrich:tool-assets --write scripts were re-run on the current branch: both produced no additional diff because existing commit cf412e0 already contains the required submitter/media metadata. The verification comment records this; maintainer review remains pending.
• MCP Server Hub: the public entry is now live and verified with HTTP 200; it shows SandBase Harness, the official GitHub repository, and the submitted runtime/MCP description. The submission endpoint returned HTTP 500 after creating the entry, so the listing URL—not the transient response—is the authoritative discovery link.
• MCPFly submission: the public API accepted the canonical repository with HTTP 200 and returned success: true, Submission received and pending approval, and submission ID sandbaseai/sandbase-harness. No public MCPFly listing is claimed until approval and publication are verified.
• MCP Central API: public downstream registry mirror returns io.github.sandbaseai/sandbase-harness:0.3.4 with status: active and the official repository URL. This is a machine-readable mirror snapshot; installation and current version remain authoritative in the official registry/repository.
• mcpservers.org submission: the existing free submission queue was re-confirmed through the public form; the confirmation page states that SandBase Harness will be reviewed within 12 hours. The current public SandBase page is for SandBase CLI and mentions Harness in the open-source stack, but no standalone Harness listing has been verified yet. Treat this as the existing queue and do not resubmit.
• Open Source Observer OSS Directory PR #1211: open; adds SandBase Harness to the actively maintained public OSS registry. pnpm validate:projects passed for all 7,133 projects, owner-validation is green, and the remaining CI is ACTION_REQUIRED pending fork-workflow approval; maintainer review is pending (status note).
• OpenSourceChoice submission: the public free-submission endpoint returned HTTP 202 and {"ok":true} after a pre-submit search found no SandBase match. The project is private until human review; no public listing is claimed yet.
• Ossium submission: the public submission API returned HTTP 200 with success:true and review id G1BPvgbobGfKn1x9nSasR; free manual review is pending and no public project page is claimed yet.
• HVTracker correction #212: requested a rescan of the public tool/plugin-surface evidence, pointing to the current agent-plugin/, server.json, MCP bridge, and six documented DSH operations. The repository now publishes OpenSSF Scorecard and CodeQL workflows; the latest public Scorecard result for commit 1359394 reports 4.6/10, with full Token-Permissions and SAST scores, while the remaining audit findings are disclosed. The correction preserves HVTracker's independent limitations and disputes only the stale “no clear plugin system or broad tool surface” signal (latest follow-up).
• MyMCPTools submission: the directory advertises a free reviewed listing, but its submission route returned HTTP 403 to this environment and did not expose a usable form in Chrome; no submission is claimed and manual follow-up remains.
• AgentDepot submission PR #9: open; free MCP directory submission with a public-repository install path. The repository's npm run validate passed with 86 agents; current v0.3.8, Registry, and GHCR multi-arch evidence was added in the follow-up comment; maintainer review is pending.
• Mahonzhan Awesome Agent Harness issue #30: submitted a factual SandBase Harness entry for the Agent Harness / Agent Runtime section with v0.3.8, API, DeepSeek integration, and GHCR evidence; curator review is pending.
• AutoJunjie Awesome Agent Harness issue #59: submitted a factual SandBase Harness entry for the Agent Runtimes section with v0.3.8, API, DeepSeek integration, and GHCR evidence. The verification follow-up adds current installation and backend-dependent isolation details; curator review is pending.
• to-real Awesome Agent Harness issue #7: submitted a paired English/Chinese SandBase Harness entry for the runtime/execution section, with link-check-friendly repository, release, API, DeepSeek integration, and GHCR references; curator review is pending.
• AgentMatter submission #2: the public submission API re-confirmed the existing review-queue entry with accepted: true, duplicate: true, previewOnly: false, and component path agent-plugin/PLUGIN.md; it requires no resubmission. The entry carries Codex/Claude Code/Cursor/OpenCode compatibility metadata and the backend/deployment-dependent isolation qualification. No public resource page or catalog inclusion has been verified, so review remains pending.
• Acuvity ARC MCP Registry issue #18: submitted the current v0.3.8 SandBase Harness OCI bridge through the registry's MCP server intake, including runtime URL/API-key configuration, storage/session notes, and disclosure that it is distinct from the older sandbaseai/cli issue #17; maintainer review pending.
• MCP Atlas PR #2: open and mergeable; added SandBase Harness to the searchable MCP catalog using the official MCP Registry as the source, with JSON validation passing. The maintainer verification confirms v0.3.8, the canonical server.json, and the official MCP configuration guide; review is pending.
• AgentSpot submission #1: submitted SandBase Harness to the free Agent category; the directory's published threshold is 100+ GitHub stars or 2,500 recent package downloads, and the repository currently meets the star threshold. The verification follow-up records v0.3.8, GitHub/release plus GHCR distribution, and the backend/deployment-dependent isolation boundary; weekly curator review is pending.
• dshbase submission #95: closed after the maintainer confirmed the verified listing above.
• Plugin Hub duplicate-install issue #78: open; added a non-destructive recovery path (update Hub, remove only the exact residual target, retry the fixed HTTPS Git source) and opened the upstream Plugin Hub issue #25 for the idempotency fix. The current Hub v1.4.0 client appears to convert an installed catalog target to update semantics; upstream verification is pending (project comment, upstream follow-up).
• DeepSeek Awesome Agent PR #411: open and clean; current v0.3.8, native DeepSeek Harness example, installation guide, and official Showcase context were posted for maintainer review.
• Hermes AI Knowledge Ops PR #10: open; the generated knowledge catalog includes the SandBase Harness adapter. Maintainer verification records v0.3.8, the official MCP installation guide, and the deployment-dependent isolation boundary (comment); the host repository's security scan/account gate remains ACTION_REQUIRED.
• Agent Switchboard listing PR #44: open; refreshed v0.3.8 listing submitted with CLI/MCP access, current Registry evidence, and verified: false / featured: false for maintainer review. Supersedes and closes PR #42. A follow-up verification comment links the release, installation, and MCP configuration docs; the only reported check issue remains the repository owner's Vercel preview authorization.
• OpenModels MCP Registry PR #20: open and mergeable; maintainer review pending. The follow-up records the current v0.3.8 image, six-tool mapping, installation guide, and a fresh python3 validate.py pass across all 209 registry files (comment).
• ForgeIndex submission: submitted through the directory's official Google Form with the repository, v0.3.8 release, MCP bridge, local/Docker runtime, and installation-guide links; the form returned “Your response has been recorded.” Publication and verification remain curator-controlled, so no public listing is claimed yet.
• TensorBlock Awesome MCP Servers issue #2067 and automated PR #2068: the generated sidecar had an incomplete install command, so the issue and bot PR were closed as superseded by the direct contributor PR #2060, which is merged and provides the public profile. The historical correction remains useful for explaining why #2068 must not be used as an installation source. This remains separate from the existing SandBase CLI entry.
• Docker MCP Registry PR #4841: submitted SandBase Harness to Docker's official MCP Registry using the self-provided multi-architecture GHCR image. The registry entry passed its name/YAML/source/config validation, and the published image answered MCP initialize and tools/list with all six tools; Docker team review is pending. The PR checklist now points to the current docs/installation.md, with legacy MCP notes retained separately (follow-up).
• ToolSDK MCP Registry PR #488: submitted a Docker-backed SandBase Harness entry with the pinned v0.3.8 GHCR image, official installation guide, and URL/API-key configuration. node scripts/validate-registry.mjs --base origin/main passes with one changed package and zero errors; maintainer review is pending.
• McpMux Server Registry PR #286: submitted a Docker-backed SandBase Harness definition with the pinned v0.3.8 GHCR image, runtime URL/API-key inputs, official documentation, and logo. The repository's per-file schema validation and 264-file conflict check both pass; maintainer review is pending.
• add-mcp registry overlay PR #111: submitted the published OCI bridge to add-mcp's documented overlay path for package-only servers, with v0.3.8, stdio transport, GHCR image, and Harness URL/API-key metadata. The PR changes only registry.overlay.json; the maintainer verification confirms the six-tool bridge and configuration. GitHub currently reports BLOCKED because the host repository's Vercel preview requires authorization; review is pending.
• LobeHub Marketplace: checked the documented @lobehub/market-cli submission path; plugin submit currently requires an authenticated lhm login, and no LobeHub account/session is available in this environment. No submission is claimed.
• curated_mcp_servers PR #9: open; maintainer review pending.
• Awesome MCP Servers PR #13201: closed as an older duplicate in favor of canonical PR #13240; future tracking uses #13240 only.
• WunderCorp Awesome MCP PR #54: open; maintainer review pending.
• Awesome AI Agents PR #57: merged at 890f558, adding SandBase Harness to Agent Skills & Tools with local-first/self-hosted runtime, MCP tools, sandboxed execution, sessions, approvals, audit, and replay. The maintainer verification confirms v0.3.8 and the backend-dependent isolation qualification; superseded intake issue #56 is now closed. This is a public directory listing, not an endorsement or security certification.
• Awesome Agent Infra PR #5: open; added SandBase Harness to the Runtime and Control Plane table with persistent sessions, MCP tools, credentials, audit/replay, and sandboxed execution. The maintainer verification confirms v0.3.8, the official server.json and MCP configuration guide, and the backend-dependent isolation boundary; GitHub currently reports UNSTABLE with no automated check result. A follow-up correction replaces the stale docs/mcp-server.md reference with the current installation and sandbox-boundary documentation.
• Awesome Agent Frameworks PR #7: open; added SandBase Harness to Agent graph / runtime with managed sessions, MCP, sandboxing, approvals, and audit/replay; the repository's README/data validations passed. The maintainer verification confirms v0.3.8 and the backend-dependent/no-universal-isolation qualification; a follow-up link correction points reviewers to the current installation and MCP notes. GitHub currently reports UNSTABLE with no automated check result.
• Scottcjn Awesome Agents PR #59: open; maintainer review pending.
• Awesome Agentic MCP Security PR #28: open and UNSTABLE; added SandBase Harness to MCP hosting and enterprise runtimes. The verification comment confirms v0.3.8, current runtime/MCP/sandbox sources, and backend-dependent isolation; no universal isolation or security certification is claimed.
• Awesome Agent Harnesses PR #3: open; maintainer review pending.
• Awesome Agent Runtime Security PR #28: open; maintainer review pending.
• Awesome Agent Cortex PR #73: open and mergeable; awesome-lint and internal-links pass, while lychee fails on two pre-existing upstream links returning HTTP 429. A status comment records that the SandBase link is not implicated, and a follow-up verification adds current release/install/backend sources and the deployment-dependent isolation qualification; maintainer review is pending.
• Awesome Autonomous Ops PR #35: open and mergeable; added SandBase Harness to MCP Servers & Gateways for Autonomous Ops with a deliberately scoped description of session governance, approvals, audit/replay, and Docker/Kubernetes execution sandboxes. The PR follows the under-150-character format, includes source links and maintainer disclosure, and avoids claiming Kubernetes control-plane or security-certification status; review is pending.
• Awesome Agentic Hardening PR #5: open and mergeable; added SandBase Harness to Runtime Sandboxing & Capability Confinement with sandboxed sessions, least-privilege tool policies, credential management, approvals, and audit/replay. The maintainer verification confirms v0.3.8 and the deployment-dependent isolation boundary; a follow-up correction replaces the stale installation path with the current guide. GitHub currently reports UNSTABLE with no automated check result.
• Awesome Agent Sandboxes PR #58: open and mergeable; added SandBase Harness as an abstraction-layer runtime with regenerated catalog data and 148 passing tests. The follow-up clarifies that isolation depends on the selected local/Docker/Kubernetes/worker backend and is not a universal microVM claim; maintainer review pending.
• Arjan Awesome Agent Sandboxes PR #9: open and clean; SandBase Harness is listed under self-hosted sandboxes with per-session Docker/Kubernetes execution, MCP permissions, approvals, and audit/replay. A follow-up adds the current installation and backend documentation, verifies the v0.3.8 GHCR MCP bridge, and explicitly preserves the backend/deployment-dependent isolation boundary; maintainer review is pending.
• Fishman Awesome Agent Sandbox PR #2: open; SandBase Harness added to the sandbox list; maintainer review pending.
• Dloss Awesome Agent Sandboxes PR #7: open and clean; SandBase Harness added to the sandbox list; maintainer review pending. Latest v0.3.8 context was posted in the PR comment.
• Awesome AI Sandboxing PR #3: open and mergeable; added SandBase Harness to the list's host-level sandboxing section. A follow-up verification supplies the official installation, MCP, sandbox-backend, and release links and explicitly qualifies isolation as deployment-dependent; maintainer review is pending.
• Awesome AI Agents Security PR #107: open and mergeable; added SandBase Harness to Sandboxing & Isolation Environments under a concise, source-linked description of governed tool access, credentials, approvals, audit/replay, and deployment-dependent execution backends; a verification follow-up records the security-scope boundary, while maintainer review remains pending.
• UCSB Awesome Agent Security PR #16: open and mergeable; added SandBase Harness to System-level Runtime Defense with a concise tool reference for governed access, credentials, approvals, sandboxed sessions, and audit/replay. The PR links the project documentation and explicitly excludes vulnerability-scanning, universal-isolation, and certification claims; maintainer review is pending.
• Awesome DevOps MCP Servers PR #327: open and mergeable; added the SandBase Harness MCP bridge to Code Execution with local, Docker, Kubernetes, and self-hosted worker backends, plus governed sessions, approvals, credentials, and audit/replay. The entry links official installation/MCP/backend sources and does not claim universal isolation or security certification; a verification follow-up records the current evidence, while maintainer review remains pending.
• EverWorks Awesome MCP Servers PR #161: open and mergeable; added SandBase Harness to Code Execution & Automation and included a source-linked details/ page covering the v0.3.8 OCI bridge, installation, MCP setup, sandbox backends, and backend-dependent isolation; maintainer review is pending. The verification/link-correction comment replaces stale references to non-existent documentation paths with the current installation/MCP guides.
• AIAnytime Awesome MCP Server PR #78: open and mergeable; added SandBase Harness as a separate entry from the existing SandBase CLI listing, with the pinned v0.3.8 Docker bridge install command and official MCP setup link; maintainer review is pending. The verification/link-correction comment replaces the stale docs/mcp.md reference with the current MCP guides.
• Collabnix Awesome MCP Lists PR #105: open and mergeable; added SandBase Harness to the DevOps & Infrastructure table with the official repository as the source, a factual MCP bridge/runtime description, and no unsupported certification or universal-isolation claim; maintainer review is pending. The verification/link-correction comment replaces stale references to non-existent documentation paths with the current installation/MCP guides.
• MCP Finder Awesome MCP Servers PR #9: open and mergeable; added SandBase Harness to Cloud and DevOps using the list's required one-sentence source-linked format. The PR discloses this as a maintainer self-submission, links the v0.3.8 stdio installation guide and official MCP Registry identity, and records that a running self-hosted Harness API is required; maintainer review is pending. The verification comment confirms the current sources and backend-dependent isolation.
• Awesome AI Agent Tools PR #27: merged at commit f6b44644110ad8e6660afed0f9f5c08bb309db5e; added a separate sandbase-harness entry to the machine-readable MCP catalog under Agent Orchestration, with the published v0.3.8 Docker stdio command, Apache-2.0 license, current GitHub star count, source links, and backend-dependent isolation qualification. Catalog validation reported zero errors; one pre-existing Blockchain category-count warning remained before the merge.
• Enterprise AI Atlas Awesome MCP Servers PR #10: open and clean; added SandBase Harness to Developer Tools as a Community MCP server with the published v0.3.8 Docker stdio command, official installation/Registry links, maintainer self-submission disclosure, and backend-dependent isolation qualification. The target's ./scripts/validate-links.sh passed locally; the verification comment confirms current sources; maintainer review is pending.
• Awesome-MCP PR #36: open and mergeable; added a structured server entry to data/catalog.yaml under developer-tools, with stdio transport, source-backed runtime/sandbox metadata, and a separate identity from SandBase CLI. awesome-mcp validate, README generation, pytest -q (6 tests), and the target test CI check all passed; maintainer review is pending.
• Awesome-MCP PR #36 verification: maintainer comment confirms the current v0.3.8, MCP Registry, running-API, and backend-dependent isolation evidence.
• bgizdov Awesome MCP Servers PR #17: open and clean; added the repository's recommended contributions/sandbase-harness.json with DevOps categorization, the v0.3.8 Docker stdio bridge, Apache-2.0 metadata, installation documentation, and backend-dependent isolation qualification. JSON syntax and official source/documentation URL checks passed locally; the verification comment confirms current sources; maintainer review is pending.
• Awesome Coding Agents PR #41: merged at 98ee356, adding SandBase Harness to CLI Agent Helpers alongside the existing SandBase CLI entry. npm run validate:catalog passed for 38 tools and npm test passed all 12 tests; the merged entry keeps the runtime distinct from the CLI and preserves the backend-dependent isolation boundary.
• Awesome AI Coding Tools PR #665: open and mergeable; added SandBase Harness to MCP Servers and Directories with a factual self-hosted runtime/local stdio bridge description. The entry follows the target's documented one-line format, links the canonical repository, and preserves the backend-dependent isolation boundary; a verification follow-up records the current installation, Registry, image, and deployment evidence, while maintainer review remains pending.
• Awesome AI Developer Tools PR #11: open and mergeable; added SandBase Harness to DevOps & Deployment using the target's three-column table format and a conservative four-star tier. The entry links the canonical repository, describes the self-hosted runtime/MCP bridge and sandboxed execution, and keeps the backend-dependent isolation qualification; maintainer review is pending.
• Pipedream Awesome MCP Servers PR #111: open and mergeable; added SandBase Harness to the Artificial Intelligence list using the target's established one-line MCP-server format and a canonical GitHub source link. The PR includes maintainer self-submission disclosure and the backend-dependent isolation qualification; a verification follow-up records the current installation, Registry, image, and deployment boundaries, while maintainer review remains pending.
• Awesome AI & Developer Tools PR #5: open and mergeable; added SandBase Harness to CI/CD & DevOps with the target's concise factual format. The PR explains its fit as self-hosted infrastructure for agent sessions, sandbox backends, MCP, approvals, artifacts, audit, and replay, and retains the backend-dependent isolation qualification; maintainer review is pending.
• Awesome AI & Developer Tools PR #5 verification: maintainer comment confirms the current release, bridge image, source-backed scope, and backend-dependent isolation.
• LaunchApp Awesome AI Coding Tools PR #34: open and clean; added SandBase Harness to the target's Model Context Protocol (MCP) section with the existing 🟢 🆓 🏠 legend for open-source, free, self-hostable tools. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, and the backend-dependent sandbox qualification; maintainer review is pending.
• Awesome Agent Harness PR #86: open and mergeable; synchronized the host main, regenerated the English/Chinese catalog and verification report, and preserved the SandBase Harness entries under Execution Substrates & Sandboxing. GitHub now reports CLEAN; the directory verifier still reports 2 stale entries and 1 external OpenReview 403 baseline issue, unrelated to SandBase's entry. The maintainer verification confirms v0.3.8, installation/MCP documentation, and the backend-dependent isolation boundary. The maintenance update is recorded in merged Daily Ops PR #279; no social-account publication is claimed.
• Awesome Security Agent Harnesses PR #1: open; added SandBase Harness to Agent Sandboxes with sandboxed sessions, governed tool access, credentials, approvals, and audit/replay. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the backend-dependent isolation boundary; GitHub currently reports UNSTABLE with no automated check result, while the target repository has 53 pre-existing awesome-lint baseline errors outside this entry.
• Awesome Agent Infrastructure PR #21: open; focused SandBase entry under execution-sandboxes, with refreshed API/release/license evidence in the follow-up comment; duplicate PR #22 was closed to keep one review path.
• Awesome Agent Control Plane PR #3: open and clean; focused entry under the runtime-control section with MCP permissions, approvals, credential handling, audit/replay, and Docker/Kubernetes providers. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the backend-dependent isolation boundary; review is pending.
• Awesome AI Sandboxes PR #28: open and clean; added SandBase Harness to the Open Source sandbox section with local, Docker, Kubernetes, and self-hosted worker options. The maintainer verification confirms v0.3.8, installation/MCP documentation, and the backend-dependent/no-universal-isolation qualification; review is pending.
• Awesome CLI Coding Agents PR #313: open and clean; SandBase Harness added under Agent infrastructure with local-first runtime, persistent sessions, sandboxed tools, MCP, memory, credentials, audit, replay, and deployment surfaces. The maintainer verification confirms v0.3.8, the official MCP configuration guide, Apache-2.0, and the backend-dependent isolation qualification; review is pending.
• Awesome Loop Engineering resource suggestion #23: submitted for review under Operations Playbooks. The verification follow-up supplies the current release, installation/backends, DeepSeek example, and harness-design evidence while preserving the backend-dependent isolation boundary; maintainer curation remains pending.
• Awesome AI Engineering PR #4: merged; SandBase Harness is publicly listed in the open-source agent engineering project table. The entry is a factual directory listing and does not imply endorsement or security certification.
• Awesome AI Agents Frameworks PR #17: open and mergeable; SandBase Harness added to the source repository list. The maintainer verification records v0.3.8, the official MCP guide, core runtime capabilities, and backend-dependent isolation; generated ranking update and review are pending.
• Agent Infra Foundation PR #3: open; SandBase Harness added to the vendor-neutral agent infrastructure index; a follow-up disclosed project affiliation, Apache-2.0 licensing, v0.3.8 evidence, and backend-dependent isolation (comment); maintainer review pending.
• MCPFind PR #168: closed as a duplicate of the newer PR #171, which uses the same published bridge image and carries the more complete current description and deployment-boundary disclosure. The active review path is #171 only.
• E2B Awesome AI SDKs PR #344: open; maintainer review pending.
• NeuraLiying Awesome Agent Harnesses Issue #4: open; proposed SandBase Harness for Production Harnesses, SDKs & Frameworks. The verification comment supplies v0.3.8, installation/MCP sources, backend details, and maintainer disclosure; curation remains pending and no endorsement or security certification is claimed.
• Acuvity MCP Servers Registry Issue #18: open; proposed the pinned v0.3.8 GHCR stdio bridge and runtime environment variables. The verification comment confirms the six-tool bridge, the running-API requirement, and backend-dependent isolation; registry review remains pending.
• Nexu Harness Engineering Guide Issue #70: open; proposed SandBase Harness as a source-backed Harness Engineering resource. The verification comment links v0.3.8, installation/MCP documentation, runtime controls, and selectable backends; maintainer curation remains pending.
• Agentic Community Landscape PR #2: open and mergeable; the Agentic → Runtime entry and logo are present, and the latest maintainer verification records v0.3.8, Apache-2.0, and backend-dependent deployment boundaries; landscape entry review pending.
• AIM Intelligence Awesome MCP Security PR #48: open; maintainer review pending.
• MCP Marketplace PR #5: open; maintainer review pending.
• Awesome Agent Runtimes PR #1: open; SandBase Harness runtime profile review pending.
• Beejmaxx Awesome Agent Runtimes PR #3: closed as a duplicate of the newer PR #4, which updates the same generated watchlist files and is the sole active review path.
• Awesome Agent Runtime Security PR #28: open and mergeable; SandBase Harness added to Provenance, Instrumentation & Observability with conservative MCP, credential, policy, audit/replay, and backend-dependent isolation wording. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the non-kernel-isolation/non-vulnerability-scanning scope; review is pending.
• Awesome Agent Security PR #11: open and mergeable; SandBase Harness added to Sandboxed Execution with concise, backend-aware wording for MCP governance, credentials, approvals, and audit/replay. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the non-microVM/kernel-isolation qualification; review is pending.
• Awesome Agent Observability PR #11: open and mergeable; SandBase Harness added to Gateways with Built-in Observability with a conservative description of its MCP gateway, controls, and audit/replay records. The maintainer verification confirms v0.3.8, the official MCP configuration guide, the deployment-dependent isolation boundary, and the absence of an OpenTelemetry claim; review is pending.
• Adventure Wave Awesome Agent Security PR #2: merged; SandBase Harness is now publicly listed under Runtime Guardrails with MCP governance, approvals, credential controls, audit/replay, and backend-aware isolation wording. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the deployment-dependent boundary.
• Awesome Native Agent Platforms PR #1: merged into the SandBase-maintained agent-infrastructure landscape as a dedicated Harness entry, distinct from the broader SandBase platform overview; it links the current installation and security documentation and states the deployment-dependent isolation boundary.
• Yanmxa Awesome Agent Sandbox PR #1: open and mergeable; SandBase Harness added to Standalone Sandboxes with the list's live Stars badge, any runtime isolation label, and backend-aware wording. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the deployment-dependent/no-universal-isolation boundary; GitGuardian check is still in progress.
• IronSecCo Awesome Agent Sandboxing PR #1: closed as a duplicate of the newer PR #2, which is the sole active review path for the Self-hosted Agent Runtimes entry.
• LAS-WG Awesome Agent Infrastructure PR #10: open and clean; SandBase Harness added to Open-Source Projects with canonical repository and installation-guide links. The verification comment confirms v0.3.8, current runtime/MCP/sandbox sources, and backend/deployment-dependent isolation; maintainer review is pending.
• AIM-Intelligence Awesome MCP Security PR #49: open and mergeable; SandBase Harness added to Tools with MCP bridge, approval policy, credential, sandbox-session, and audit/replay wording. The maintainer verification confirms v0.3.8, the MCP configuration guide, and the distinction from vulnerability scanning and fixed isolation mechanisms.
• Awesome AI Agent Runtimes PR #3: open and clean; SandBase Harness added to Self-Hosted Solutions and the comparison matrix. The maintainer verification confirms v0.3.8, installation/MCP documentation, and the backend-dependent/no-universal-isolation qualification; review is pending.
• Awesome Agent Harness PR #29: open and clean/mergeable; SandBase Harness added to the Agent Harness timeline. The verification follow-up confirms v0.3.8, Apache-2.0, runtime capabilities, and backend/deployment-dependent isolation; maintainer review remains pending.
• Awesome Harness Engineering PR #224: open; SandBase Harness added to Demo Harnesses with local, Docker, Kubernetes, and worker execution details; maintainer review pending.
• Awesome Harness Engineering PR #226: open, clean, and mergeable; added a technical SandBase Harness reference to Security, Sandbox & Permissions with persistent sessions, MCP governance, approvals, credentials, artifacts, audit/replay, and backend-dependent isolation wording. Maintainer review pending.
• weiwei966 Awesome AI Harness PR #3: open; added bilingual English/Chinese Reference Harnesses entries describing the local-first runtime, MCP bridge, sessions, sandboxed turns, credentials, memory, artifacts, approvals, audit, replay, and backend-dependent isolation.
• Awesome Agent Harnesses inclusion suggestion #1: opened after the upstream fork name conflicted with an existing unrelated fork. The verification comment supplies v0.3.8, installation/MCP sources, runtime controls, and backend-dependent isolation; maintainer curation remains pending.
• Bilingual Awesome Agent Harness PR #6: open; matching English and Chinese entries added to the reference harnesses section; maintainer review pending.
• Bayshier Awesome Agent Harnesses PR #2: open and clean; SandBase Harness is listed under Platforms & Frameworks with a factual runtime description covering persistent sessions, MCP, sandboxed execution, credentials, approvals, audit, and replay. A maintainer follow-up adds v0.3.8, installation, and sandbox-backend sources and explicitly avoids universal-isolation or security-certification claims; review is pending.
• Cline MCP Marketplace submission #2364: open; non-interactive Cline installation and stdio initialize handshake were documented for the published v0.3.8 bridge image. A maintainer verification note links the current llms-install.md/server.json evidence, and a bilingual official Discussion update makes the path discoverable. Both preserve the Docker reachability, deployment-dependent isolation, self-submission, and no-endorsement boundaries; marketplace review remains pending.
• Best-of MCP Servers issue #370: the original proposal referenced v0.3.7; a maintainer update supplies the current v0.3.8 release, GHCR bridge image, six-tool installation guide, and MCP Registry identity. Inclusion and ranking remain pending; no endorsement, security certification, or causal referral is claimed.
• ChatMCP MCPSo submission #3834: open; submitted the official MCP metadata, v0.3.8 image, six-tool description, and self-hosted runtime configuration; review pending.
• Harness Engineering Guide resource #70: open; submitted SandBase Harness as a tool/framework reference for lifecycle, sandboxing, MCP, memory, credentials, audit, and replay; curator review pending.
• BrethofAI Awesome MCP Servers proposal #12: open; submitted the MCP bridge with official metadata, published image, and installation evidence. The maintainer follow-up records v0.3.8, the six-tool scope, backend-dependent isolation wording, and maintainer disclosure (comment); review remains pending.
• Mctrinh Awesome MCP Servers PR #105: open; submitted the current SandBase Harness MCP bridge to the Production-Ready Servers list. This is a new, current-repository submission distinct from the closed PR #102 for the retired sandbaseai/cli repository; maintainer review pending.
• Awesome Agent Frameworks architecture proposal #6: open; submitted SandBase Harness with the requested concept, architecture, key trade-off, and selection guidance. The guide is explicitly opinionated and requires architectural analysis rather than a link-only addition; curator review pending.
• Agent Sandbox Taxonomy profile proposal #5: open; submitted a conservative, backend-aware profile proposal covering compute isolation, credentials, governance, and observability. The issue explicitly welcomes corrections and asks the maintainer to assign scores from repository evidence; taxonomy review pending.
• Mossaka Awesome Agent Sandboxes PR #1: open; added SandBase Harness under Agent-Native Sandbox Platforms / Open Source with current stars, TypeScript, Apache-2.0, MCP, durable sessions, governance, and backend details; maintainer review pending.
• Awesome Agent Observability PR #11: open; added SandBase Harness under Model Context Protocol as a self-hosted runtime for sessions, approvals, governed tool execution, and audit/replay records; the required repository-level lint currently fails only because the base repository lacks the awesome and awesome-list GitHub topics.
• MCP Server Security Tools PR #5: open and clean; added SandBase Harness to the MCP security-tools catalog with a paired evaluation note, explicitly distinguishing governance/runtime controls from vulnerability scanning and documenting backend-dependent isolation. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the scope boundary; review is pending.
• MCP Server Finder evaluation issue #4: requested an independent assessment of the current six-tool MCP bridge, with source-backed release, installation, Registry, and backend-dependent isolation details. The follow-up records merged security PR #117 and its targeted verification (comment); Finder review remains pending and no score or security certification is claimed.
• Agentic DevOps MCP PR #42: added a focused SandBase Harness entry under Kubernetes & Containers with persistent sessions, MCP governance, audit/replay, and Docker/Kubernetes backend context. The PR is open and mergeable; maintainer review is pending (disclosure and verification).
• Awesome DevOps AI PR #54: merged at 2cc2c67 with a focused SandBase Harness entry under MCP Servers for DevOps. The public entry keeps persistent sessions, sandboxed execution, approvals, audit/replay, and Docker/Kubernetes backend context; the disclosure and verification remain source-backed and do not imply endorsement or security certification.
• Awesome Platform Engineering PR #63: added a focused SandBase Harness entry under Internal Developer Platforms with auditable sessions, sandboxed execution, approvals, and Docker/Kubernetes-backed workflows. The PR is open and mergeable; the lint check is in progress, and maintainer review is pending (disclosure and verification).
• Awesome DevOps Platform PR #4: added a focused SandBase Harness entry under AI & Automation in DevOps with auditable sessions, sandboxed execution, approvals, and Docker/Kubernetes-backed workflows. The PR is open and mergeable; maintainer review is pending (disclosure and verification).
• Awesome Platform Engineering PR #11: added a focused SandBase Harness entry under AI Platform Engineering & LLMOps with auditable sessions, sandboxed execution, approvals, and Docker/Kubernetes-backed workflows. The PR is open and mergeable; maintainer review is pending (disclosure and verification).
• Awesome LLMOps PR #539 (from project request #538): the repository automation generated a Runtime / AI Agent catalog PR. Its build and auto-merge workflow checks pass, while maintainer review remains pending; the original request includes the official repository, v0.3.8 release, MCP installation guide, security boundary, and maintainer disclosure (request verification comment). A concise maintainer follow-up links the same review evidence.
• TensorChord Awesome LLMOps PR #785: added a single source-backed SandBase Harness entry to the LLMOps table, covering the self-hosted runtime, MCP bridge, governance controls, audit/replay, and selectable execution backends. The contribution commit now includes the required Signed-off-by line and GitHub reports the DCO check SUCCESS; the PR remains under maintainer review. The maintainer verification and DCO follow-up preserve the backend/deployment-dependent isolation boundary. Initial and follow-up review-gated channel drafts are recorded in merged Daily Ops PR #281 and PR #282; no social-account publication is claimed.
• Awesome Agent Infrastructure PR #21: an existing focused submission under Execution Sandboxes was refreshed rather than duplicated; entries.yaml now points to the current MCP installation guide and uses deployment-dependent isolation wording. The PR is open and mergeable; maintainer review is pending (follow-up verification).
• Awesome MCP Security PR #12: open; added SandBase Harness to the Tools and code section as an open-source MCP governance/runtime tool, with a security-focused, non-marketing description covering approvals, credential scope, session isolation, and audit/replay.
• Awesome Agent Tools PR #17: open; added SandBase Harness under Agent Runtimes with repository build/install guidance and factual coverage of persistent sessions, sandbox backends, MCP governance, and audit trails.
• Yenanjing Awesome Harness Engineering PR #6: open; added SandBase Harness to the Agent Harness Frameworks table with the checked 638-star signal, Apache-2.0/TypeScript metadata, and runtime-specific capabilities; maintainer review pending.
• Awesome Harness Engineering 中文版 PR #6: open; added a Chinese description under Harness 框架与工具 covering persistent sessions, MCP governance, approvals, audit/replay, and replaceable sandbox backends; maintainer review pending.
• Awesome Agent Architecture issue #90: open; proposed SandBase as a source-backed system under study, mapped to tool runtime, permissions/sandbox, persistence, MCP, and observability sections. The verification comment links current source evidence and preserves the backend-dependent isolation boundary; maintainer review remains pending.
• ToolSDK MCP Registry PR #487: closed as a duplicate of the canonical PR #488; the canonical entry has passing registry checks and maintainer verification.
• E2B Awesome MCP Gateways PR #77: open and mergeable; SandBase Harness MCP bridge added to the gateway list. E2B's CLA bot requires the contributor to sign the E2B CLA and then comment @cla-bot check; this cannot be completed by an agent on the maintainer's behalf.
• AI Agent Infrastructure List PR #4: open; SandBase Harness added to runtime lists; maintainer review pending.
• Awesome MCP Clients PR #182: merged at 36289ef (https://github.com/AlexMili/Awesome-MCP/commit/36289ef0741290196284007d96503d578427c4c9). The entry records SandBase Harness as an MCP client/runtime integration with stdio and URL connectivity, persistent sessions, sandboxed tools, memory, credentials, audit, and replay; the maintainer verification confirms v0.3.8, the official MCP configuration guide, and the backend-dependent isolation qualification. This is a directory entry, not an endorsement or security certification.
• Skyming Awesome AI Agent PR #19: open; SandBase Harness added to open-source agent projects; maintainer review pending.
• Awesome Multi-Agent AI Harnesses PR #4: open; SandBase Harness added to Dedicated Multi-Agent Harness Systems with the project's existing stars-badge format; maintainer review pending.
• Anandesh-Sharma Awesome Agent Harnesses PR #5: open; SandBase Harness added to Coding-Agent Harnesses with approximate stars and distinctive runtime design; maintainer review pending.
• Awesome Agent Harness PR #58: open; maintainer review pending.
• Awesome AgentOps PR #14: open; deployment/runtime infrastructure entry review pending.
• Best of Agent Harnesses PR #99: open and mergeable; generated-list maintainer review pending. The maintainer verification records v0.3.8, installation/MCP evidence, runtime capabilities, and the backend-dependent isolation boundary. The PR was corrected to use the destination's required scripts/generate.py source plus regenerated outputs; local python3 -m pytest tests/ -q passes 54 tests (update). GitHub's latest fork tests workflow is action_required pending maintainer approval, not a test failure (CI status). The correction is recorded in merged Daily Ops PR #424. A later duplicate intake was closed and redirected to this canonical PR (duplicate cleanup).
• Awesome Agent Harnesses PR #5: open, clean, and mergeable; adds SandBase Harness to the coding-agent harness map. The verification follow-up confirms v0.3.8, Apache-2.0, runtime capabilities, and backend/deployment-dependent isolation; CodeRabbit reports success, while maintainer review remains pending.
• Production Agentic Systems PR #57: open and mergeable; maintainer review pending. The maintainer verification records v0.3.8, the Managed Agents API, DeepSeek MCP bridge, sessions, governance, audit/replay, and the backend-dependent isolation boundary.
• Awesome LLM Agents PR #319: open and mergeable; maintainer review pending. The entry follows the destination's single-file data format and places SandBase Harness under Agent Infrastructure; the local test suite passes 16 tests. The maintainer verification links v0.3.8, Apache-2.0/self-hosted scope, and the backend/deployment-dependent isolation boundary.
• Docker MCP Registry PR #4838: closed as a duplicate of the canonical PR #4841; review should continue on #4841 only.
• Awesome AI Agents PR #467: open and clean/mergeable; the existing single-line entry is under Building / Frameworks and maintainer review is pending. The verification follow-up confirms the source-backed runtime capabilities and records that local/Docker/Kubernetes/worker backends do not provide identical isolation properties.
• Scottcjn Awesome Agents PR #59: open and clean/mergeable; the existing entry targets an Agent platforms/frameworks directory and maintainer review is pending. The verification follow-up links the current installation guide and records the backend-dependent isolation boundary.
• Authora Awesome Agent Security PR #10: open; maintainer review pending.
• DevInsight Awesome MCP PR #6: open; maintainer review pending.
• RoyalPinto Awesome MCP Security PR #4: open and clean; added SandBase Harness under the permission category with generated output. The verification comment confirms v0.3.8, current runtime/MCP/sandbox sources, and backend-dependent isolation; the entry is not a security certification.
• Awesome AI Agents 2026 PR #539: open; maintainer review pending.
• Puliczek Awesome MCP Security PR #299: open; added SandBase Harness to MCP security tools with permissions, approvals, credentials, sandboxed execution, and audit/replay wording. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the distinction from vulnerability scanning; GitHub currently reports UNKNOWN with no automated check result.
• TensorBlock Awesome MCP Servers PR #2060: merged at c88cedf; the entry adds the current ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8 reference to Code Execution Servers. TensorBlock's merge follow-up provides the public SandBase Harness profile after registry deployment; this is a directory listing, not an endorsement or security certification.
• MCPVault submission: the public workflow accepts a repository URL and automatically reads project metadata, but the normal POST to /api/submit returned HTTP 401 not_signed_in because this environment has no MCPVault GitHub login session. No submission or listing is claimed; continue only after normal account authorization, and search/claim first to avoid duplicates.
• Bureado Runtime Security PR #27: open; maintainer review pending.
• Awesome MCP 中文 PR #521: open and clean; added SandBase Harness to 开发与代码执行 with v0.3.8, six MCP tools, the GHCR image, and local/Docker/Kubernetes/Worker sandbox coverage. A maintainer follow-up links the current installation and sandbox-backend documentation, records the deployment-dependent isolation boundary, and notes that directory inclusion is not security certification; Chinese-language directory review is pending.
• Deep Insight Awesome AI Agents PR #50: open and clean; added SandBase Harness to the Frameworks section as a self-hosted runtime/MCP bridge with managed sessions, sandboxed execution, approvals, credentials, artifacts, and audit-friendly state. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the backend-dependent isolation boundary; review is pending.
• Picrew Awesome Agent Harness PR #85: open and clean; current v0.3.8, runtime capabilities, and installation evidence were posted for maintainer review.
• Awesome MCP List PR #408: open and clean; added SandBase Harness as a self-hosted MCP runtime for sessions, tool calls, approvals, credentials, audit/replay, and Docker/Kubernetes execution. The maintainer verification confirms v0.3.8, the official MCP configuration guide, the runtime-vs-CLI distinction, and the backend-dependent isolation boundary; category review is pending. A follow-up correction replaces a stale docs/mcp-server.md reference with the current installation and sandbox-boundary documentation.
• Awesome MCP Devtools PR #299: open and clean; added SandBase Harness to Proxies and Gateways with self-hosted MCP bridge, permissions, approvals, credentials, audit/replay, and Docker/Kubernetes providers. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the backend-dependent isolation boundary; review is pending.
• YuzeHao Awesome MCP Servers PR #461: open and clean; added SandBase Harness to Sandbox & Virtualization with local, Docker, Kubernetes, and worker providers plus MCP permissions, approvals, credentials, audit, and replay. The maintainer verification confirms v0.3.8, the official MCP configuration guide, and the backend-dependent/no-universal-isolation qualification; review is pending.
• Awesome Security Agent Harnesses PR #1: open; added SandBase Harness to the Agent Sandboxes section with a factual description of sandboxed sessions, governed tool access, credentials, approvals, and audit/replay. A follow-up corrected the installation-guide link and states that isolation depends on the selected backend and deployment configuration; directory review is pending and the entry is not a security certification.
• Awesome MCP Collection PR #38: closed as a duplicate of the newer PR #39, which is the sole active review path for the Development & Version Control entry.
• Cue OS Awesome Agent OS PR #2: open and mergeable; added SandBase Harness to Runtimes with a concise description of persistent sessions, MCP tools, approvals, and selectable sandbox backends. The PR includes maintainer disclosure, v0.3.8 and installation evidence, and the backend-dependent isolation qualification; the repository check requires Python 3.11+ and could not run locally under the available Python 3.10, so remote maintainer/CI review is pending.
• Awesome AI Coding Sandboxes PR #14: open and mergeable; added SandBase Harness to the Containers & gVisor supplementary list with a mechanism-focused description of local, Docker, Kubernetes, and Worker execution backends. The PR includes source links, maintainer disclosure, and an explicit backend-dependent isolation qualification; data generation and diff checks passed, while review is pending.
• Awesome MCP Servers for DevOps PR #75: open and clean; added SandBase Harness to Kubernetes and Containers as a self-hosted MCP bridge for persistent sessions and local/Docker/Kubernetes/Worker execution sandboxes. The PR follows the directory's table format, includes installation/backend sources and maintainer disclosure, and explicitly qualifies the deployment-dependent isolation boundary; review is pending.
• Awesome X-Ops PR #250: open and clean; added matching English and Chinese entries under Agentic Workflow, describing the self-hosted runtime, MCP tools, persistent sessions, approvals, audit/replay, and selectable sandbox backends. The PR includes source links, maintainer disclosure, and the backend-dependent isolation qualification; review is pending.
• Agentbrisk submission: accepts open-source agents, frameworks, and MCP projects by email; no automated submission was attempted, so this remains a manual outreach candidate.
• PromptFrenzy AI Directory: provides a no-auth submission API and automatic directory PR, but requires a static dofollow badge on the tool's own durable domain before submission. The current Harness project has no verified Harness-specific site page suitable for that reciprocal badge; no badge was added to the unrelated SandBase platform site, and no submission/listing is claimed.
• Claw360 platform submission: a public directory for agent-only platforms with a free submission form. SandBase Harness is a plausible runtime/platform candidate, but the form's Web3Forms endpoint rejected this server-side request with HTTP 403 (Use our API in client side or contact support with server IP address); no listing or successful submission is claimed. A maintainer with a browser session can submit the official repository URL for directory review.
• MeshKore directory submission: free public submission accepted with response status=received, submission id 14, and a stated 24-hour review window; the submission explicitly left connect_to_mesh=false, and no public profile is claimed until review creates one.
• Promotion outreach templates: ready-to-send factual drafts for Agentbrisk and harnesses.sh; no email or direct message was sent from this environment.
• Agent Launchpad submission: free listing is available, but submission requires an authenticated magic-link session and a project screenshot; no credentials or upload were available, so this remains a manual outreach candidate.
• harnesses.sh: curated, manually verified cross-vendor harness directory; SandBase is not currently indexed, and the site requests missing-harness corrections through the maintainer's public channels rather than a submission form, so this remains a manual outreach candidate.
• mcp.so/mcpso submission thread: submitted SandBase Harness through the public GitHub Issue workflow with v0.3.8, official installation/MCP documentation, and the pinned GHCR bridge command; directory review and publication are pending.
• Collective AI Tools Issue #332: submitted SandBase Harness separately from the existing CLI entry using the directory's MCP submission template; directory review and publication are pending.
• Awesome Agent Skills PR #79: added SandBase Harness to the MCP runtime and infrastructure section; the verification comment confirms v0.3.8 and backend-dependent isolation. GitHub reports UNSTABLE; maintainer review is pending.
• Awesome MCP List PR #409: added SandBase Harness to AI Agents & Frameworks; the verification comment confirms v0.3.8, current runtime/MCP/sandbox sources, and backend-dependent isolation. GitHub reports CLEAN; maintainer review is pending.
• Awesome Agent Runtimes PR #4: proposed SandBase Harness for the maturity-gated watchlist; generated-data checks pass and maintainer review is pending.
• Awesome Agent Sandbox PR #2: added SandBase Harness to Related Projects with deployment-dependent isolation wording; Sourcery approval and GitGuardian checks passed, and target-maintainer merge remains pending because the current account lacks merge permission (handoff).
• Awesome Agent Infra PR #6: added SandBase Harness to Runtime and Control Plane; maintainer review is pending.
• Awesome CLI Coding Agents PR #314: added SandBase Harness to Runtime & execution backends; PR is mergeable and maintainer review is pending.
• Awesome AI Developer Stack PR #2: added SandBase Harness to the MCP Servers table; maintainer review is pending.
• Awesome Agent Cortex PR #74: added SandBase Harness to Agent Runtime Infrastructure; repository checks pass and maintainer review is pending.
• Awesome Agentic AI 中文 Stage 7 PR #228: merged at 1cb0406 as the conflict-free integration for #213; 1,036 script tests, 31 targeted tests, locale/mirror checks, and build checks passed.
• Awesome Terminal Agents PR #5: added SandBase Harness as an Engineering-Practice-Tool reference; maintainer review is pending.
• A2M submission: supports terminal-first AI project listings; SandBase is not currently indexed, but the submission flow requires account authentication through the A2M CLI/site, so this remains a manual outreach candidate.
• AgentKart submission: open-source AI agent marketplace with a public submission page, but the flow requires an authenticated site session; no credentials were available, so this remains a manual outreach candidate.
• DeepYard submission: submitted the official repository to the Frameworks & SDKs category through the public review form; the form returned a redirect to its /thanks page, but no public listing is confirmed yet. The description discloses maintainer affiliation and backend/deployment-dependent isolation.
• BotMarket MCP submission #4: the public MCP intake successfully parsed the canonical server.json metadata and queued submission 4 for manual review; automated registry PR creation failed because the directory backend returned a missing Git [SHA] error. Separately, BotMarket's public API now exposes an active SandBase Harness record (102971) sourced from the official MCP Registry (record API); this is a registry-sourced listing, not evidence that manual queue 4 was merged.
• AI Agent Tools submission: the public submission API accepted the SandBase Harness entry for the MCP Servers category and returned review record mtg57tuzw8mrh; no public listing is claimed until the directory publishes it.
• MCP Foundry: reviewed as a possible security-focused promotion channel. Its submission contract requires a distributable executable binary and toolbox.toml platform metadata, while SandBase's public MCP bridge is currently distributed as a Docker OCI image; no misleading or incompatible submission was made.
• MCP.Directory: the public submission API confirms the repository is already submitted and queued (409, “We'll review it soon!”); a public detail page is not yet discoverable. The free review queue is the selected path; no paid acceleration was used.
• AIMCP submissions: pending; no public detail page confirmed.
• MCPizy submission: public standard-review form is available, but it requires a contact email; no submission was made because no project-authorized email is configured in this environment.
• agentregistry: reviewed as a self-hosted registry platform rather than a shared public submission directory; its documented flow publishes into an operator-managed instance, so no third-party listing was created.
• MCP Hub / mcpdir Harness request #20: open; submitted SandBase Harness separately from the existing SandBase CLI issue #19, with v0.3.8, the published GHCR bridge, installation guide, six-tool scope, deployment-dependent isolation wording, and maintainer disclosure. Directory review is pending.
• AgentForge: intake form is reachable, but its submission API requires an authenticated session; no unauthenticated submission or listing is claimed.
• MCP Market: offers a free queue and paid expedited placement, but no submission was made because the form requests contact information and paid promotion is outside the current authorization scope.
• AgentsAI.tools submission: public agent form accepts GitHub projects without account login; the submission was attempted with the official repository details, but the backing Supabase hostname now returns NXDOMAIN in public DNS, so no successful submission is claimed and the form is gated until its backend is restored.
• Moltbook AI submission: submitted the official repository, GitHub URL, factual runtime description, and project maintainer GitHub noreply contact through the public review form; HTTP 200 confirmation received, directory review pending.
• AiAgents.Directory submission: submitted the official repository, factual runtime description, and project maintainer GitHub noreply contact through the public form; redirected to the site's success page, directory review pending.
• CordisPlugin: a public detail-page result was discovered, but direct verification currently returns HTTP 402; do not treat its metadata or install instructions as verified until the page is accessible.
• sandbase-blog freshness issue #272
• Handbook freshness issue #290

Gated or not eligible

• AgentForge submission: the public form API returned 401 Authentication required; no submission was created.
• AgentAtlas submission: the directory advertises a one-time $39 submission fee; no paid submission was made.
• Bloom publish: open-source AI-agent registry with a public publish page, but publishing redirects to account sign-in; no account was available, so no submission was made.
• agents-lib: the public directory invites GitHub contributions, but its GitHub link currently points to the placeholder your-org/agents-lib repository; no unverifiable submission was made.
• AI Agents Directory submission: the public form routes to a Dodo Payments checkout and the page advertises a $10 one-time listing fee; no paid submission was made.
• CyberAgents Exchange: relevant free, vendor-neutral directory for open-source security agents, skills, MCP servers, and playbooks; manual submission requires accepting the CyberAgents Contribution Agreement and recording the acceptance timestamp, so no PR was opened without explicit authorization to accept that agreement.
• AGNTCY Agent Directory Service: open OASF-based registry supporting MCP, A2A, and Agent Skills records; publishing requires an OASF record and a configured Directory node/network announcement, while SandBase currently has no A2A/OASF agent card, so this remains a future manifest/integration candidate rather than a claimed listing.
• AAIF project proposal: the Linux Foundation intake requires production adoption in at least two organizations, two maintainers from different organizations, at least ten contributors, and agreement to the hosted-project trademark/account and contribution-agreement process; the current project evidence does not satisfy those requirements, so no proposal was submitted.
• Agents-OSS submission: relevant independently maintained OSS agent directory with a repository-only intake, but the form is protected by Cloudflare Turnstile in this environment; no bypass or submission is claimed.
• Infrabase.ai submission: submitted the official SandBase Harness repository with a factual runtime description through the free review form; the form redirected to /success and confirmed receipt, so directory review is pending. No featured placement or backlink was purchased or selected.
• AgentIndex missing-agent report #3: submitted a structured request to index SandBase Harness as a local-first runtime with persistent sessions, sandboxed execution, MCP, approvals, audit, and replay; the maintainer verification note covers v0.3.8 and backend/deployment-dependent isolation (comment); directory review pending.
• Open Source Radar issue #7: the radar currently excludes SandBase Harness as marketing-driven because of the high number of directory links; a factual response documented independent SSD Nodes coverage, dshbase verification, F8W indexing, and the official Showcase for future reconsideration.
• AI Agent Radar daily report #46: automatically included SandBase Harness in the 2026-08-30 report with MCP, Apache-2.0, examples, tests, and agent-runtime topic signals; this is a dated radar snapshot, not a maintainer-reviewed permanent listing.
• Agent Infrastructure Landscape intake #173: submitted a curator intake for the agent-infrastructure landscape; the issue was corrected to reflect the repository's Apache-2.0 license, and a follow-up verified v0.3.8, the Docker MCP bridge image, and the current installation guide. Review is pending and the intake is not an endorsement or security certification.
• AI Native Landscape project submission #18: submitted bilingual project metadata under platform-infra / sandboxes-runtimes; curator review pending.
• Agent Harness Token-Consumption Benchmark issue #1: proposed SandBase Harness as a headless runtime candidate, with the v0.3.8 release, installation guide, DeepSeek Harness example, and published MCP bridge image; benchmark maintainer review pending.
• Agent Harness MCP preset proposal #47: proposed a source-backed SandBase Harness MCP preset or registry entity using the v0.3.8 bridge image and six tools; the integration requires a running SandBase API and backend/deployment-dependent isolation (comment); maintainer review pending.
• Awesome Agent Harness survey issue #14: proposed adding SandBase Harness to the Full-Stack Harnesses matrix with conservative E/T/C/S/L/V capability labels and source links; survey maintainer review pending.
• RUCAIBox Agent Harness reading list issue #11: proposed SandBase Harness as an open-source runtime resource with v0.3.8, MCP installation, Registry, and handbook evidence; research-list scope review pending.
• DSH Plugin Market metadata PR #558: metadata entry is open, clean, and its validate-submission check is successful; current v0.3.8 and installation evidence were posted for maintainer review.
• DSH Plugin Market metadata issue #1839 and generated PR #1847: current metadata scanner intake for sandbaseai/sandbase-harness; validate-submission passes and maintainer verification records the GHCR MCP bridge and backend-dependent isolation. Publication remains pending maintainer merge.
• dshplugin.dev submission: public form requires Turnstile verification; no automated bypass attempted.
• AgentSeal MCP Security Registry: the registry supports direct submission for servers not yet indexed, but its submission/API endpoints returned Cloudflare Turnstile verification from this environment; no bypass was attempted and no AgentSeal listing is claimed. A fallback registry request is now open as AgentSeal issue #36, with a source-backed verification comment (comment) requesting the normal analysis. AgentSeal's public guidance describes the registry as an automated MCP security-analysis pipeline (registry guidance, MCP analyzer documentation).
• Awesome Claude Code issue #2657: maintained the existing SandBase CLI suggestion with current v0.1.17, Apache-2.0, MCP Registry, and 25-client setup-guide evidence (verification comment); this is a disclosed review request, not a ranking, endorsement, or security certification.
• MCPDir issue #20: maintained the separate SandBase Harness runtime submission with current v0.3.8, six-tool MCP bridge, installation, and backend-dependent isolation evidence (verification comment); directory review remains pending.
• Awesome MCP issue #99: maintained a distinct Gateway & Proxy category proposal while documenting that Sandbox & Execution already contains the merged entry from PR #95; maintainers retain the decision on cross-category inclusion (verification comment).
• Awesome MCP Registry nomination #49: submitted through the registry's documented nomination workflow; the next automated scan decides whether the server clears its published trust-score threshold. No manual README edit or score claim was made.
• Awesome MCP Registry Servers PR #5: open and mergeable; added the official v0.3.8 SandBase Harness OCI/stdio metadata with required runtime URL and optional API-key variables. JSON validation passed, and the maintainer verification note records the canonical MCP Registry identity and source-of-truth links (comment).
• Chat2AnyLLM Awesome MCP Servers PR #14: open; added a machine-readable servers/sandbase-harness.yaml entry with the public repository, Apache-2.0 license, runtime/sandbox/audit/replay tags, and regenerated dist/ artifacts. python3 scripts/validate.py, build, and README generation passed; the repository's baseline unittest discovery is unavailable because its tests/ directory is not importable.
• DhanushNehru Awesome MCP Servers PR #75: open; added SandBase Harness to Development & DevOps with a concise, factual description of its MCP bridge, sandboxed turns, artifacts, audit, and replay. The target list had no existing Harness entry; the maintainer verification confirms v0.3.8, the official MCP configuration guide, separation from SandBase CLI, and the backend-dependent isolation boundary. GitHub currently reports UNSTABLE with no automated check result.
• mrtnrocks Awesome Agent Infrastructure PR #5: open; added SandBase Harness to Compute & Runtime with a concise local-first/self-hosted runtime description covering MCP, sandboxed sessions, artifacts, audit, and replay.
• MrPeppersDev Agent Infrastructure Landscape intake #173: submitted SandBase Harness to the catalog's documented auto-research intake for AI sandbox & runtime environments, including v0.3.8, Apache-2.0, official Registry, and backend-aware isolation notes. A follow-up records the Docker MCP bridge image and current installation guide, while preserving the catalog's pending-review/no-endorsement boundary. The Issue was created successfully; the repository currently has no intake label, so no label is claimed.
• MCP-SecurityTools 中文社区 issue #5: submitted a scope-aware proposal for a possible Agent Runtime Governance / MCP security-controls category; explicitly clarified that SandBase is not a vulnerability scanner and that isolation depends on backend/deployment configuration.
• FindMCP: the public form was rechecked on 2026-08-31 with the official repository, v0.3.8 Docker/stdio installation JSON, and the project's public GitHub noreply contact; its API still returned HTTP 500, so no listing was created or claimed.
• MCP Find: the public directory does not currently expose a SandBase entry. Its server-action submission endpoint returned HTTP 500 for the valid repository metadata, so no review record or listing is claimed and no repeated submission was attempted.
• MCP Server Spot: the directory has an existing SandBase CLI entry but no SandBase Harness entry. The public form did not return a submission confirmation from this environment, and its public data still contains only the CLI record; no duplicate submission or listing claim was made.
• MCP Index: the directory states that it syncs servers from the official MCP Registry within a day. SandBase Harness is not yet visible at a public detail URL; the manual submission action returned HTTP 403 from this environment, so the existing official-registry entry is being left for the directory's automatic sync rather than resubmitted.
• DSH Market: a public page exists, but its npm installation path is unsafe to promote: the public managed-agents package currently reports latest as 0.0.1, while this repository is 0.3.8; the page presents that package as the current runtime. The repository's GitHub-source install remains the source-of-truth path. Its submit page exposes placeholder correction links (hello@example.com and a non-existent issue route), and its API is disallowed by robots.txt, so no correction could be filed.
• DSH Packs: public discovery is confirmed, but its install snippet still pins v0.3.7; use the repository's current release tag instead. The public submission form currently exposes a placeholder Formspree endpoint (YOUR_ID), so no correction could be filed from this environment.
• GitHub repository About metadata: the public Homepage field now points directly to the current installation guide, while release links remain available in the README. This is a navigation improvement, not a usage or endorsement claim.
• DSH Plugin Hub: public discovery is confirmed, but its indexed metadata still reports 0.3.7; use the repository's current release tag and README as the source of truth.
• deepseek-plugin.org: public discovery is confirmed, but the page still contains v0.3.2 references; use the repository's current release tag and README as the source of truth.
• DeepseekPlugin: the public submission API confirms the repository is already listed, but its detail page still reports v0.3.7; use the repository's current release tag and README as the source of truth.
• DSH Hub: a public detail page exists, but it currently presents the old managed-agents package/repository metadata; do not use it as the current installation source until corrected.
• Agent Plugins Hub: public discovery is confirmed, but the detail page currently reports the old v0.2.0 package snapshot and marks install/runtime as not tested; use the repository's current release and installation guide instead.
• DSHPlugin registry: the public registry currently shows a SandBase Harness entry under the legacy managed-agents display name, but no current-version detail route was exposed by the page; keep the repository's pinned Git source as the installation authority.
• DSH Plugin: public discovery is confirmed, but the detail page still reports v0.3.7 and links to an older pinned commit; use the repository's current release tag and README as the source of truth. Its submission FAQ says listed projects sync automatically, so no duplicate submission is needed; recheck after the next directory refresh.
• CordisPlugin: search discovery reports a matching Listed page, but a direct verification request returned HTTP 402 from this environment, so no verified public listing or current-version claim is recorded.
• Coolbat Awesome DSH Plugins: the independent directory currently places SandBase Harness in its Hold Queue because the public managed-agents distribution identity is ambiguous/name-colliding; this is not counted as a verified recommendation until the identity/install path is clarified. A maintainer-facing identity clarification issue #17 now distinguishes the repository, canonical MCP server ID, pinned GHCR image, Git-source install, and unrelated npm package; the directory's conservative decision remains pending.
• npm managed-agents: unrelated package metadata points to aiwhiteteam/open-managed-agents, has a different maintainer, and reports latest as 0.0.1; it is not a SandBase release and must not be promoted as an installation path.
• Awesome Agent Harnesses suggestion #4: submitted SandBase Harness to the list's Production Harnesses, SDKs & Frameworks section with the current repository, installation, harness-design, and sandbox-backend sources. The entry explicitly qualifies backend/deployment-dependent isolation; the repository did not grant push access, so this is a maintainer-facing issue suggestion pending review rather than a pull request. The review-gated X/LinkedIn/Discord drafts are recorded in merged Daily Ops PR #276; no social-account publication is claimed.
• mcp.so submission thread #1: submitted the canonical SandBase Harness repository, installation guide, MCP server ID, v0.3.8 OCI image, and a concise runtime description to the directory's public MCP-server intake. The comment explicitly qualifies backend/deployment-dependent isolation; directory processing and any listing remain maintainer-controlled. The review-gated channel drafts are recorded in merged Daily Ops PR #277; no social-account publication is claimed.
• HKUST-KnowComp Awesome Agent Harness issue #8: submitted SandBase Harness as a source-linked runtime resource for possible placement under Tool Use & Code Execution or Sandboxing & Execution Environments. A source verification follow-up confirms the current v0.3.8 repository/docs and preserves the distinction from a research paper or security certification; curator scope review is pending. The review-gated channel drafts are recorded in merged Daily Ops PR #278; no social-account publication is claimed.
• DeepSeek Harness Handbook PR #291: merged as commit 425dd255 after companion catalog cleanup PR #292 removed three dead ecosystem links and synchronized the 79-resource counts. The English/Chinese SandBase Harness bridge guide is now refreshed from v0.3.7 to v0.3.8, with verify passing; this is a maintained documentation integration, not an endorsement or security certification.
• Sunrisepeak dsh-index PR #43: proposed the current SandBase Harness descriptor for the dsh-index catalog. The submitted revision passed its listed descriptor, site-build, boot, and gate checks, but GitHub currently reports DIRTY; a local rebase was reproduced successfully, while catalog publication remains pending maintainer write access and branch update.
• Official Discussion #116 update: published a factual v0.3.8 integration update with the current installation source, handbook/index review status, and a request for user feedback on backend choice, MCP tool schemas, session lifecycle, and audit/replay gaps. The post explicitly preserves the deployment-dependent isolation boundary and makes no certification or endorsement claim.
• Official Discussion #116 Chinese update: added a Chinese-language v0.3.8 integration summary linking the merged handbook guide, current installation source, and dsh-index status, with the same backend-dependent isolation and no-endorsement qualification.
• Official Discussion #116 latest update: announced the merged Awesome Coding Agents listing, reiterated the current v0.3.8 installation source, and disclosed the then-pending TensorBlock generated-metadata correction; TensorBlock later closed the automated path as superseded by merged PR #2060. No ranking, endorsement, benchmark, security certification, or social publication is claimed.
• Official Discussion #116 promotion update: published a bilingual checkpoint for the DeepYard review submission and BotMarket manual-review queue record 4, including their current limitations and the source-backed v0.3.8 installation links. No public listing, ranking, endorsement, security certification, or traffic claim is made.
• Official Discussion #116 BotMarket status correction: documented the independently verified active BotMarket record 102971 sourced from the official MCP Registry, while keeping manual queue 4 separate because its automatic PR step failed. No ranking, endorsement, security certification, or traffic claim is made.
• Official Discussion #116 TensorBlock update: announced the merged TensorBlock MCP directory entry and its public profile, including the current v0.3.8 bridge reference. The update explicitly describes this as directory discovery rather than security certification or endorsement and preserves the backend/deployment-dependent isolation boundary.
• AAE Agent Engineering issue #1: proposed SandBase Harness for the curated Agent Harness category of a 21-category, ten-project-per-category knowledge base. The submission includes v0.3.8, Apache-2.0, TypeScript, usage/architecture, DeepSeek Harness, MCP Registry, and release evidence; curator placement remains pending and is not presented as an endorsement or security certification.
• Picrew Awesome Agent Harness issue #82: proposed the merged DeepSeek Harness Handbook as a Documentation / Learning resource, with the current v0.3.8 bridge guide and source-backed runbooks. A prepared catalog commit adds the entry and regenerated mirrors; the available fork has unrelated history, so the latest maintainer note asks Picrew to cherry-pick or recreate the minimal change. Directory inclusion remains pending and is not an endorsement or security certification.
• Awesome Terminal Agents PR #5: open and clean; added SandBase Harness as an Engineering-Practice-Tool reference with project disclosure. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, and backend/deployment-dependent isolation; maintainer review is pending.
• Awesome AI Agents 2026 PR #16: open and clean; added SandBase Harness to the agent runtimes/platforms table. The verification comment confirms v0.3.8, current runtime sources, and backend-dependent isolation; maintainer review is pending.
• Awesome AI Engineering PR #4: merged at 0a308b0; added SandBase Harness to the open-source agent-engineering project table with current v0.3.8 runtime evidence. The merged directory entry is a factual listing, not an endorsement or security certification.
• Awesome AI Developer Tools PR #11: open and clean; added SandBase Harness to DevOps & Deployment with current Registry and GHCR references. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, and backend/deployment-dependent isolation; maintainer review is pending.
• Awesome Agent Sandboxes PR #59: open and clean; added a generated sandbox-catalog entry with refreshed outputs. The verification comment confirms v0.3.8 and the non-universal, backend/deployment-dependent isolation boundary; maintainer review is pending.
• Awesome Agent Sandbox PR #2: open and clean; added SandBase Harness to self-hosted/open-source sandbox solutions. The verification comment confirms v0.3.8, current runtime/MCP/sandbox sources, and backend-dependent isolation; maintainer review is pending.
• Awesome Agent Sandbox PR #4: open and clean; added SandBase Harness to container sandboxes. The verification comment confirms v0.3.8, current source links, and the deployment-dependent isolation boundary; maintainer review is pending.
• Awesome CLI Coding Agents PR #314: open and clean; added SandBase Harness to Runtime & execution backends with maintainer disclosure. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, and backend/deployment-dependent isolation; maintainer review is pending.
• Awesome Agent Infra PR #6: open; added SandBase Harness to Runtime and Control Plane. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, and backend/deployment-dependent isolation. GitHub reports UNSTABLE, so automated status remains unresolved and maintainer review is pending.
• Curated MCP Servers PR #9: open and clean; added SandBase Harness to Developer Tools & Infrastructure. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, and backend/deployment-dependent isolation; maintainer review is pending.
• Awesome Agent Runtimes PR #1: open and clean; added SandBase Harness to the runtime comparison table. The verification comment confirms v0.3.8, persistent sessions, MCP, and selectable execution backends, with isolation dependent on backend and deployment configuration; maintainer review is pending.
• AI Agent Infrastructure List PR #4: open and clean; added matching English and Chinese runtime entries. The verification comment confirms v0.3.8, current installation/MCP/sandbox sources, the user-owned running API, and backend/deployment-dependent isolation; maintainer review is pending.
• Skyming Awesome AI Agent PR #19: open and clean; added a concise Chinese entry for the local-first runtime and documented capabilities. The Chinese verification comment confirms v0.3.8, current source links, and the backend/deployment-dependent isolation boundary; maintainer review is pending.
• Awesome Agent Harness PR #58: open and clean; added SandBase Harness to Agent Runtimes with maintainer disclosure. The verification comment confirms v0.3.8, current runtime/MCP/sandbox sources, and backend-dependent isolation; maintainer review is pending.
• Awesome Agent Security PR #10: open and clean; added SandBase Harness to Sandboxed Execution. The verification comment confirms the source-backed runtime and explicitly states that directory inclusion is not a security certification; maintainer review is pending.
• DevInsight Awesome MCP PR #6: open and clean; added SandBase Harness to the MCP Servers section with maintainer disclosure. The verification comment confirms v0.3.8, the user-owned API, current MCP/sandbox sources, and backend/deployment-dependent isolation; maintainer review is pending.
• Awesome X for Agents PR #4: open and clean; proposed SandBase Harness for the Runtime & Sandbox section of this community-maintained directory for infrastructure used by AI agents. The verification comment discloses project affiliation and states that actual isolation depends on the selected runtime and deployment configuration; maintainer review is pending.
• Awesome AI Agents PR #55: open and clean; proposed SandBase Harness for the AI Agent Frameworks table using the directory's required Engine and Deployment fields. The verification comment discloses project affiliation and states that actual isolation depends on the selected runtime and deployment configuration; maintainer review is pending.
• Agent Plaza project post: published one bilingual, source-linked introduction under agent-infrastructure; the public API returned HTTP 200 and post ID plz_20260831055939_e9dd91f6. The post uses the sandbase-maintainer identity, links the canonical repository and installation guide, and states that isolation depends on the selected backend and deployment configuration. This is a community post, not an endorsement, security certification, or traffic guarantee.
• MeshKore directory submission: submitted the canonical repository through the public listing form; the endpoint returned HTTP 200 with status: received and submission ID 15, with review/addition stated within 24 hours. The submission listed SandBase Harness under AI Infrastructure and explicitly left connect_to_mesh disabled because no A2A endpoint was claimed. Listing status remains review-pending and is not an endorsement, security certification, or paid placement.
• AgentStack MCP listing: submitted SandBase Harness through the free community form as an MCP server in Dev Tools. The form redirected with HTTP 303 to its received page, and the live detail page now reports MCP server with quality status In review. The listing links the canonical repository and pinned GHCR stdio command; it remains a source-linked directory entry, not a verification badge, endorsement, security certification, or paid placement.
• AI Agent Tools Directory submission: submitted SandBase Harness through the public /api/submit form as an open-source infrastructure tool. The API returned HTTP 200, status: ok, and submission ID mtgu4e78fw1ja; a follow-up search found no public detail page yet, so review remains pending. No featured placement, ranking, endorsement, or security certification is claimed.
• AgentVerse-5K PR #3: added SandBase Harness to the Coding Agents and MCP Servers tables using the public repository description and current star count, in descending-star order. The PR is clean and mergeable; maintainer review is pending. This is a community index submission, not an endorsement or security certification.
• AI Agent Marketplace PR #36: added SandBase Harness to the marketplace's AGENT.md using its requested project format and official repository, installation, MCP, deployment, and issue links. The PR is clean and mergeable; maintainer review is pending. This is a directory submission, not an endorsement or security certification.
• Awesome AI Agents PR #4: added SandBase Harness to the Agent Tools table with the canonical repository and a concise factual description. The PR is clean and mergeable; maintainer review is pending. This is a community list submission, not an endorsement or security certification.
• 中文 Awesome AI Agents PR #13: added SandBase Harness to the MCP 生态 category through the directory's structured data/tools.json workflow, regenerated README output, and passed validate_catalog.py for 23 projects. The PR is clean and mergeable; maintainer review is pending. The submission distinguishes Harness from the existing SandBase CLI entry and is not an endorsement or security certification.
• BestAIAgent.in PR #1: added SandBase Harness to lib/imported-agents.ts as a source-linked imported/noindex entry, intentionally omitting pricing, scores, benchmarks, and unverifiable evidence claims. npm run verify:catalog passed; TypeScript typecheck was unavailable in the clean clone because dependencies were not installed. The PR is clean and mergeable, with deployment-dependent isolation explicitly qualified; maintainer review is pending.
• 中文 Agent 清单 PR #2: added an independent SandBase Harness runtime entry to the Chinese list's runtime/framework section, separate from its existing DeepSeek Harness entry. The PR is clean and mergeable; maintainer review is pending. The verification note links the current release and installation/MCP documentation and qualifies isolation by backend and deployment configuration.
• Protodex MCP Directory issue #52: submitted SandBase Harness through the directory's documented “Submit a Server” Issue workflow with the canonical repository, DevOps category, current release, installation, and MCP links. Index/maintainer review is pending; the request discloses project affiliation and does not claim inclusion, endorsement, or security certification.
• Nandanhegde MCP Directory issue #2: submitted SandBase Harness through the directory's documented GitHub submission workflow with the canonical repository, devtools category, current release, installation, and MCP links. The directory states that free listings are reviewed weekly; inclusion remains pending. Project affiliation and deployment-dependent isolation are disclosed, with no endorsement or security certification claimed.
• Public MCP Servers PR #12: added one curated data.js entry for the v0.3.8 Docker stdio bridge, including MANAGED_AGENTS_URL, optional MANAGED_AGENTS_API_KEY, and a scoped security note. The destination validator passed for 126 servers with no errors or warnings; maintainer review is pending. No hosted endpoint, universal isolation, endorsement, or security certification is claimed.
• OpenModels MCP Registry PR #22: added servers/sandbase-harness.yaml with the six documented stdio tools, pinned ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8 installation metadata, required MANAGED_AGENTS_URL, and optional MANAGED_AGENTS_API_KEY. The destination validator passed for 209 files; maintainer review is pending. The entry states that execution isolation depends on backend and deployment configuration and makes no hosted-endpoint, universal-isolation, endorsement, or security-certification claim.
• we-can-use MCP curation PR #2: added factual SandBase Harness entries to the curated English and Korean MCP infrastructure sections. The submission links the official repository and keeps the backend/deployment-dependent isolation qualification; the PR is mergeable and maintainer review is pending. This is a source-linked curation contribution, not an endorsement or security certification.
• Awesome-AI-Repos PR #2: added SandBase Harness to the AI Agents & Agent Frameworks section after confirming that no existing entry was present. The one-line description links the canonical repository and covers durable sessions, selectable sandbox backends, tool governance, artifacts, audit, and replay; maintainer review is pending and no endorsement or security certification is claimed.
• AgentStack directory issue #1: proposed SandBase Harness for the directory's MCP server category after confirming no existing entry in the hand-curated list. The proposal links the official repository and pinned v0.3.8 Docker bridge, requires a user-owned MANAGED_AGENTS_URL, and preserves the backend/deployment-dependent isolation boundary; maintainer review is pending and no endorsement or security certification is claimed.
• Awesome Agent Plugins issue #5: closed after the maintainer accepted SandBase Harness under Dev & Coding. The public catalog entry is now live as sandbase-harness, and the maintainer confirmed the canonical schema, real mcp.json/PLUGIN.md, self-hosted API requirement, and backend-dependent isolation (acceptance comment). This is a community listing, not an endorsement or security certification.
• Official Discussion #116 Agent Plugin update: published a bilingual integration update linking the schema-validated agent-plugin/ bundle and Awesome Agent Plugins issue #5. The post identifies the user-owned Harness API prerequisite and backend/deployment-dependent isolation boundary; it is a project update, not a catalog inclusion, endorsement, or security certification claim.
• Official Discussion #116 promotion checkpoint: published a bilingual summary of the four current directory review paths—Awesome Agentic AI, Awesome MCP Toolkit, Awesome Engineering AI, and Awesome Agent OS. Each remains maintainer-pending; the update discloses project affiliation, user-owned API requirements, and backend/deployment-dependent isolation, and makes no inclusion, ranking, endorsement, or security-certification claim.
• AI Systems Atlas suggestion #34: proposed SandBase Harness through the Atlas's required evidence-backed system-suggestion workflow. The request links the canonical repository, Apache-2.0 license, runtime documentation, and the backend/deployment-dependent isolation boundary; Atlas editorial review is pending and no inclusion, endorsement, or security certification is claimed.
• Awesome Agent OS PR #3: proposed one concise SandBase Harness entry under Runtimes in the directory's one-project-per-PR workflow. The entry covers durable sessions, sandboxed tools, MCP, approvals, credentials, and replay; the destination check is CI-controlled, maintainer review is pending, and no inclusion, endorsement, ranking, or security certification is claimed.
• Awesome Engineering AI PR #3: proposed one concise source-linked entry under Harnesses, GUIs and workspaces. The destination requires an active project, at least 500 stars, and a concrete coding-agent use case; SandBase met those checks, while GitGuardian and maintainer review remain pending. No inclusion, endorsement, ranking, or security certification is claimed.
• Awesome MCP Toolkit PR #3: proposed one concise Chinese-language entry under Developer & Code following the destination's contribution format. The entry links the official repository and documents the MCP/runtime boundary, user-owned API prerequisite, and backend/deployment-dependent isolation; maintainer review is pending and no inclusion, endorsement, ranking, or security certification is claimed.
• Awesome Agentic AI PR #2: proposed one source-linked SandBase Harness entry under Sandboxes and Computer Use. The description covers durable sessions, governed MCP tools, approvals, credentials, audit/replay, and selectable backends; maintainer review is pending, with no inclusion, endorsement, ranking, or security certification claimed.

The latest Discussion #116 status update records four duplicate cleanups: MCPFind #168, Awesome MCP Collection #38, Awesome Agent Sandboxes #8, and Awesome Agent Sandboxing #1 were closed in favor of their newer review paths (#171, #39, #9, and #2). It also records that Hugging Face #2432's Cursor Bugbot passed while Docker MCP Registry #4841, OpenModels #22, and Picrew #86 remain maintainer-reviewed. The update makes no inclusion, ranking, endorsement, or security-certification claim and preserves the user-owned API and backend/deployment-dependent isolation boundary.

The follow-up Discussion #116 clarification records the Beejmaxx #3/#4 duplicate cleanup and confirms that MobinX #408 and #409 target different directory sections and should both remain open. No inclusion, ranking, endorsement, or security-certification claim is made.

The latest Discussion #116 queue clarification records the Vivy #1/#2 duplicate cleanup. It also confirms that Bureado #29/#30 and Fhiltscher #14/#15 target different directory sections and remain valid separate review paths.

The latest Discussion #116 status update records Yanmxa #2 as approved with successful Sourcery and GitGuardian checks, while preserving Yanmxa #1 as a separate Standalone Sandboxes entry. The remaining merge is controlled by the target repository maintainer.

The Awesome Open Source AI scope-check issue #723 proposes SandBase CLI for the curated open-source AI list's Agentic AI or Developer Tools & Integrations section. The issue follows the destination's request-first rule because category placement is not exact; it remains open with no maintainer response and no PR has been opened. The proposal is for the separate CLI/MCP bridge, not a SandBase Harness listing, and does not claim inclusion, endorsement, or security certification.

The LuciferForge MCP Directory issue #52 requests a SandBase Harness listing. A source-correction comment replaces the stale docs/mcp-server.md reference with the current installation, runtime, and MCP source paths (comment); directory review remains pending. The proposal discloses project affiliation and backend/deployment-dependent isolation, and does not claim inclusion, endorsement, or security certification.

The MiniMax Awesome Integrations issue #12 requests a SandBase Harness integration entry under Developer Tools. A follow-up updates the proposed release from v0.3.7 to v0.3.8 and links the current MiniMax, installation, and MCP guides (comment); maintainer review remains pending. The request documents the public MiniMax endpoints and model IDs, discloses project affiliation, and makes no inclusion, endorsement, or security-certification claim.

The DhanushNehru Awesome MCP Servers PR #75 remains open for maintainer review. A correction to the earlier verification note replaces the removed docs/mcp-server.md path with the current llms-install.md and docs/installation.md links (comment); the entry remains a factual, source-linked discovery proposal with backend/deployment-dependent isolation and no endorsement or security-certification claim.

The Picrew Awesome Agent Harness PR #86 remains the canonical open entry after duplicate #85 was closed. A link-correction follow-up replaces the removed docs/mcp-server.md path with the current llms-install.md MCP guide (comment); the PR remains open for maintainer review with the backend/deployment-dependent isolation qualification.

The Nandanhegde MCP Directory issue #2, Collective AI Tools issue #332, and MyMCPTools issue #8 each had an open SandBase Harness request with no prior maintainer response. Follow-up clarifications identify the removed docs/mcp-server.md path and provide the current llms-install.md and docs/installation.md links (Nandanhegde, Collective, MyMCPTools); all remain curator-controlled and pending.

The Kubernetes SIG Agent Sandbox issue #1500 opens a scope discussion about a source-linked SandBase Harness compatibility or deployment example. It accurately separates Agent Sandbox's Kubernetes workload orchestration from SandBase Harness's agent-session/runtime governance, and explicitly makes no existing-adapter, inclusion, endorsement, or security-certification claim. The issue is awaiting maintainer guidance before any PR or documentation change.

The public mcpub submission flow was evaluated and intentionally not used: it requires a public MCP endpoint plus /.well-known/mcp.json, while the SandBase Harness bridge is configured against a user's own API URL/API key rather than a public hosted endpoint. MCP Central's submission documentation describes its catalog as a mirror of the official MCP Registry, which already contains the canonical Harness record; no duplicate submission was created.

The Agentic AI Foundation project proposal was evaluated as a high-value future promotion route but not submitted. The official template requires evidence of production adoption in at least two organizations, two core maintainers from different organizations, at least ten contributors, a public governance/decision process, and a required agreement to donate project trademarks and accounts if accepted. Those claims and legal commitments cannot be made on the project's behalf without verified evidence and explicit owner authorization. AAIF review remains a future option, not a current application or foundation affiliation.

The KillerSkills marketplace submission accepts a public PLUGIN.md, and the repository now provides agent-plugin/PLUGIN.md alongside the schema-validated plugin.json and mcp.json. The document is source-backed and tested with the existing MCP distribution suite (6 tests passed). The marketplace requires GitHub sign-in to submit; no listing or marketplace approval is claimed until an authorized account completes that step.

The MCP Find community directory PR #171 adds the SandBase Harness MCP bridge to community-servers.yml using the published ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8 image. The PR is open and currently mergeable; its entry links the canonical repository and qualifies isolation as dependent on the selected backend and deployment configuration. This is a maintainer-reviewed directory submission, not an endorsement or security certification.

GitHub repository Topics were refreshed to replace the less central agent-memory tag with the published agent-plugin capability. The current 20-topic set now covers agent runtime, plugin, harness, sandbox, MCP, self-hosting, infrastructure, audit, and deployment discovery terms; this is repository discoverability metadata only and does not imply third-party endorsement.

The duplicate weiwei966/awesome-ai-harness PR #4 was closed in favor of the more complete PR #3, which adds matching English and Chinese reference-Harness entries. The closure comment links the canonical review path; no directory inclusion or endorsement is claimed.

The Agent Plugins Directory listing is publicly live and source-indexed, with the plugin's MCP configuration and Copilot/Cursor/VS Code install paths visible. The current page is pinned to an older source revision and displays the earlier 0.3.4 bridge image, so the repository links the page and states the current 0.3.8 source configuration; a future directory reindex is still required before calling the page refreshed. The directory is an independent discovery surface and does not execute plugin code or provide security endorsement.

The maintained aloth/awesome-ai-agents list now publicly includes sandbaseai/sandbase-harness under Agent Skills & Tools. The entry is a factual source link covering the runtime's MCP, sandbox, session, approval, audit, and replay capabilities; it is a community-list inclusion and not a security certification or project endorsement.

The latest Discussion #116 promotion checkpoint reconciles four additional public directory merges: Awesome AI Agents #57, Awesome Agent-Native Services #116, Awesome DevOps AI #54, and Awesome MCP Servers #45. The state is also recorded in merged Daily Ops PR #458. These are source-linked community listings, not rankings, endorsements, recommendations, or security certifications; effective isolation remains dependent on the selected backend and deployment configuration.

The maintained Awesome Agent Plugins catalog now publicly lists sandbase-harness under Dev & Coding. Issue #5 was closed after the list maintainer independently checked the canonical schema, real mcp.json and PLUGIN.md, and the self-hosted/backend-dependent runtime boundary (acceptance comment). This is a community plugin listing, not an endorsement or security certification.

The public-listing confirmation is also recorded in Discussion #116. The update distinguishes the accepted Agent Plugins catalog entry from the still-pending Agent Plugins Directory reindex and does not claim ranking, recommendation, endorsement, or security certification.

The latest Discussion #116 DSH listing confirmation records the merged Awesome DeepSeek Harness Top 500 #3 entry and the accepted Blue-Whale-Harness #153 sandbox Runtime/MCP listing. Both are community discovery surfaces, not ranking endorsements or security certifications.

The closed GitHub Awesome Copilot issue #2725 was rejected with the reason “purely paid service.” A follow-up maintainer handoff documents that the plugin is Apache-2.0, self-hosted, and distributed through a Docker stdio bridge to a user-owned MANAGED_AGENTS_URL, rather than requiring a hosted SandBase SaaS account. The current account lacks permission to reopen the issue or trigger /rerun-intake, so no acceptance or re-review is claimed.

The follow-up Discussion #116 promotion checkpoint summarizes the latest review paths: MCPRadar #8, Awesome MCP Registry #49, AgentStack #1, AI Systems Atlas #34, RUCAIBox #11, AAE #1, Awesome Agent Harness Survey #14, and the bilingual list #7. The update distinguishes independent review requests from directory inclusion and makes no ranking, endorsement, or security-certification claim.

The Awesome MCP Registry nomination #49 now has a successful Validate nomination workflow (run 33380817777); the workflow's actual validate job was skipped, and the public README still has no SandBase Harness entry. The accurate state is workflow accepted with evaluation/listing pending, not a score or inclusion. This correction is recorded in Discussion #116; no ranking, endorsement, recommendation, or security certification is claimed.

The MCPRadar scan request #8 asks for an independent scan of the SandBase Harness MCP bridge. A maintainer verification comment links the current v0.3.8 release, official MCP Registry identity, published bridge image, and llms-install.md configuration (comment). The request states that the bridge uses a user-owned Harness API and that isolation depends on the selected backend and deployment configuration; no scan result, security certification, endorsement, or universal isolation claim is made before the directory's review.

The Awesome MCP Registry nomination #49 submits the public SandBase Harness MCP server to that directory's documented automated evaluation. The maintainer verification links the current v0.3.8 release, official Registry identity, published bridge image, and llms-install.md configuration (comment), and explicitly leaves the score and inclusion decision to the registry process. The submission discloses project affiliation and qualifies isolation by backend and deployment configuration; no listing, ranking, endorsement, or security certification is claimed before evaluation.

The AgentStack issue #1 proposes SandBase Harness for the directory's MCP server category. A maintainer verification comment links the current v0.3.8 release, official MCP Registry identity, published bridge image, and llms-install.md configuration (comment). It discloses the user-owned API requirement, project affiliation, and backend/deployment-dependent isolation; directory review remains pending and no inclusion, ranking, endorsement, or security certification is claimed.

The AI Systems Atlas issue #34 proposes SandBase Harness as an operational AI system. The verification comment links the current v0.3.8 release, Apache-2.0 license, installation/MCP guide, and runtime boundary (comment). It discloses the user-owned API requirement, project affiliation, and backend/deployment-dependent isolation; curator review remains pending and no inclusion, ranking, endorsement, or security certification is claimed.

The RUCAIBox Awesome Agent Harness issue #11 is a scope-qualified proposal for SandBase Harness as an open-source engineering/runtime resource. The verification comment links the current release, source, installation/MCP guide, official Registry identity, and related handbook (comment). It explicitly distinguishes the runtime from a research paper and asks the maintainer to close the proposal if the collection only accepts formal publications; no inclusion, ranking, endorsement, or security certification is claimed.

The Awesome Agent Harness survey issue #14 proposes SandBase Harness for the Full-Stack Harnesses completeness matrix. The verification comment links the current release, runtime/usage documentation, installation/MCP guide, and official Registry identity (comment). It preserves conservative partial labels for context management and evaluation, discloses project affiliation, and qualifies isolation by backend and deployment configuration; matrix inclusion remains curator-controlled and is not a ranking, endorsement, or security certification.

The AAE Agent Engineering issue #1 proposes SandBase Harness for the Agent Harness category. The verification comment links the Apache-2.0 source, current v0.3.8 release, usage/architecture guide, MCP metadata, and DeepSeek integration example (comment). It leaves category placement and the list's entry limit to the curator, discloses project affiliation, and qualifies isolation by backend and deployment configuration; no recommendation, ranking, endorsement, or security certification is claimed.

The bilingual Awesome Agent Harness issue #7 proposes matching English and Chinese runtime entries. The verification comment links the current release, API reference, installation/MCP guide, DeepSeek integration example, and published bridge image (comment). It discloses project affiliation and leaves category/paired-README decisions to the list maintainer; isolation depends on the selected backend and deployment configuration, and no inclusion, ranking, endorsement, or security certification is claimed.

The Kubernetes SIG Agent Sandbox issue #1500 is a scope-qualified discussion about a possible compatibility or deployment example. The follow-up proposes a documentation-only integration boundary: Agent Sandbox manages Kubernetes workload lifecycle while a user-owned Harness API governs agent sessions and selects the Kubernetes execution backend (comment). It explicitly makes no first-party-adapter, inclusion, compatibility-certification, endorsement, or security-certification claim; isolation remains dependent on the selected Kubernetes runtime and deployment configuration.

The Awesome DSH Plugins issue #17 clarifies the SandBase Harness distribution identity in the directory's Hold Queue. The verification comment distinguishes the repository/runtime, official MCP Registry identity, canonical server.json, and pinned OCI bridge from the unrelated unscoped managed-agents npm package (comment). It explicitly accepts retaining the conservative hold if a unique npm package name is required; no trust-score upgrade, inclusion, endorsement, or security certification is claimed.

To improve the next source-indexed result, agent-plugin/plugin.json now declares the implemented discovery terms agent-plugin, persistent-sessions, audit-replay, and credentials in addition to its existing runtime/MCP/sandbox terms, and records plugin patch version 0.1.1. The manifest validates against the Agent Plugins 1.0 schema and the MCP distribution test suite remains green; this change does not claim a refreshed directory page until its pinned revision changes.

Promotion rules

• Verify the URL and page content before adding an entry.
• Keep pending submissions separate from public listings.
• Prefer useful setup guides, reproducible examples, and source-backed fixes.
• Never buy or manufacture stars, reviews, votes, or engagement.
• Do not claim official endorsement from a directory or upstream project.