docs: define external harness adapter boundary#181
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR clarifies the intended boundary between Coven’s daemon and external integrations by documenting OpenClaw as an external ACP runtime bridge (via @opencoven/coven) rather than a daemon-owned harness, and by reinforcing that new harnesses should enter through the generic adapter contract (not daemon special-cases).
Changes:
- Adds a new docs page describing the OpenClaw bridge integration model and responsibilities split.
- Updates harness docs/navigation to include the OpenClaw bridge and depict it in the architecture diagrams.
- Tightens adapter guidance to emphasize a harness-neutral adapter contract and an “external adapter first” rule.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/openclaw-coven/README.md | Strengthens guidance on future harness mapping and avoiding daemon special-cases. |
| docs/harnesses/openclaw.md | New page documenting OpenClaw as an external bridge via @opencoven/coven. |
| docs/harnesses/index.md | Adds OpenClaw bridge to harness navigation and diagrams. |
| docs/HARNESS-ADAPTERS.md | Reframes adapter guidance around a generic, harness-neutral contract and maturity steps. |
| docs/FUTURE-HARNESSES.md | Updates future-harness notes to link OpenClaw bridge and emphasize “external adapter” framing. |
| docs/docs.json | Adds the OpenClaw harness doc to the documentation nav structure. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| `allowFallback` defaults to `false`. Enable it only when you intentionally want failed/unavailable Coven launches to fall back to another ACP backend such as `acpx`. | ||
|
|
||
| By default, the plugin only maps OpenClaw ACP agent ids for the current Coven v0 scope: Codex and Claude Code. Future harness ids must be explicitly configured in `harnesses` after the Rust daemon supports and validates them. | ||
| By default, the plugin only maps OpenClaw ACP agent ids for the current Coven v0 scope: Codex and Claude Code. Future harness ids, such as Hermes, must be explicitly configured in `harnesses` after the Rust daemon supports and validates them through the generic adapter contract. Do not add special-case OpenClaw or Hermes logic to the daemon. |
Comment on lines
+69
to
+71
| config: { | ||
| covenHome: "~/.coven", | ||
| }, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- clarify that harnesses should follow a generic external adapter boundary instead of becoming hardcoded daemon special cases\n- document OpenClaw as the first external integration through the @opencoven/coven bridge\n- add OpenClaw bridge docs to the harness navigation and tighten plugin README guidance for future harnesses like Hermes\n\n## Verification\n- git diff --check\n- python3 -m json.tool docs/docs.json