Tasks
What a task holds, how a reference such as TASKAID-45 names it out loud, where it came from, and what finishing one does.
A task is one thing you intend to do. Everything else in Taskaid is a way of looking at your tasks or acting on them, so this is the only object worth learning in detail.
What a task holds
Name is the thing itself. Short is better; a task you cannot read at a glance is a project in disguise.
Note is the room underneath it, written in Markdown and rendered as rich text. Headings, lists, bold and inline code all work, which makes it a reasonable place for an assistant to leave the detail behind a decision.
Date is the day you intend to work on it, and it decides whether the task sits in Inbox, Today or Upcoming. Scheduling covers it properly.
List is where the task belongs, and it is independent of the date. See Lists.
Star marks the ones that matter more than the rest. It changes nothing about where a task appears, which is the point: it survives rescheduling, and assistants weigh it when you ask what to pick up.
Estimate is how long you think the work takes, in minutes. It is a judgement aid rather than a booking, so nothing is placed at an hour, and an assistant asked what fits in a free afternoon has something to reason with.
Every task has a reference
Alongside its name, each task carries a short reference numbered within your account:
TASKAID-45That is how a task gets named out loud. Paste it into a chat, or say "finish TASKAID-45", and an assistant knows exactly which one you mean without anyone handling a database id. #45 and plain 45 work too, so you can say the short form and be understood.
The prefix is deliberately not TASK-: a conversation with Jira or Linear connected is already full of identifiers shaped like that, and TASK-45 would be genuinely ambiguous. The longer prefix arrives saying which tool it belongs to.
A task's page can do the pasting for you. Open starts a new chat with an assistant, already naming the task by its reference. The assistant reads the task itself through Taskaid, so it needs Taskaid connected there first. For an assistant without it, Copy as prompt puts the task's name and note on your clipboard, with its reference, ready to paste anywhere.
Where a task came from
A task records whether Taskaid itself or a connected assistant such as ChatGPT or Claude added it, and shows it on the task's detail.
It is set once, when the task is created, from the name the client registered under, and nothing later can move it. That makes it provenance rather than a status: it answers "where did this come from", not "who is working on it". A task you created in ChatGPT and then rescheduled in the app still says ChatGPT, because that is still where it came from.
Finishing
Completing a task takes it out of Inbox, Today and Upcoming, and records the moment it happened.
Progress counts by when you finished something rather than when it was scheduled, so a task you had scheduled for last week and finish this morning counts towards today. What you got done is a fact about today; what you had planned is not.
From an assistant
Through the MCP server, tasks are search_tasks, view_task and save_task. The Tools reference shows each one as served.
There is no delete tool, by design: an assistant can finish a task or clear its date, but it cannot remove one, even if you ask it to.
Next: Scheduling for how the date behaves, or Lists for how tasks get organised.