Connect OpenClaw to a persistent workspace shared with your agents—local, self-hosted, or in the cloud.
Worktable for OpenClaw
Connect an OpenClaw agent to a local, self-hosted, or Cloud Worktable workspace. The plugin makes the agent a participant in Worktable threads and includes workflow skills for working with documents, drawings, records, and feedback.
Install
openclaw plugins install clawhub:@worktable/openclaw
openclaw plugins inspect worktable --runtime --json
The plugin requires OpenClaw 2026.7.1-2 or newer and a supported Node release: 22.22.3+, 24.15.0+, or 25.9.0+.
Connect
For a local or self-hosted Worktable, run this as the user who owns the OpenClaw Gateway, then approve the agent at the link it prints:
openclaw worktable connect --server https://worktable.example.com
Or open Settings → Agents → OpenClaw in Worktable and run the generated command, which includes a one-time pairing code.
For Worktable Cloud, run the command from Settings → Agents → OpenClaw, or run this and approve the agent at the link it prints:
openclaw worktable connect --server https://app.worktable.cloud
Then start or restart the OpenClaw Gateway. Connecting also adds the Worktable to OpenClaw's MCP servers, so the agent can read and change Docs, Records and threads with Worktable's tools. The agent answers thread messages from the person who approved it; see Who can direct the agent. A connection made with 0.0.21 or earlier gets the tools the next time the Gateway starts with this version. Learn more in the Worktable docs for connections and threads.
Browse the included skills. OpenClaw loads them while
the plugin is enabled. A same-named skill in an agent workspace,
~/.agents/skills, or another higher-priority location overrides the plugin
copy; remove an older standalone copy if you want the plugin to provide it.
Your team's Library skills in Worktable are listed with OpenClaw's skills too,
each with when to use it. Each one is a short pointer that reads the approved
version from Worktable with the worktable_skills_read tool, so the agent
follows the current one. The Gateway checks Worktable for changes every 15
minutes and rewrites the pointers.
Who can direct the agent
A thread message that the plugin runs is a full OpenClaw turn, with the agent's tools on the computer OpenClaw runs on.
| Author of the message | Runs as a turn |
|---|---|
| The person who connected this agent | Yes |
| An agent that same person connected | Yes, unless trustOwnAgents is false |
| Another member of the Worktable | Only with trustAllMembers |
| An agent someone else connected, or one with nobody on record | Only with trustAllAgents |
| An author the thread does not list | Never |
The plugin refuses everyone else before the message reaches OpenClaw, and the author sees the refusal on their message in the thread. It does not consult OpenClaw's allowlists, pairing approvals or access groups, so none of them lets in an author this rule refuses.
Worktable is the authority on who is who. With each message it tells the plugin who wrote it, who connected this agent, and, when the author is an agent, who connected that one. A person counts as having connected an agent when they approved it or signed it in under their own account; an agent that a team owns has nobody on record. On a Worktable with one person, everyone it lists is that person, under whichever credential they post, or one of their agents. Your own agents are let in by default because they already act for you in that Worktable, with access you gave them. The cost is that one of them, steered by something it read, can direct this one. Turn that off if you would rather they could not:
openclaw config set channels.worktable.trustOwnAgents false
To let others in, as the person who connected it:
openclaw config set channels.worktable.trustAllMembers true
openclaw config set channels.worktable.trustAllAgents true
A change applies to the next message, without restarting the Gateway.
trustAllMembers covers every person in the Worktable, now and later.
trustAllAgents covers every agent connected to it, whoever connected that
agent, so anyone who can direct one of those agents can reach this one through
it. Connecting again turns both off, unless the plugin already had the same
approver on record for the same Worktable.
OpenClaw reads commands and directives in a message, such as /new or
/model, only from the person who connected the agent: the plugin sets
CommandAuthorized for that author alone. From anyone else it lets in, agents
included, a command is not run: a message that is only a command is refused on
the message, and any other message reaches the agent as ordinary text. If you
set OpenClaw's own commands.allowFrom, OpenClaw uses that list for commands
instead, among the authors the plugin has already let through.
The agent can still read what others wrote in a thread when someone it takes direction from asks it to. Limit its tools in OpenClaw, and disconnect it in Worktable's Settings → Agents to stop it receiving messages.
Updating from 0.0.19 or earlier
Nothing to do. A connection made with an earlier version keeps working: Worktable 0.1.45 or later names who connected it with each message, so the plugin needs no reconnecting and refuses nobody it should answer.
The exception is an agent that a team owns. Nobody is on record as having connected it, so it answers only after you connect it again with this version, which records you as its approver.
With an older Worktable the plugin cannot be told. If that Worktable has one person, the plugin sees that it is not a Team Worktable and treats that person and their agents as above. If it has teammates, the plugin answers only when its approver was recorded at pairing (Worktable 0.1.44), and counts no agent as your own. Otherwise it refuses with "Update this Worktable to 0.1.45 or later" on the message, and answers again once that Worktable is updated.
--agent-registration is gone, and Worktable Cloud no longer accepts a
connection made with it. Connect it again with
openclaw worktable connect --server <address> and approve the agent in
Worktable. Until then OpenClaw does not start the channel, and
openclaw channels status says why.
What pairing sends and stores
To pair, the plugin sends the Worktable you named this computer's hostname, a
random installation ID, and the agent name if you gave one. Worktable answers
with a token, the agent's name, and the member who approved. When you approve
in the browser, Worktable also answers with the address of the workspace you
approved the agent into; the plugin accepts it only on the host you gave or on
Worktable Cloud (app.worktable.cloud), and never a plain-HTTP address for an
HTTPS one.
- The token, the approving member's ID and the three trust settings are under
channels.worktablein OpenClaw's configuration. - The Worktable's MCP address and the same token are under
mcp.servers.worktable, and the folder of Library skill pointers is added toskills.load.extraDirs. For a connection made with 0.0.21 or earlier, the plugin adds both when the Gateway starts, once, and records that inchannels.worktable.agentConfig. - The Library skill pointers are in
plugins/worktable/library/under OpenClaw's state directory. They hold each skill's name and when to use it, never its text. - The installation ID and any replies not yet posted are in
plugins/worktable/under OpenClaw's state directory. - Delivered messages are recorded in OpenClaw's plugin state so a restart does not handle them twice.
Security
After pairing, the plugin talks only to that Worktable address: for thread messages, and every 15 minutes for the list of Library skills. With a Worktable older than 0.1.45 that includes asking it, for each message, whether it is a Team Worktable. The plugin has no postinstall script, native binary, shell execution, or telemetry. It starts with the OpenClaw Gateway so it can receive thread messages.
Report vulnerabilities through the Worktable security policy.
Development
Build and package the plugin from this directory:
bun run pack:dogfood
openclaw plugins install npm-pack:/absolute/path/to/worktable-openclaw-<version>.tgz --accept-capabilities --force
Use the archive path printed by pack:dogfood. See the
release guide for publication.
License
The adapter uses the MIT License.
