Let your AI assistant fill the backlog for you
Plan a project in chat with Claude or your editor, and have it create the projects and tasks in UnaTask directly. No copy and paste from idea to backlog.
The UnaTask team, Building UnaTask. May 27, 2026. 4 min read.
Cleo just spent forty minutes with an AI assistant planning a launch. It was genuinely good: the assistant broke the launch into phases, suggested tasks she hadn’t thought of, even proposed who should own what. A real plan, sitting in a chat window. And then came the part she does every single time: retyping all of it, by hand, into her task manager.
More and more planning starts in a conversation now. You think out loud with an assistant, it helps you structure the work, and you end up with a clean plan in the wrong place. The bridge from that plan to your actual backlog is forty minutes of mindless copying, and it’s exactly the kind of dull, error prone data entry that the assistant could obviously do, if only it could reach your tools.
Skip the retyping
UnaTask speaks MCP, the open standard for connecting AI assistants to real tools. Connect an assistant like Claude, or your code editor, with a personal token, and it can create projects and tasks in your workspace directly. The plan it just helped you write, it can also file.
- Turn a planning chat into a populated backlog in one step.
- Create tasks in bulk, a whole project structure at once instead of one at a time.
- You stay in control: it’s your token, your workspace, your rules.
Because it’s a personal token scoped to your workspace, nothing happens that you didn’t authorize, and you can revoke access whenever you like. The assistant doesn’t get the keys to everything. It gets a specific, revocable door into the one workspace you pointed it at.
The bulk part matters more than it looks. Filing one task by hand is fine. Filing a forty task project breakdown by hand is where good plans go to die, because nobody wants to do it, so it gets done badly or not at all. Letting the assistant create the whole structure at once means ambitious plans actually make it into the system intact, at the exact moment your motivation is highest.
So Cleo’s launch plan never gets retyped. She finishes the conversation, the assistant writes the projects and tasks straight into UnaTask, and she switches tabs to find the whole backlog already there: phases, tasks, owners, ready to work. The forty minute copying chore is just gone, and the plan goes from idea to backlog without her touching a single form.
Think out loud with an assistant, then let it do the data entry. The plan should land in your backlog, not in a transcript you have to retype.