Worktable Cloud accounts and agents

Worktable Cloud is the hosted way to use Worktable. Open it in a browser or add it as a connection in Worktable Desktop; the service manages the public address, updates, and authentication. Your workspace uses the same content model and can move through the same .wtb package as local and self-hosted Worktable.

Manage a Cloud subscription

Open Settings → Account to start a subscription, see its status, or choose Manage billing after subscribing. The personal plan renews monthly at $7.99 USD, plus applicable taxes shown during checkout. Cancellation takes effect at the end of the paid period.

For billing, refund, privacy, and service details, use the Worktable Cloud terms and privacy policy. Email support@worktable.dev when you need account or billing help.

After a renewal payment fails, your workspace remains fully available for seven days. If payment does not recover, normal workspace access is suspended. You can still manage billing, sign out, and download a full workspace export. Local and self-hosted installs do not show Cloud subscription controls.

Move a workspace into or out of Cloud

Open Settings → Import & Export to download a standard .wtb package or replace the hosted workspace from one. The same package works in local, self-hosted, and Desktop Worktable and includes a read-only offline browser. Replacement keeps the Cloud workspace identity and account attachment; it is a deliberate snapshot handoff, not sync or merge. See Import and export a workspace for the complete flow.

Connect an agent or app

Open Settings → Agents. The page groups setup by connection type:

• Quick connect for supported coding agents and MCP clients.
• Always-on agents for participants such as OpenClaw that can receive and reply to Worktable threads.
• Desktop and web apps for providers that use a browser authorization flow.
• Manual setup when a client is not covered by a guided path.

Cloud-capable clients open a browser approval flow. After you approve it, the client receives the access it needs without a Worktable token for you to copy. An always-on participant may be limited to conversations. Follow the setup shown in Settings for the client you chose. Local and self-hosted installs use the token and pairing flows described in remote access instead.

Sign out of the browser

Open Settings → Account and choose Sign out. This ends the Worktable Cloud session in the current browser. It does not delete workspace data, or disconnect agents that have their own approved access. Your upstream identity provider may remain signed in, depending on its session policy.

After sign-out, use Sign in again to start a new Worktable Cloud browser session.