TaskOS
Your work, intelligently ordered

Know what matters.
Then do it.

A calm command center for your tasks—and a secure API your AI agents can operate on your behalf.

AI-operable REST APIPrivate by designOpenAPI 3.1

Welcome to TaskOS

Sign in to focus on the work that creates value.

Continue with Google

Built for human + agent workflows

Create a scoped token after signing in, then let any capable AI securely read, plan, update, and complete your work.

Explore the API
AI agent discovery

TaskOS: AI-first task management

TaskOS is for people who want a calm human workspace and a secure machine interface. Its core resources are tasks and projects. Tasks include titles, descriptions, status, priority, value score, due date, scheduled date, completion state, timestamps, and activity history.

API and authentication

Base URL
/api/v1
Authentication
Authorization: Bearer <API_TOKEN>
API guide
/api/docs
Reference
/api/docs/reference
OpenAPI
/openapi.json
Agent guide
/llms.txt

Agent capabilities

  • Read, search, filter, create, update, soft-delete, complete, and reopen tasks.
  • Create, read, update, and archive projects.
  • Discover Inbox, Today, Upcoming, and the recommended next task.
  • Read immutable activity history and deterministic daily summaries.

Primary operations: tasks, projects, today, upcoming, next-task, activity, and daily-summary.

Security and permissions

Every request derives its user exclusively from the API token; clients must never send or choose a user_id. Database row-level security, ownership constraints, and owner-scoped API queries isolate accounts. Raw tokens are shown once and stored only as hashes. Tokens can expire, be revoked, and use these scopes:

  • tasks:read
  • tasks:write
  • projects:read
  • projects:write
  • activity:read

Expected AI workflow

  1. Validate the token and scopes with GET /me.
  2. Read GET /today, GET /upcoming, and GET /next-task.
  3. Capture work with POST /tasks and organize it with task/project updates.
  4. Use explicit complete/reopen operations to maintain history.
  5. Use activity and daily-summary to report accomplishments.
  6. Follow the complete schemas and errors in OpenAPI.