Repository navigation
Description
What Problem This Tracks
Babelfish can translate many external plugin contributions using OpenClaw's existing public plugin SDK. Several remaining compatibility gaps cannot be implemented faithfully inside Babelfish because the relevant behavior is owned by OpenClaw, or because OpenClaw already has an internal bundle implementation that should be exposed rather than duplicated.
OpenClaw Public Seams Needed
- Imported agent profiles: a public registration contract for named agent definitions with model selection, tool allow/deny policy, turn limits, memory, background mode, and workspace isolation.
registerAgentHarnessrepresents an entire runtime and is not an appropriate mapping for one imported agent definition. - Approval-boundary hooks: a public hook that fires when an interactive tool approval is about to be shown and can allow, deny, rewrite, or return a durable permission decision. Pre-tool policy can deny but cannot faithfully approve or update approval rules.
- Bundle LSP projection: a public way for a native plugin to contribute bundle-derived LSP defaults. OpenClaw already supports Claude bundle LSP configuration internally; Babelfish should reuse that owner instead of launching a second LSP implementation.
- Bundle settings projection: a public way to contribute validated bundle settings/defaults, including the supported Claude
agentandsubagentStatusLinesettings. This should reuse OpenClaw's existing bundle settings merge behavior. - Connector registry: a public connector registration and authentication contract before Codex app connector IDs can be mapped. Connector IDs must not be treated as MCP endpoints.
- Host notification events: a generic notification lifecycle event before Claude
Notificationhooks can be mapped without producing false events from unrelated message delivery.
Better Delegated To OpenClaw
- Marketplace resolution and lifecycle: OpenClaw already owns bundle installation and Claude marketplace resolution, including source policy, caching, updates, enable/disable state, and managed restrictions. Babelfish should eventually delegate or forward to that infrastructure instead of implementing a second marketplace manager. Equivalent Codex or Hermes resolvers should also plug into the OpenClaw install owner when those ecosystems have stable marketplace contracts.
Why These Should Not Be Approximated In Babelfish
Approximations would either execute behavior at the wrong lifecycle boundary, bypass OpenClaw policy and authentication ownership, duplicate internal bundle loaders, or expose source capabilities with materially different security semantics. Babelfish should keep unsupported contributions visible until a stable host contract exists.
Desired Outcome
Add generic public SDK or manifest projection contracts for the capabilities above, then migrate Babelfish mappings to those contracts. The APIs should remain source-format-neutral so Codex, Claude Code, Hermes Agent, and future clients can share them.
Evidence
- Babelfish support matrix documents the affected
NoandPartialsurfaces. - OpenClaw already contains internal Claude bundle LSP/settings and marketplace behavior, but these are not dynamic public native-plugin registration surfaces.
- OpenClaw pre-tool policy and agent harness APIs do not represent approval dialogs or individual imported agent profiles.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Jul 13, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed August 2, 2026, 3:11 PM ET / 19:11 UTC.
Summary
Keep open. Current
maindeliberately detects these imported-plugin surfaces, preserves them as unsupported, and warns at runtime; the requested source-neutral OpenClaw contracts remain unimplemented. This MEMBER-authored, security-sensitive umbrella needs a maintainer-sponsored host API and trust-boundary decision before Babelfish work can be safely scoped.Reproducibility: not applicable. this is a request for new host SDK contracts, not a report of broken established behavior. Current source and documentation consistently show that the named surfaces are intentionally detected and reported as unsupported.
Ways to help us reproduce this
Maintainer decision needed
Why: The issue combines new public API direction with approval, authentication, model, and execution trust boundaries; repository policy requires confirmation before manifest-contract changes, and Babelfish cannot safely choose those host semantics itself.
Next step
A maintainer must choose public host API and trust-boundary direction before the umbrella can be split into safe, implementable work.
Review details
Best possible solution:
Keep the unsupported surfaces visible while OpenClaw sponsors narrow, source-neutral public contracts with explicit authorization and lifecycle semantics, then migrate each Babelfish mapping only after its host contract is approved and tested.
Do we have a high-confidence way to reproduce the issue?
Not applicable: this is a request for new host SDK contracts, not a report of broken established behavior. Current source and documentation consistently show that the named surfaces are intentionally detected and reported as unsupported.
Is this the best way to solve the issue?
Unclear: exposing a source-neutral contract is the right general direction, but the issue combines several lifecycle and security models that need separate host-owned API decisions before implementation.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning high; reviewed against b5c42c46da2c.
Label changes
Label justifications:
P2: This is a meaningful compatibility and platform-design gap, but current behavior keeps the unsupported surfaces visible instead of causing an active outage.impact:security: The requested approval, connector, authentication, model, and execution seams directly define plugin trust boundaries.Evidence reviewed
What I checked:
README.md:95, 5e2ccd634980)src/bundle-plugins.ts:372, 5e2ccd634980)src/index.ts:103, 5e2ccd634980)v0.1.0, whose tag points to the release commit; currentmainis later atb5c42c46and does not provide a released or main-only implementation of the requested host contracts. (CHANGELOG.md:10, b5c42c46da2c)AGENTS.md:30, b5c42c46da2c)Likely related people:
v0.1.0release commit that introduced the compatibility matrix and the current unsupported-surface behavior. (role: introduced the released compatibility boundary; confidence: high; commits: 5e2ccd634980, 807a7c54e76f; files:README.md,src/index.ts,src/bundle-plugins.ts)main, making them a relevant routing contact for any later hook-execution integration. (role: recent adjacent runtime contributor; confidence: medium; commits: b5c42c46da2c; files:src/index.ts)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.1 remaining item