Feature Ideas

Archive lists to keep your space organized but access them at any point in time.

Select multiple tasks to edit or move all at once.

For example: "Repeat after completion" "Repeat X days, weeks, months... after previous item is checked off". For bills to send or training items it makes sense to create a new tasks when previous is completed with a parametre.

Create collapsible task sections in lists for better sorting and organizing.

Allow users to add snippets of code to lists.

I’d love to see a proper backup and restore system. Ideally, I could create local backups of my Superlist data and later restore either an entire account or selected lists. This would provide protection against accidental deletions, unwanted changes, or other mistakes. I don’t necessarily need the backup format to be human-readable; reliability and complete restoration are more important

Been using Superlist as a task manager with a Claude driven interface. Unfortunately there are gaps ranging from missing functionality to bugs. Here's the inventory of items not working per Claude. Superlist MCP Connector — Issue Report From: Sharad Puri (sharadpuri71@gmail.com) Re: Issues encountered using the Superlist MCP connector with an AI assistant App version: [fill in from Superlist menu → About Superlist] Example list URL (if helpful): [paste a list URL] I've been using the Superlist MCP connector heavily with an AI assistant and hit several issues. Grouped below into bugs (things that appear broken) and limitations (capabilities missing from the connector). Happy to provide more detail or screen recordings. Bugs search returns no results for anything Overview: Calls to the MCP search tool return an empty result set ({"results":[]}) for every query — including exact titles of tasks that have existed in my account for days. Reproduce: Have several tasks in an account (e.g., a task titled "Summer Camps").Via the MCP, call search with the query "Summer Camps" (or any exact title).Result is empty, despite the task existing and being readable via get_list. Impact: High. The connector effectively can't find anything. It also breaks the documented guidance to "fall back to search when a list read is truncated (>100 tasks)" — on a list over 100 items, the overflow becomes unreachable. Observed consistently across multiple days, so it does not appear to be indexing lag. Checklist/checkbox completion state is stripped on save Overview: Creating a task whose content includes a checked item (- [x] …) saves it back as unchecked (- [ ]). Reproduce: Via the MCP, add_task with content containing - [x] Already done item.Read the task back with get_task.The item returns as - [ ] (unchecked). Impact: Medium. Combined with there being no tool to complete an individual checklist item, a subtask's "done" state cannot be set through the connector at all. Limitations (missing capabilities) 3. Task body / subtasks cannot be edited after creation update_task accepts only title, due_date, repetition, and priority — there is no field to modify a task's body/notes. So checklist items (subtasks) can only ever be set at creation time. Adding or removing a single subtask later requires deleting and recreating the entire task. A content/notes parameter on update_task would resolve this. 4. Assignee identity (email/ID) is not exposed on read get_task and fetch return a collaborator's display name but not their email or user ID. Since assign_task requires an email/ID, you can't reassign a task programmatically without already knowing the assignee's email out of band. Returning the assignee's email/ID (where permissions allow) would close this gap. 5. No creation timestamp on tasks Task metadata includes priority, status, labels, and due date, but no created/entered date. This makes it impossible to sort or filter tasks by when they were added via the connector. Exposing a created_at field would help. Notes Connector authorized via OAuth; account is on [plan].These are connector/MCP-surface observations; the same data reads correctly via get_list, so the underlying tasks are intact.

When moving a task from one list to another, it currently lands at the bottom of the destination list. It would be useful to have a setting or toggle to choose whether moved tasks should be placed at the top or bottom of the list.

Currently on the master task list you can only choose one filter option. It would be helpful to add a secondary filter option. For example, filter by priority & date as opposed to one or the other.

I find it useful to see my tasks spread in a calendar, especially in weekly view, so I can make sure I have a healthy workload in my hands each day.

The Today view is great, but Week view would be helpful to navigate through the week and not get lost in the detail of one task.

Seamless integration of the calendar to enter tasks directly at a specific time would greatly assist in planning the day. If you want to schedule a task, another window with the calendar could open on the right. In this window, you should also be able to directly schedule the required time by reducing or enlarging the task.

Set optional start and end dates on tasks to make planning easier.

Use tags to organize lists into Kanban boards. This is useful to teams tracking project task status and task priority. Users should be able to click and drag tasks within a Kanban board that is introduced as a new and optional view or as an content type insert.

Enable Windows users to manage lists and tasks with a dedicated desktop app.