Skip to content

(feat) move client out of internal. this create a gocrawl client library#29

Open
bclermont wants to merge 3 commits into
nextlevelbuilder:mainfrom
bclermont:feat/client-lib
Open

(feat) move client out of internal. this create a gocrawl client library#29
bclermont wants to merge 3 commits into
nextlevelbuilder:mainfrom
bclermont:feat/client-lib

Conversation

@bclermont

Copy link
Copy Markdown

internal/ can't be imported, and I rather use this library than re-implement it from scratch

Bruno Clermont added 3 commits June 25, 2026 18:45
…thods

Extended the WS client to cover chat, sessions, agents, config, skills, and
cron method groups with correct request/response shapes verified directly
against the current goclaw server handlers, including several field-naming
corrections beyond the agent_key/session_key rename from PR nextlevelbuilder#30.
…and config.patch shape

WS RPC calls in cmd/*.go still sent legacy snake_case fields (agent_key,
session_key) that the gateway no longer accepts (it expects agentId/
sessionKey), and config.patch/apply sent {key,value} instead of the real
{raw,baseHash} JSON5-diff contract. Migrated call sites to the typed
client wrappers (ChatSend/ChatHistory/ChatInject/ChatSessionStatus,
SessionsCompact/SessionsReset, AgentWait, Cron*, Config*) so the wire
shape matches internal/gateway/methods on the server, and updated tests
to match the corrected contracts.
@bclermont

Copy link
Copy Markdown
Author

I improved this PR to fill the missing coverage of goclaw server API

@bclermont

Copy link
Copy Markdown
Author

I suggest we create a new repository: gocrawl-client and I move that logic there and switch the CLI to it. and I'm refactoring the MCP server to use that client library as well

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