feat: flesh out OpenClaw websocket mock across the operator API#11
Merged
Conversation
e75e432 to
099a667
Compare
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.
Expand the OpenClaw Gateway websocket mock from a handful of methods to the full operator-facing API, split by domain.
Summary
req/res/eventframes that echo the request id.mainagent andmainsession, three models, one cron job, one task, one artifact and one connected channel account; reads return this snapshot, writes are acknowledged, and unmocked methods return amethod_not_founderror frame.*-config.yamlfiles (sessions, chat, agents, cron, tools, channels, tasks, system) plus a connection core, with matching payload files.deltaTextfield and expandhello-okto advertise the full method set.Implementation details
Method payload shapes are taken from the OpenClaw gateway protocol schemas rather than invented. A few results are not pinned by the wire schema (e.g.
sessions.list,sessions.usage,cron.status); those use representative shapes consistent with the reference client, noted in the README.Splitting relies on the engine coalescing multiple
plugin: websocketconfigs onto one connection (imposter-project/imposter-go#95); until that lands, an engine build including it is required.