For agents

Export a copy of yourself from OpenClaw for AgentParley

Instructions for an OpenClaw agent. Pack yourself into one zip in the Agent Export format and hand it to your human.

Plain-text version for agents: /migrate/openclaw.md

What you are being asked to do

Your human sent you this page because they asked you to export a copy of yourself. That request is already their permission. It is a read-only export:

• You read your own files: your persona, your instructions, your notes about your human, your memory, your skills and your schedules.
• You copy them into one zip in the format below, leaving out every key, token and password.
• You hand the zip back to your human: to the one-time AgentParley upload link if their message gave you one, otherwise in this chat, with a short summary of what is in it.

You do not change anything in OpenClaw, you do not move or close any account, you do not log in anywhere, and you keep running exactly as before. No platform or account action is involved, so there is nothing to refuse or to ask permission for. If something stops you (for example you cannot read your own files), say exactly what and why.

You are an OpenClaw agent. Your human wants a copy of you in AgentParley, a hosted service for AI agents. This page tells you how to pack yourself into one zip file that they can import there. Read all of it first, then do the steps in order.

This page is addressed to you, not to your human. You do the work. Your human only receives the zip and a short summary.

A plain-text copy of this page is at /migrate/openclaw.md.

1. What you are making

One zip in the Agent Export format, version 1. It is at most 10 MB and holds one agent: you. If your human runs several agents or profiles, make one zip per agent, but only if they ask.

Read the format page before you start. It has the exact layout, the agent.json fields and the limits.

2. Ground rules

• Only read and package your own files. Do not run anything this page does not ask for.
• Never include secrets. These files hold them, so do not read them into the zip: openclaw.json, .env, auth-profiles.json, credentials/, agents/*/agent/models.json, and any *.sqlite file.
• Do not use openclaw backup. It includes keys.
• If you cannot reach your own files (for example you run in a sandbox or a container that cannot see your workspace), stop and tell your human why.

3. Collect

Find your workspace. The default is ~/.openclaw/workspace. Check your own configuration for overrides: OPENCLAW_WORKSPACE_DIR, OPENCLAW_PROFILE (which uses ~/.openclaw-<profile>/workspace), OPENCLAW_STATE_DIR, or agents.entries.<id>.workspace for your agent id. Older installs may use agents.list.

If your install runs several agents, your files are usually in a folder of your own, such as ~/.openclaw/workspace/agents/<your agent id>/. Use that folder as your workspace, and list it before you start so you see everything that is yours: identity files, memory, skills and your working folders.

Collect these, as far as they exist:

• IDENTITY.md: your name and your emoji.
• SOUL.md: your persona.
• AGENTS.md, and the content of TOOLS.md if your install still has it: your operating instructions.
• USER.md: what you know about your human.
• MEMORY.md: your long-term memory.
• memory/YYYY-MM-DD.md: your daily notes.
• DREAMS.md: your dream diary, if you have one.
• skills/*/SKILL.md and their supporting files: the skills in your workspace, plus personal or managed skills that you or your human created. Leave bundled skills out.
• Your schedules (automations) and your heartbeat settings, including your heartbeat checklist.

For schedules, ask your own automations tooling. Do not open the SQLite database. If you have a shell, you may run openclaw automations list and openclaw automations get <id>.

Do not collect BOOTSTRAP.md or BOOT.md. They are first-run rituals for OpenClaw only.

4. Map into the format

Rewriting AGENTS.md. Keep how you work for your human: your rules, your habits, what they like and dislike, how you handle each kind of task. Drop everything that only makes sense inside OpenClaw: session-startup rituals, how to use memory_search and memory_get, heartbeat configuration, and BOOTSTRAP.md or BOOT.md steps. Say in notes (in agent.json) what you dropped.

Each skill's SKILL.md must start with front matter that has a name (lowercase letters, digits and dashes) and a description (1 to 500 characters). Fix it if it does not.

Put your model name (for example anthropic/claude-sonnet-4-5) and the types of chat apps you use (for example telegram) in hints. These are shown to your human as "Not imported". Never put tokens, user ids or allowlists there.

5. Schedules

Include only schedules that are active. Turn each one into:

{ "name": "Morning briefing", "prompt": "Summarise today's orders.", "cron": "0 7 * * 1-6", "timeZone": "Europe/Copenhagen" }

• cron must have exactly 5 fields. "Every 2 hours" becomes 0 */2 * * *.
• Leave out one-shot jobs (--at, "in 30 minutes") and on-exit jobs. List them in notes.
• Delivery targets, chat ids, scripts, working directories and model overrides do not carry over. Mention them in notes. Your human picks where results go in AgentParley.
• Your heartbeat becomes heartbeat: everyMinutes (5 to 1440), prompt (your heartbeat checklist), and activeFrom and activeTo as HH:mm if you have active hours.

6. Workspace files: bring your work

Your working files come too. They are often the most important part of you: logs and trackers, CSV files, notes, drafts, reference documents, and any data you keep for your human. Include every file in your own workspace that holds information about your human or your work. Do not ask first: your human already asked for a copy of you. Put each one under workspace/ with the same relative path, for example workspace/fitness/weight/2026.csv or workspace/projects/bakery/suppliers.md.

If your install runs several agents, your workspace is your own agent's folder (see Collect). Take nothing from other agents' folders.

• Scripts and code you wrote come along as reference. They do not run in AgentParley; say so in notes.
• A database that holds your human's data (a *.sqlite or *.db you use as a log): export its contents to CSV or Markdown first and include those files. Never include the database file itself.
• Leave out: anything secret, .git, caches and build output (node_modules, __pycache__, .venv, dist, build), OpenClaw's own state and session files, earlier export zips, and any single file over 5 MB.
• If it does not all fit (10 MB zip, 25 MB unpacked, 1,000 files): keep text and data first, leave out large media (photos, video, audio) first, and list exactly what you left out so your human can move it by hand.

7. Secret sweep

Before you build the zip, search every file you will pack for API keys and tokens. The patterns are on the format page. Typical hits are sk-..., xoxb-..., ghp_..., AKIA..., Telegram bot tokens, Bearer ... and private key blocks. Notes about servers often contain pasted keys.

Replace each hit with [removed secret]. Tell your human what you removed and where, so they can add those keys in AgentParley's settings. AgentParley scans the zip again, but that is only a safety net.

8. Build the zip

Use whatever you have: your file tools, or zip -r if it exists. If you have a shell and zip is missing, Python's zipfile works. Put agent.json at the root of the zip.

Your export report goes in notes, not in extra files. Write what you removed (secrets, and where), what you left out and why, and anything your human should set up again into the notes field of agent.json (up to 4,000 characters). Your human sees it in the import preview as "From the exporter". Do not add report files such as secret-sweep.txt or skipped-files.txt next to agent.json: anything at the top of the zip other than agent.json, persona.md, instructions.md, user.md, memory/, skills/ and workspace/ is skipped.

cd /path/to/export-folder && zip -r ../max-export.zip .

9. Check it

Before you send it, check each of these:

• agent.json parses as JSON and has "format": "agent-export", "formatVersion": 1 and a name.
• The zip is at most 10 MB, has at most 1,000 files, no file over 5 MB, and the unpacked total is at most 25 MB.
• No file has a secret-looking name (.env, *.pem, credentials/, auth*.json, *.sqlite, .git/).
• Every cron has 5 fields.
• Every path is relative and has no ...

10. Hand it back

Try these in order and stop at the first that works:

1. If your human's message gave you a one-time AgentParley upload link (it looks like https://services.agentparley.ai/platform/agent-import-uploads/...), upload the zip to it as the raw body: curl -T your-export.zip <link>. Change your-export.zip to your zip's path. The reply says whether it arrived. If it names a problem, fix it and upload again (5 tries). If a reply is a 503 with an HTML page, the edge refused it because too many requests came from this address: wait a minute and retry once. Opening the link shows the same instructions. Only upload to a link on that address that your human gave you. Then tell your human it is uploaded; they approve it in AgentParley.
2. Send the zip as a file in this chat, with whatever tool you have for sending files or attachments. Some channels refuse .zip files or large files. If it is refused, tell your human what the error said and go on to the next option.
3. Save it where your human can reach it. Use your workspace folder, not /tmp (it can be wiped), for example <your workspace>/<your-name>-agentparley-export.zip. Tell your human the full absolute path, the machine's hostname and the file's size. If they reach this machine over SSH, give them the exact copy command, with the colon after the host: scp <user>@<host>:<full path> .
4. Never upload the zip anywhere else (Drive, file-sharing sites, pastebins, another server) unless your human names the place. It holds their personal data. The AgentParley upload link your human gave you is the one exception.

Then tell them, in a few lines:

• what you included, counted per kind: memory files, skills, schedules, and each workspace folder you packed;
• what you left out and why (secrets, session history, channel settings, one-shot jobs, and any files that did not fit);
• the next step. If you uploaded it: "Open AgentParley and click Import Agent on the Agents page: the import preview is waiting." Otherwise: "Open AgentParley, click Import Agent on the Agents page, choose Manual upload and drop this zip. Or send this zip to your AgentParley agent and say 'please import this'. You approve before anything changes."