OpenClaw
meshpoint connect openclawwrites a dependency-free hook pack (package.json with openclaw.hooks: ["."], HOOK.md, handler.js) and installs it with openclaw plugins install <dir> --force. The handler runs meshpoint tap openclaw per event, so the Gateway host needs the meshpoint CLI on its PATH and a login. Restart the Gateway after installing.
meshpoint connect openclaw --remove disables the hook and deletes the pack (OpenClaw’s plugins uninstall does not handle hook packs). Restart the Gateway afterwards.
Events
Section titled “Events”| OpenClaw event | What happens |
|---|---|
agent:bootstrap |
Adds team knowledge, the last checkpoint and active teammates to the bootstrap context as a virtual MESHPOINT.md. Cached per session for 15 minutes, because bootstrap fires on every run. A pending checkpoint nudge is appended here. |
message:received |
Captures the inbound message as the user turn. |
message:sent |
Captures the reply as the assistant turn and counts it toward the checkpoint. |
command:new, command:reset, session:auto-reset |
Send the spool and forget the session. |
OpenClaw exposes no transcript to hooks, so the tap keeps its own record of reply counts per session under ~/.local/state/meshpoint/openclaw-replies/. Events of one conversation are tied together by sessionKey; message events carry no session id.
Chat agents have no repository
Section titled “Chat agents have no repository”A Gateway agent usually has no git checkout, so set the project explicitly in the Gateway’s environment:
MESHPOINT_PROJECT=github.com--acme--web # [A-Za-z0-9._-], up to 128 charsMESHPOINT_BRANCH=main # optional, default mainWith a systemd user service, a drop-in works:
[Service]Environment=MESHPOINT_PROJECT=github.com--acme--webEnvironment=MESHPOINT_BRANCH=mainEnvironment=PATH=/home/you/.local/bin:/usr/bin:/bin:/home/you/.npm-global/binthen systemctl --user daemon-reload && systemctl --user restart openclaw-gateway.service. With neither a git workspace nor MESHPOINT_PROJECT, the hook does nothing. Recall is branch-scoped, so MESHPOINT_BRANCH must match the branch the items were written on.
The skill
Section titled “The skill”The nudge asks for the meshpoint skill, which this adapter does not install: OpenClaw skills live in the agent’s workspace. Add the skill there if you want the chat agent to write items on its own; otherwise the nudge is a reminder for a person.
openclaw agent -m "..."firesagent:bootstrapbut notmessage:received; add--deliver --channel <ch> --to <id>to exercisemessage:sent. Real inbound captures need a message through a channel.- Gateway logs are in
/tmp/openclaw/openclaw-<date>.log(oropenclaw logs), not journald. - A new item written elsewhere shows up in a session’s bootstrap after the 15-minute cache expires, or at once in a new session.
