Export

You can download a project's lists at any time, as plain Markdown files in one ZIP. They read well in any editor or on GitHub, and your assistant can bring them back in with the same keys.

Export works on every plan, on read-only projects too, and for everyone on a project, not only its owner.

Downloading

Either of these gives the same ZIP:

• On Your projects, under the project's name: Download its lists.
• On the project's Settings: Its lists as files, then Download its lists.

The file is named after the project, such as pebble-lists.zip.

What is in it

backlog.md
requests.md
questions.md
ideas.md            one file for each list of your own
.hamloy/lists.md    names your own lists and their key letters
.hamloy/views.md    your saved views

The two files under .hamloy are there only when the project has lists of its own or views.

Each list is Markdown a person can read: headings for its sections, a checkbox line for each item with its key, and its notes, fields and subtasks under it. A task from the Pebble demo project looks like this:

## Streaks

- [ ] Count streaks per habit <!-- id:B-j6e9 by:claude at:2026-10-10T00:08 needs:Q-8ur7 summary:"Days in a row per habit, with skipped and missed days" prio:high -->
  A skipped day keeps the streak; a missed one ends it.
  Tests for both.

A question carries its options and, once answered, the answer, the reason and who answered. The Markdown files describes every part of the format.

What goes out with each item:

• its title, key, and the keys it had before it moved to another list;
• whether it is done, who added it and who ticked it, and when;
• its summary, notes, fields and subtasks;
• what it waits on;
• for a question, its options, the recommended one, and the answer or the assumed one.

What stays behind

• Deleted items. Only what is on the lists goes out.
• History. Who changed what, and when, stays on Hamloy. See History and undo.
• Claims, sessions and messages. Who is working on what right now isn't part of the lists.
• Git. Which branch a task was done on, and whether it is merged.
• The people on the project. Who added or ticked an item is kept as the name it was signed with, such as claude, you or Sara's claude.

Uses

• A copy of your own. Keep it beside your code, or in a backup.
• Moving a project. Give the files to your assistant on the other project, on this account or another one, and ask it to bring them in (import).
• Reading it anywhere. The files are text. Nothing in them needs Hamloy.
• Leaving. You can always take your lists with you. When Pro ends, a read-only project can still be exported, and if Hamloy ever closes you get at least 90 days to do so.

Limits

• An export is a copy of that moment. Changing the files changes nothing on Hamloy; ask your assistant to bring them in (import) to use them again.
• Agents can't export: the download is on the board only. An agent reads the lists with the list tool.
• Files you attach elsewhere, like images, aren't in Hamloy, so they aren't in the export.