Keep control

Your tasks, your tools

Use the same task behavior through the API, command line, and MCP. Give scripts and agents explicit permissions.

Open Completely

Why it helps

Let your tools work with your task list.

A script can capture follow-up work. A command-line tool can fit tasks into your working routine. An authorized agent can act through MCP without inventing a separate task system.

The API, CLI and MCP use the same task behavior and explicit permissions. Connected tools should preserve the distinctions you rely on in the interface.

What you can count on

  • Public API
  • Command-line workflows
  • Permissioned MCP access

A closer look

Does an integration bypass access rules?

No. Scripts and agents need explicit permissions. Access through another interface doesn’t grant a wider view of private projects or personal planning.

Build on this

Your work stays yours.

Keep control of access, carry your work between tools, and continue across devices.

Keep your work with youKeep tasks and changes safe through interruptions, with a durable offline experience and understandable recovery.Private by defaultUse one account across workspaces. Your Inbox, Today plan, reminders, saved views, and focus history belong to you.Continue across devicesCarry the same work across your devices, preserving task meaning and showing conflicts instead of silently losing changes.

A little less on your mind

One place for it all.
One next step.

From the thought you don’t want to lose to the work you’re ready to finish.

Open Completely