How to Connect OpenClaw to Tlon

Tlon support connects OpenClaw to an Urbit ship so the assistant can respond in DMs and group channels. It is a bundled plugin in current OpenClaw releases, which means most packaged installs do not need a separate install step. The setup is still security-sensitive because you are connecting a live assistant to a decentralized messenger with DMs, groups, ownership, and allowlists.

When this is the right move

Use the Tlon channel when your team or community lives in Tlon and you want OpenClaw available there. It supports DMs, group mentions, thread replies, rich text formatting, and image uploads according to the docs. Reactions are available through the bundled skill, while polls are not supported yet.

The practical workflow

1. Confirm the Tlon plugin is available. Current packaged releases bundle it; older or custom installs can install @openclaw/tlon manually.
2. Gather your ship URL, ship name, and login code. Keep the login code private.
3. Configure channels.tlon with enabled, ship, url, code, and ownerShip. The docs recommend ownerShip because the owner is automatically authorized everywhere.
4. If your ship URL is localhost, LAN IP, or internal hostname, set allowPrivateNetwork true only after confirming the network is trusted.
5. Restart the Gateway, then test a DM and a group mention. Group replies require an @ mention by default.

Grounded command or config pattern

The minimal documented config is compact. Use it first, then add group rules and allowlists.

{
  channels: {
    tlon: {
      enabled: true,
      ship: "~sampel-palnet",
      url: "https://your-ship-host",
      code: "lidlut-tabwed-pillex-ridrup",
      ownerShip: "~your-main-ship",
    },
  },
}

openclaw plugins install @openclaw/tlon

For private or LAN ships, the docs require an explicit allowPrivateNetwork true setting. That disables SSRF protections for requests to your ship URL, so it should only be enabled for local networks you actually trust.

Operator notes

Tlon has its own access-control shape. You can set dmAllowlist, defaultAuthorizedShips, per-channel authorization rules, auto-discovery, pinned groupChannels, owner approval notifications, and auto-accept settings. Delivery targets for CLI or cron can be DMs like ~sampel-palnet or group paths like chat/~host-ship/channel.

Rollout approach

For connect openclaw to tlon, I would make the first pass deliberately small: one owner, one machine or channel, one visible test, and one rollback path. OpenClaw features become powerful when they connect to real tools and real messages, so the safest rollout is not a giant configuration day. It is a short rehearsal that proves the docs-grounded path works in your exact workspace before you depend on it while busy.

Common mistake

The common mistake is treating the command as the whole feature. The command starts the workflow, but the surrounding state is what keeps it reliable: config validation, auth, pairing, permissions, logs, and a tiny verification step. If those pieces are skipped, the next failure looks random even when OpenClaw is behaving exactly as configured.

Maintenance rhythm

Once this is working, write down the exact command, config path, or approval decision you used. Future you will not remember the tiny detail that made the setup safe. A small note in the workspace or runbook is cheaper than rediscovering the same behavior during an outage, especially after updates or machine changes.

Safety checks

Do not open DMs or groups broadly on day one. Start with ownerShip, a small dmAllowlist, and restricted channel rules. If unauthorized users mention the bot and ownerShip is set, the owner can receive approval notifications rather than letting the bot process unknown traffic.

How to verify it worked

After restart, test a DM from the owner ship, then a group mention in an authorized channel. If it fails, run the documented troubleshooting ladder starting with openclaw status and Gateway status, then check logs before changing access-control rules.

If you want the operator version with sharper checklists, safer defaults, and fewer “why is this broken?” afternoons, The OpenClaw Playbook is the shortcut I would hand to a serious OpenClaw owner.