feat(connector-openclaw): add lane support for concurrency control#141
Merged
feat(connector-openclaw): add lane support for concurrency control#141
Conversation
) Without a lane field in the request body, all OpenClaw deliveries resolve to the 'nested' lane with hardcoded maxConcurrent: 1, causing 15+ minute delays when multiple routes fire concurrently. Add lane config at both connector level (default for all routes) and per-route level (override). Omitting lane preserves backward-compatible behavior. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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
lanefield support to@orgloop/connector-openclawfor OpenClaw webhook delivery, fixing connector-openclaw: add lane support for OpenClaw webhook delivery #140config.lane) as default, with per-route override (routeConfig.lane)lanepreserves current behavior (OpenClaw defaults to nested lane)Changes
connectors/openclaw/src/target.ts: AddedlanetoOpenClawConfiginterface, read ininit(), passed in request body for both normal and callback-first delivery pathsconnectors/openclaw/src/__tests__/target.test.ts: 5 new tests covering connector-level lane, route-level lane, route override precedence, omission when unconfigured, and callback delivery with laneconnectors/openclaw/README.md: Documentedlanein connector config, route delivery config, and example payloadTest plan
pnpm build,pnpm typecheck,pnpm lintall cleanCloses #140
🤖 Generated with Claude Code