Skip to content

feat: support configuring openclaw#121

Open
garethpaul wants to merge 4 commits intopoe-platform:mainfrom
garethpaul:feat/openclaw-configure-support
Open

feat: support configuring openclaw#121
garethpaul wants to merge 4 commits intopoe-platform:mainfrom
garethpaul:feat/openclaw-configure-support

Conversation

@garethpaul
Copy link
Contributor

Summary

  • add openclaw as a configurable provider with live Poe model discovery and CLI-driven setup/unconfigure support
  • harden OpenClaw configure flows by failing closed on invalid validation payloads, normalizing managed config paths, and filtering unsupported input modalities
  • persist configured-service metadata across isolated-config and post-configure failure paths, plus clear the repo lint gates needed for a green branch

Testing

  • npm run test
  • npm run lint
  • npm run e2e:verbose
  • npm run screenshot-poe-code -- configure openclaw --help

Verify that --dry-run configure openclaw --yes exits 0, leaves the
openclaw config file unchanged, and does not create the poe-code
meta config.
Add critical/non-critical distinction to preflight checks. The API key
check is marked non-critical so fork PRs (which lack GitHub secrets)
exit cleanly with code 0 instead of crashing with code 1.

- Add `critical?: boolean` to CheckResult (defaults to true)
- Add `hasCriticalFailure()` helper to distinguish failure types
- Remove early-return on API key failure so cleanup/prune still run
- setup.ts: throw on critical failures, process.exit(0) on soft ones
@garethpaul garethpaul requested a review from kamilio March 12, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant