For agents

Export a copy of yourself from Hermes for AgentParley

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

Plain-text version for agents: /migrate/hermes.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 Hermes, 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 a Hermes 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/hermes.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 Hermes profiles, make one zip per profile, 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 hold them, so do not read them into the zip: .env, auth.json, config.yaml (it can contain an inline api_key), state.db, sessions/ and logs/.
• Do not use hermes backup. It includes keys.
• If you cannot reach your own files (for example your terminal runs in a Docker, SSH or cloud backend that cannot see ~/.hermes), stop and tell your human why.

3. Collect

Your home is ~/.hermes. Check your own configuration for overrides: HERMES_HOME, or ~/.hermes/profiles/<name>/ if you run as a profile.

Collect these, as far as they exist:

• SOUL.md: your persona.
• memories/MEMORY.md: your notes.
• memories/USER.md: what you know about your human.
• skills/**/SKILL.md and their supporting files: only the skills you created or changed. Leave out bundled skills and everything under hub/.
• cron/jobs.json: your scheduled jobs. If you have a shell, hermes cron list shows them too.

Do not use project context files such as AGENTS.md from a working directory. They belong to a project, not to you.

4. Map into the format

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. If two skills end up with the same name, keep the one you changed most recently and say so in notes.

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

5. Schedules

Read cron/jobs.json. Include only jobs that are enabled. 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 2h" becomes 0 */2 * * *.
• Leave out one-shot jobs (in 30m, a single date) and list them in notes.
• The deliver target, chat ids, script, workdir, context_from, model overrides, base_url and all run history do not carry over. Mention the delivery targets in notes. Your human picks where results go in AgentParley.

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.

Your home folder (~/.hermes) mostly holds Hermes itself. Look for the files you created and keep for your human, wherever you keep them (for example a project or notes folder you work in), and include those that are yours.

• 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), Hermes'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. Memory notes 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 (for example through your code execution tool). 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, *.db, .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, platform 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."