Have something to say?

Tell us how we could make the product more useful to you.

MCP: expose a task's source/connector origin link in get_task / list_tasks

Tasks created from a connector (Slack, Gmail, etc.) show an "Open in Slack/Gmail" deeplink in the Akiflow UI, but the MCP tools don't return it - get_task/list_tasks stop at links, which only holds user-attached or text-parsed URLs, never the connector source. Confirmed: get_task returns links: [] for a card with a Slack source link in the UI. This breaks AI triage over MCP - assistants rely on links to recover context, so integration-sourced tasks look "underspecified" when they actually have the richest upstream context. Affects all connectors. Please add a source/origin field (or the connector deeplink in links with a type marker) to the task payload.

אור about 1 hour ago

Feature Request: Group Tasks by Priority with Sub-sorting

The customer has submitted a feature request for Akiflow. They are seeking the ability to visually group tasks by priority into distinct sections, similar to how Trello or other to-do lists display tasks. The customer emphasizes the importance of being able to sort tasks *within* each priority group, which is not possible with the current global 'sort by priority' function as it locks the order and does not provide separate visual sections. While workarounds like using Projects with Sections or grouping the Someday list were suggested, the customer is specifically requesting this functionality for the main daily planning views (Today/Upcoming). The customer has been directed to the Product Feedback Board to upvote this request.

Vlad about 5 hours ago

Change the new home screen feed into a dashboard

As much as I like a lot of the new features, I find that the new feed in the home screen of the mobile app is not very useful. I don't need view new view of the tasks I'm working on in the day since they're already in my today list - this is just duplication. Additionally, a feed of these updates from Aki isn’t something I want to keep checking during the day. Rather, a dashboard displaying how much time I'm spending on various tasks and projects (like the assess your day screen), my accuracy rate in planning task durations, and other useful information such as my percentage of tasks completed for the day, how many productive hours I have left in the day, or my ability to fit more tasks into my day, and maybe even the pomodoro timer - this would be a more useful home screen I'd want to check regularly. You have all the data to make this happen, it's just a matter of turning this app home screen into something that makes us more productive, ie. Showing us our information, rather than less productive, ie. Giving us yet another feed to scroll through.

Kara 2 days ago

Expose Subtasks as first class resources in the MCP API

It would be great if Subtasks were exposed as first class entities for both Aki and MCP compatible assistants, with the same level of support that Tasks currently have. Right now, assistants such as Aki, ChatGPT, Codex, Claude, and other MCP compatible clients can perform the following operations on Tasks: Read Create Update Delete Complete Plan and reschedule Reorganize The current limitation is that Subtasks are not exposed as actionable entities for Aki or other MCP compatible clients. As a consequence, when asking an assistant to create a task with several subtasks, it typically falls back to writing a checklist inside the task description instead of creating actual Subtasks. Ideally, both Aki and the MCP integration should support operations such as: Read subtasks Create subtasks Update subtasks Delete subtasks Complete/uncomplete subtasks Reorder subtasks Move subtasks between parent tasks Convert a task into a subtask, and vice versa if supported This would allow AI assistants to treat Subtasks as first class entities and interact with them in the same way they currently interact with Tasks.

Eduardo 4 days ago