Thinkly gives you Jade first. OpenClaw stays an optional advanced path.

OpenClaw migration guide

Cloud-safe AI Executive Assistant, no terminal-first setup

Meet Jade first. Keep OpenClaw as an advanced input path.

Jade reads what you save, remembers what you forget, and drafts work for your approval. Use OpenClaw only when you already run advanced local agent flows.

This page is now a migration guide for users comparing a no-install assistant with a self-managed gateway workflow.

Meet JadeOptional setupGet API keyOpen install guide

No terminal-first setup

Start with Jade in the browser. Add OpenClaw later if you need it.

Start from the app

Sign in, capture context from the browser, and ask Jade to turn it into drafts or briefings.

Jade remembers across sessions

Saved clips become pages, topics, and connected memory Jade can reuse when the work returns.

OpenClaw stays optional

Use the plugin or Agent API only when another agent needs to feed Jade from a custom workflow.

Capture -> Jade memory -> Drafts -> Approval -> Optional OpenClaw/API

Jade memory

Thinkly gives your assistant memory before it gives you infrastructure.

Instead of running a gateway first, start with an assistant who can use saved context. Jade keeps useful outputs as reusable memory so drafts stay grounded in what you approved.

Keep useful answers beyond one session

Reconnect old context when the topic comes back

Review drafts before anything ships

Memory graph + topic wiki

This is where saved context becomes assistant memory.

Clips become memory units

Each saved exchange becomes a reusable unit Jade can cite and reuse.

Knowledge graph keeps connections

Topics, clips, and pages stay linked so related context is easier to recover.

Approval keeps trust high

Jade can draft from memory, but you decide what gets published, exported, or sent.

OpenClaw is best treated as an advanced source, not the first product experience.

OpenClaw + Thinkly

Want the no-install path first?

Start with Jade, then add OpenClaw or the Agent API only when a custom agent needs to feed her memory.

Optional OpenClaw setup

Optional OpenClaw setup

Use this only if you already run OpenClaw and want those conversations to feed Jade memory.

Install the Thinkly plugin

Get your API key

Paste the config into OpenClaw

Restart the OpenClaw gateway

Minimal config
{
  "apiUrl": "https://thinkly.pluglab.ai",
  "apiKey": "tk_your_key_here"
}

FAQ

FAQ

What is the difference between OpenClaw and Thinkly?

OpenClaw is a self-managed agent gateway. Thinkly gives you Jade, a hosted AI Executive Assistant with memory, drafts, and approval workflows.

Should I install OpenClaw before trying Thinkly?

No. Start with Jade in the browser. Add OpenClaw only if you already need custom agent input.

When should I use /clip vs /ingest?

/clip is for the latest exchange or a specific answer. /ingest is for links, notes, files, and bulk material.

Where do saved items show up inside Thinkly?

They land as clips first, then connect into topics, pages, graph views, and topic wiki workflows.

Do I need an API key before installing?

You can install first, but the plugin becomes useful once you create an API key and add it to the config.

OpenClaw + Thinkly

Start with Jade. Add OpenClaw only when it earns its place.

Get the hosted assistant first, then connect advanced inputs when the workflow actually needs them.