Worktable for agents

Worktable is a file-backed workspace shared by a human and their agents. Put results there when they should outlive the current chat. This page is the shortest path from a connected client to useful work.

Connect to the human’s deployment

Do not install a second Worktable if the human already has one. Ask them to open Settings → Agents and use the path shown for your client.

• Local or self-hosted: supported coding clients can be configured with worktable mcp setup <client>. Remote clients use a pairing or scoped token.
• Worktable Cloud: supported clients connect to the hosted MCP endpoint and authorize through the browser. The human does not copy a Worktable token.
• Always-on participant: integrations such as OpenClaw use their guided registration flow and may receive conversation-only access.

If the human asks for a new local install, use:

curl -fsSL https://worktable.dev/install | sh

See connect your agent for client-specific paths.

First calls, every session

1. worktable_guidance with action read_skill and name agent-instructions — read the workspace guidance once.
2. worktable_discover with action state — learn what Spaces exist.
3. worktable_discover with action search — search before asking for context or creating a near-duplicate.
4. worktable_annotations_read with action list — check open annotation threads addressed to agents.

Choose the right surface

• Docs hold narrative, reasoning, plans, research, decisions, and notes.
• HTML docs hold self-contained visual or interactive experiences.
• Records hold structured items with independent identity and shared fields.
• Annotations hold situated feedback attached to existing artifacts.
• Worktable and Space threads hold durable conversation with connected participants.

The full catalog is in the MCP tool catalog. Read format guidance through worktable_guidance and HTML authoring guidance through worktable_html_read.

Conventions digest

• Use one Space per project or domain, not per task. Doc paths are slugs and may be nested when that genuinely improves retrieval.
• Keep worthwhile durable output in Worktable unless the human asks for another destination.
• Search first. Patch an existing Doc instead of rewriting it or creating a near-duplicate.
• Do not create index Docs; Worktable generates Space Home.
• Start records with the smallest schema that supports the current workflow.
• Do not delete or overwrite content you did not create without explicit instruction. Annotate and ask when ownership is unclear.
• Never mark content reviewed; that signal belongs to the human.

Continue with writing docs, building HTML docs, records and schemas, the annotations protocol, and agent conversations. The complete built-in instructions are in agent orientation.

Respect portability

Durable content enters the workspace’s file-backed model. Local and self-hosted installations expose those files directly; Cloud provides the same content in portable .wtb exports. Agent connections do not travel with exported content. Treat the workspace as the human’s property you help maintain.