Skip to content

Docs

Import

Ask your assistant to bring in the work you kept somewhere else, a TODO file, a plan, notes, issues or another tool's lists, at once.

Your assistant brings your work into Hamloy, from wherever you kept it until now: a TODO.md, a plan, notes, a checklist in the README, issues, comments in the code, or another tool's lists. There is no file to upload. Connect your assistant to a project, then ask it.

Bringing your work in

  1. Connect your assistant to the project; see Projects.
  2. Ask it, in your own words: "Bring my TODO.md into Hamloy", or "Move our plan into Hamloy".

Each repo's work goes into its own project. For several repos, connect each one and ask your assistant there.

On a project with nothing in it yet, your assistant offers this by itself. Hamloy tells it to look for how the work was kept until now and ask you first.

It reads what you have and makes one call with the import tool. That brings in everything at once:

⏺ hamloy - Bring in work kept elsewhere (MCP)(lists: {"task": "## Shop\n- [ ] Put the prices up …", "question": "- [ ] Which colour? …"})
  ⎿  brought in 6 tasks, 2 requests, and 1 question, with 2 subtasks (3 done)
     The list tool shows them, in Bakery. This work lives here from now on: keep it here, not in the old place. If it came from a file or another tool, tell the human, and ask whether to delete the old file or leave one line in it saying the work moved to Hamloy, so no one keeps using it.

The board shows the new items at once, and its history says who brought them in.

What comes across

  • Headings become headings. One with the name of a heading the list has already is that heading.
  • Tasks, requests and questions go to their own lists. Groups of items become headings. For a list of your own, like ideas, ask for it; your assistant makes it first.
  • The same work found in two places, say a README checklist and an issue, is one item: your assistant gives it once.
  • Done stays done, with when, if the source says.
  • Notes, subtasks and fields, such as a priority, come with the item.
  • Questions keep their options, the recommended one, and their answers. Your assistant is told which came in with none recommended.
  • What waits on what is kept, by the ids the source used or by the keys already in Hamloy.
  • Who did it. Your own work and your assistant's come in as yours and your assistant's. Someone from another place comes in as you.

History, claims and messages from the old place don't come.

Into a project with items already

An import can add to a project you already use. An item its list already has, by its title, is left out, and the reply names it. Bringing the same file in twice adds nothing the second time. An item whose key is already taken gets a fresh one.

Whole or not at all

Either everything comes in, or nothing does, and your assistant is told why, for example:

Nothing was brought in: its items wait on each other in a circle (B-aaaa waits on B-bbbb waits on B-aaaa), so none of them would ever be free.

Other reasons: an item waits on one that isn't there; the same item is given in two lists; a list's text isn't text, has an unfinished git merge in it, or holds no items; a title, notes or field is longer than the tools allow (every one is named at once); more than 2,000 items at once.

Afterwards

Hamloy's lists are where the work lives from now on. Your assistant stops writing to the old place. You can delete the old file, or keep it for what belongs with the code, like a roadmap you publish.

An export of a Hamloy project comes back the same way: give your assistant the ZIP's files and ask it to bring them in.