Repository navigation
[RefImpl] OpenClaw host adapter #287
Description
Target runtime or language
OpenClaw (TypeScript plugin)
What this proves
An OpenClaw plugin that puts any OpenClaw agent under an ACS Guardian:
- ACS on a messaging agent host, not only on coding agents. Each run has a real sender, so the Guardian decides per person.
- Every step OpenClaw runs goes to the Guardian, signed per §10, and the plugin applies the decision.
- One adapter for any ACS Guardian that signs per §10, proven on both: Go (Add a Go Guardian reference implementation #169) and TypeScript (fix(agt): implement ACS-Core wire safeguards #229).
- Lives in the shared host-adapter area from Align expectations for Guardian reference implementations (#252) #256, at
adapters/openclaw/.
On 12 Oct I discussed with @artmaro on Slack that I take this one.
Do you intend to implement this yourself
Yes, I want this assigned to me
Current Priority Scope
Feeds the runnable Guardian reference implementation
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
Lrd0036 commentedon Oct 19, 2026
I think this is a reasonable adapter request, however I'm unsure how to prevent ourselves from getting stuck in constant adapter creep.
How do we control the scope of... what adapters do we want to include and how do we prevent it from getting out of control?
Hermes, Openclaw, Antigravity, Opencode, etc? Also, once we continue to expand into these... what happens when said coding agents make updates that render the ACS incompatible?
Do we prioritize the most commonly used coding agents? I am unsure.
Anyways, proceed. Thank you for the proposition @President!