MyInc gives you your AI crew first. OpenClaw stays an optional advanced path.

OpenClaw migration guide

Cloud-safe AI crew, no terminal-first setup

Meet your crew first. Keep OpenClaw as an advanced input path.

Your crew 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 AI crew with a self-managed gateway workflow.

Meet JadeOptional setupGet API keyOpen install guide

No terminal-first setup

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

Start from the app

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

Your crew remembers across sessions

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

OpenClaw stays optional

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

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

Crew memory

MyInc gives your crew memory before it gives you infrastructure.

Instead of running a gateway first, start with a crew that can use saved context. Your crew 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 crew memory.

Clips become memory units

Each saved exchange becomes a reusable unit your crew 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

Your crew 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 + MyInc

Want the no-install path first?

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

Optional OpenClaw setup

Optional OpenClaw setup

Use this only if you already run OpenClaw and want those conversations to feed your crew’s memory.

Install the MyInc plugin

Get your API key

Paste the config into OpenClaw

Restart the OpenClaw gateway

Minimal config
{
  "apiUrl": "https://myinc.app",
  "apiKey": "tk_your_key_here"
}

FAQ

FAQ

What is the difference between OpenClaw and MyInc?

OpenClaw is a self-managed agent gateway. MyInc gives you a hosted AI crew with memory, drafts, and approval workflows.

Should I install OpenClaw before trying MyInc?

No. Start with your crew 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 MyInc?

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 + MyInc

Start with your crew. Add OpenClaw only when it earns its place.

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