メニュー
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the `td` CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Executes an implementation plan (from /spec) end to end: turns its Steps into a tracked checklist, works through them one at a time — implement, run the Step's Verify, check it off, commit — then runs the plan's overall Verification and delivers a PR. When the plan is one phase of a /phasing roadmap, delivery also writes the phase's carry-over fragment and flips its status in the roadmap. Invoking /implement is itself the go-ahead to execute; there's no separate approval gate. Use when the user wants to execute, build, or ship a plan that already exists, or invokes /implement.
Turns settled PRD/TDD/ADR scope into an ordered set of phases, each sized to be exactly one /spec (one Approach, one Verify surface, one PR), organized as a dependency graph so parallel streams fall out of real technical dependency instead of being guessed upfront. Writes the roadmap to docs/roadmaps/<slug>/roadmap.md; each phase becomes its own /spec afterward. Use when the user wants to break a feature or system into phases, plan a rollout across multiple PRs, or invokes /phasing.
Writes or updates a Product Requirements Document (PRD) — a concise, best-practice description of what a system, feature, or subsystem does for its users, never how it's built. Takes its input from a /brainstorm convergence artifact, a /tdd document, or the user's own description of a feature. Use when the user wants a PRD, product requirements doc, or asks to turn a brainstorm or design into product requirements, or invokes /prd.
Reviews a delivered change against its contracts — the /spec plan, the roadmap phase's boundary, binding ADRs, and test authenticity — and returns a verdict with blocking and advisory findings.
Writes or updates an implementation plan — a concise, actionable breakdown of how one change will be made: what recon (and any binding ADRs) found, the chosen approach, an ordered list of steps, and how each step (and the change as a whole) is verified done. Scoped to a single change, not a system (that's a TDD) and not user-facing behavior (that's a PRD) — the plan is the handoff artifact between deciding what to build and building it. Use when the user wants an implementation plan, asks to plan a feature, bugfix, or refactor before coding it, or invokes /spec.
Writes or updates a Technical Design Document (TDD) — a description of how a system, subsystem, or component is put together. Not a proposal: states the design rather than building a case for it, and references the ADRs, PRDs, or brainstorm docs that justify it instead of restating them. Grounds every part in the most reliable source available — code where it's built, anchor docs where it isn't yet — and flags unbuilt pieces inline instead of labeling the whole document. Use when the user asks for a technical design document, architecture document, or system design doc, or wants a system's (or part of a system's) architecture written down with diagrams.
SOC 職業分類に基づく
| name | todoist-cli |
| description | Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the `td` CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters. |
| compatibility | Requires the td CLI (@doist/todoist-cli) to be installed and authenticated via 'td auth login'. |
| license | MIT |
| metadata | {"author":"Doist","version":"1.69.2"} |
td <command> --help for available subcommands, flags, and usage examples where provided.td <command> --help for exact flags when you already know the command family.id:..., or a Todoist web URL as a reference.td task <ref>, td project <ref>, td workspace <ref>, td comment <ref>, and td notification <ref> default to view.--project, --task, and --workspace.p1 highest (API 4) through p4 lowest (API 1).curl the fileUrl and then Read the downloaded file — the vision pipeline can reject an image and leave it pinned in context, which breaks the rest of the session. Fetch with td attachment view <file-url> (or --json) when you actually need the content; the base64 output is plain text and safe to keep in context. Skip the fetch entirely unless the user asked for visual analysis — the Name, Size, and Type fields are usually enough.--json, but other output and pagination flags vary by family. Many list commands support subsets of --ndjson, --full, --raw, --limit <n>, --all, --cursor <cursor>, or --show-urls; check td <command> --help for the exact surface.--json to return the created or updated entity.--dry-run to preview actions without executing them.--yes.--quiet / -q suppresses success messages. Create commands still print the bare ID for scripting (e.g. id=$(td task add "Buy milk" --quiet)).--no-spinner, --progress-jsonl, -v/--verbose, --accessible, --quiet, --user <id|email>.td auth login
td auth login --read-only
td auth login --additional-scopes=app-management
td auth login --read-only --additional-scopes=app-management
td auth login --additional-scopes=backups
td auth login --read-only --additional-scopes=backups
td auth login --additional-scopes=billing
td auth login --additional-scopes=app-management,backups
td auth login --callback-port 9000 # override the OAuth callback port
td auth login --json # emit the new account record as JSON
td auth login --ndjson # one-line newline-delimited JSON
td auth token
td auth status
td auth status --json # full status payload as JSON (--ndjson also supported)
TOKEN=$(td auth token view)
TOKEN=$(td auth token view --user you@example.com)
td auth logout
td auth logout --json # emits `{"ok": true}` (--ndjson is silent)
td auth login, td auth status, and td auth logout all accept the standard --json / --ndjson machine-output flags. For login and status the body carries the account record (id, email, auth metadata, plus storedUsers and source from status); logout emits a {"ok": true} envelope under --json and stays silent under --ndjson. Across all three, keyring-fallback warnings are written to stderr so stdout stays parseable. td auth login additionally accepts --callback-port <n> (default 8765, with a small fallback range when the port is busy).
Opt-in OAuth scopes are requested via --additional-scopes=<list> (comma-separated). Run td auth login --help for the full list. Currently supported:
app-management — adds the dev:app_console scope (manage your registered Todoist apps — rotate secrets, edit webhooks, etc.). Required by td apps list and td apps view.backups — adds the backups:read scope (list and download Todoist backups). Required by td backup list and td backup download.billing — adds the billing:read_write scope, or billing:read when combined with --read-only (view subscription, plan, and pricing). Required by td billing subcommands.Combine freely with --read-only to keep data access read-only while still granting an opt-in scope (e.g. td auth login --read-only --additional-scopes=backups). When a command fails for lack of a scope, the error suggests a re-login command that preserves whichever flags were originally used.
Tokens are stored in the OS credential manager when available, with fallback to ~/.config/todoist-cli/config.json. TODOIST_API_TOKEN takes precedence over stored credentials.
td auth token view writes the stored token to stdout for use in scripts. Always capture it into a shell variable (e.g. TOKEN=$(td auth token view)) — never invoke it bare in an agent transcript or piped to a shell that echoes its output, since that would leak the secret. Honors --user <id|email> for multi-account installs and refuses when TODOIST_API_TOKEN is set in the environment (the token is already available there).
The CLI can hold credentials for multiple Todoist accounts at once.
td auth login # adds the account; first one becomes default
td accounts list # all stored accounts (with default marker)
td accounts list --json # { accounts: [...], default } envelope; --ndjson streams one account per line
td accounts use <id|email> # set the default account (alias: td accounts default; --json/--ndjson supported)
td accounts current # show the active account (--json/--ndjson supported)
td accounts remove <id|email> # delete an account and its token (--json/--ndjson supported)
td --user <id|email> task list # one-off override for any command
td auth logout --user <id|email> # log out a specific account
td accounts is also available as td user / td users (back-compat aliases).
Resolution order: --user <ref> > user.defaultUser from config > the only stored account. With multiple accounts and no default, commands error and ask for --user (or td accounts use). <ref> matches an exact id or email (case-insensitive on email). TODOIST_API_TOKEN still bypasses the resolver entirely.
td today, td inbox, td upcoming, td completed, td activitytd task list/view/add/quickadd/update/reschedule/move/complete/uncomplete/delete/browse (alias: td task qa for quickadd)td project list/view/create/update/archive/unarchive/archived/delete/move/reorder/join/browse/collaborators/permissionstd project progress/health/health-context/activity-stats/analyze-healthtd goal list/view/create/update/delete/complete/uncomplete/link/unlinktd label ..., td filter ..., td section ..., td folder ..., td workspace ...td comment ..., td notification ..., td reminder ...td template ..., td attachment view <file-url>, td backup ...td hc locales/search/viewtd stats, td settings ..., td config view, td accounts ..., td completion ..., td view <todoist-url>, td doctor, td update, td changelogtd apps list/view (requires td auth login --additional-scopes=app-management)td backup list/download (requires td auth login --additional-scopes=backups)td billing subscription/plan/prices/pricing (requires td auth login --additional-scopes=billing)Tasks, projects, labels, and filters can be referenced by:
id:xxx - Explicit IDhttps://app.todoist.com/app/task/buy-milk-8Jx4mVr72kPn3QwB or https://app.todoist.com/app/project/work-2pN7vKx49mRq6YhT)Some commands require id: or URL refs (name lookup unavailable): task uncomplete, section archive/unarchive/update/delete/browse, comment update/delete/browse, notification view/accept/reject.
Reminder commands that take an ID (reminder get/update/delete, reminder location get/update/delete) only accept id:xxx or raw IDs — URLs are not supported for reminders.
td today
td inbox --priority p1
td upcoming 14 --workspace "Work"
td completed list --since 2024-01-01 --until 2024-01-31
td completed list --search "meeting notes"
td activity --type task --event completed
td task add "Buy milk" --due tomorrow
td task quickadd "Buy milk tomorrow p1 #Shopping"
td task qa "Review PR @urgent +Alice"
td task list --project "Work" --label "urgent" --priority p1
td task view "Buy milk"
td task add "Plan sprint" --project "Work" --section "Planning" --labels "urgent,review"
td task update "Plan sprint" --deadline "2026-06-01" --assignee me
td task reschedule "Plan sprint" 2026-03-20T14:00:00
td task move "Plan sprint" --project "Personal" --no-section
td task complete "Plan sprint"
td task uncomplete id:123456
td task delete "Plan sprint" --yes
td task browse "Plan sprint"
Choosing between task add and task quickadd:
td task quickadd (alias td task qa) uses Todoist's natural-language parser. Inline syntax covers dates ("tomorrow at 2pm"), priority (p1–p4), project (#Project), labels (@label), sections (/Section), and assignee (+Person on shared projects). Prefer quickadd when all task attributes can be expressed inline and you do not need to set additional structured fields — it's one call and no name-resolution lookups are required.td task add when you need flags that Quick Add syntax can't express (--deadline, --description, --parent, --duration, --uncompletable, --order), when the text is being composed programmatically, or when you need explicit id: / URL references for project/section/parent.td task quickadd supports --stdin, --json, and --dry-run only; everything else is embedded in the text.td add <text> is a human shorthand for td task quickadd — same parser, same flag surface (--stdin, --json, --dry-run). Agents should prefer td task quickadd / qa for discoverability alongside the other task subcommands.--due on task add / task update is sent verbatim to the API as due_string — the CLI does not parse or rewrite it. The server's due_string parser handles simple inputs ("2026-06-01", "tomorrow", "every Monday") but does not unpack some more complex clauses (i.e. starting <date>).Useful task flags:
--stdin on task add reads the task description from stdin; on task quickadd (and the top-level td add) it reads the full natural-language text from stdin.--parent, --section, --project, --workspace, --assignee, --labels, --due, --deadline, --duration, and --priority cover most task workflows.td task complete --forever stops recurrence; td task update --no-due clears the due date, --no-deadline clears deadlines, and --no-labels removes all labels; td task move --no-parent and --no-section detach from hierarchy.td project list --personal
td project list --search "Road"
td project archived
td project view "Roadmap" --detailed
td project collaborators "Roadmap"
td project create --name "New Project" --color blue
td project update "Roadmap" --favorite
td project update "Roadmap" --folder "Engineering"
td project update "Roadmap" --no-folder
td project update "Roadmap" --parent "Engineering"
td project update "Roadmap" --no-parent
td project update "Roadmap" --parent "Engineering" --json
td project update "Roadmap" --parent "Engineering" --dry-run
td project reorder "Roadmap" --before "Marketing"
td project reorder "Roadmap" --after "Marketing"
td project reorder "Roadmap" --position 0
td project reorder "Roadmap" --position 2 --json
td project reorder "Roadmap" --before "Marketing" --dry-run
td project archive "Roadmap"
td project unarchive "Roadmap"
td project move "Roadmap" --to-workspace "Acme" --folder "Engineering" --visibility team --yes
td project join id:abc123
td project delete "Roadmap" --yes
td project progress "Roadmap"
td project health "Roadmap"
td project health-context "Roadmap"
td project activity-stats "Roadmap" --weeks 4 --include-weekly
td project analyze-health "Roadmap"
td project archived-count --workspace "Acme"
td project permissions
td workspace list
td workspace view "Acme"
td workspace projects "Acme"
td workspace users "Acme" --role ADMIN,MEMBER
td workspace insights "Acme" --project-ids "id1,id2"
td workspace create --name "Acme"
td workspace update "Acme" --description "Acme Inc." --dry-run # admin-only
td workspace delete "Old WS" --yes # admin-only
td workspace user-tasks "Acme" --user alice@example.com
td workspace activity "Acme" --json
td workspace use "Acme" # persist a default; omitted refs on other workspace commands fall back to it
td workspace use --clear # forget the stored default
td folder list "Acme"
td folder view "Engineering"
td folder create "Acme" --name "Engineering"
td folder update "Engineering" --name "Platform" --workspace "Acme"
td folder delete "Engineering" --workspace "Acme" --yes
td label list
td label list --search "bug"
td label view "urgent"
td label create --name "urgent" --color red
td label update "urgent" --color orange
td label delete "urgent" --yes
td label browse "urgent"
td label rename-shared "oldname" --name "newname"
td label remove-shared "oldname" --yes
td filter list
td filter view "Urgent work"
td filter create --name "Urgent work" --query "p1 & #Work"
td filter update "Urgent work" --query "p1 & #Work & today"
td filter delete "Urgent work" --yes
td filter browse "Urgent work"
td section list "Roadmap"
td section list --search "Planning"
td section list --search "Planning" --project "Roadmap"
td section create --project "Roadmap" --name "In Progress"
td section update id:123 --name "Done"
td section reorder "Review" --project "Roadmap" --before "Done"
td section reorder "Review" --project "Roadmap" --after "In Progress"
td section reorder --section "Review" --project "Roadmap" --position 0 --dry-run
td section reorder "Review" --project "Roadmap" --position 2 --json
td section archive id:123
td section unarchive id:123
td section delete id:123 --yes
td section browse id:123
Shared labels can appear in td label list and td label view, but standard update and delete actions only work for labels with IDs. Use td label rename-shared and td label remove-shared for shared labels.
td goal list # List all accessible goals
td goal list --workspace "Work" # Filter to workspace goals
td goal view "Ship v2" # View goal details and linked tasks
td goal create --name "Ship v2" # Create personal goal
td goal create --name "Ship v2" --workspace "Work" # Create workspace goal
td goal create --name "Ship v2" --deadline "2026-04-03"
td goal create --name "Ship v2" --json # Return created goal as JSON
td goal create --name "Ship v2" --dry-run # Preview creation
td goal update "Ship v2" --name "Ship v3"
td goal update "Ship v2" --description "New desc" --json
td goal delete "Ship v2" --yes
td goal complete "Ship v2" # Mark goal as completed
td goal uncomplete "Ship v2" # Reopen a completed goal
td goal link "Ship v2" --task "Buy milk" # Link a task to a goal
td goal unlink "Ship v2" --task "Buy milk" # Unlink a task from a goal
td comment list "Plan sprint"
td comment list "Roadmap" --project
td comment add "Plan sprint" --content "See attached" --file ./report.pdf
td comment add "Plan sprint" --content "See attached" --file ./report.pdf --file-name "Quarterly report.pdf"
td comment update id:123 --content "Updated text"
td comment delete id:123 --yes
td comment browse id:123
td attachment view "https://files.todoist.com/..."
td notification list --unread
td notification view id:123
td notification accept id:123
td notification reject id:123
td notification read --all --yes
td reminder list "Plan sprint"
td reminder list --type time
td reminder add "Plan sprint" --before 30m
td reminder add "Plan sprint" --at "2026-06-01 09:00" --urgent # iOS full-screen alarm
td reminder update id:123 --before 1h
td reminder update id:123 --no-urgent # toggle urgency without changing time
td reminder delete id:123 --yes
td reminder get id:123
td reminder location add "Plan sprint" --name "Office" --lat 40.7128 --long -74.0060 --trigger on_enter --radius 100 # radius in meters
td reminder location update id:456 --radius 200 # radius in meters
td reminder location delete id:456 --yes
td reminder location get id:456
td attachment view prints text attachments directly and encodes binary content as base64. Use --json for metadata plus content. Prefer this over curl + Read on Todoist file URLs — for images in particular, Read will try to decode the file through the vision pipeline, and if that fails the image stays pinned in conversation context and every retry hits the same error.
td comment view flags image attachments with a Hint line pointing at td attachment view. In --json mode the hint is written to stderr so stdout stays parseable — watch the tool output, not just the JSON body.
td hc
td hc --help
td hc locale --set-default pt-br
td hc search "filters" --ndjson # one article per line for scripts (--json also supported)
td hc view https://www.todoist.com/help/articles/introduction-to-filters-V98wIH
td hc queries the Todoist online Help Center. Run td hc --help for locale discovery, article search, and article viewing details. td hc locale --set-default <locale> persists a preferred locale in ~/.config/todoist-cli/config.json under hc.defaultLocale; the --locale flag on individual subcommands still overrides it. td hc view accepts id:N, raw numeric article IDs, get.todoist.help URLs, and public www.todoist.com/help/articles/... marketing URLs (resolved to the underlying Zendesk article via slug search).
td template export-file "Roadmap" --output template.csv
td template export-url "Roadmap"
td template create --name "New Project" --file template.csv --workspace "Acme"
td template create --name "New Project" --file template.csv --file-name "Q2 plan.csv"
td template import-file "Roadmap" --file template.csv
td template import-file "Roadmap" --file template.csv --file-name "Q2 plan.csv"
td template import-id "Roadmap" --template-id product-launch --locale fr
td backup list
td backup download "2024-01-15_12:00" --output-file backup.zip
The backup command surface requires the backups:read OAuth scope — re-run td auth login --additional-scopes=backups to grant it. Without the scope, calls fail with an AUTH_ERROR whose hint preserves any previously used flags (e.g. a read-only user sees td auth login --read-only --additional-scopes=backups).
td apps list
td apps list --json
td apps view "Todoist for VS Code"
td apps view id:9909
td apps view 9909
td apps view id:9909 --json
td apps view id:9909 --include-secrets
td apps view id:9909 --json --include-secrets
td apps update id:9909 --add-oauth-redirect https://example.com/callback
td apps update id:9909 --remove-oauth-redirect https://example.com/callback --yes
The apps command surface manages the user's registered Todoist developer apps (integrations). All apps subcommands require the dev:app_console OAuth scope — re-run td auth login --additional-scopes=app-management to grant it. Without the scope, calls fail with a MISSING_SCOPE error pointing at the same hint.
td apps list plain output leads with the display name and follows it with (id:N) (self-describing in --accessible mode), then an indented Client ID: <client_id> line, then the description. --json / --ndjson dump the full app payload (id, clientId, displayName, status, userId, createdAt, serviceUrl, oauthRedirectUri, description, icons, appTokenScopes).
td apps view <ref> accepts a name (fuzzy/case-insensitive), id:N, or a raw numeric id. Plain output shows display name as a header, then a labelled key/value block (id, status, users, created date, service URL, OAuth redirect, token scopes, icon URL, client id) followed by the description. Webhook configuration is always fetched (getAppWebhook — callback URL is user-supplied, not a secret). When --include-secrets is set, the command additionally fetches the app's secrets (client_secret), verification token, test token, and distribution token.
td apps update <ref> --add-oauth-redirect <url> appends an OAuth redirect URI to the app, and --remove-oauth-redirect <url> takes one off (requires --yes to actually mutate, like td task delete). The two flags are mutually exclusive — pass one at a time. The URI is validated before any API call: https://<host>, http(s)://localhost[:port][/path], http(s)://127.0.0.1[:port][/path], or a custom-scheme URI (e.g. myapp://callback) are accepted; javascript, data, file, vbscript, and ftp custom schemes are rejected. Removals skip validation so users can clean up legacy malformed URIs. Adding a URI already set on the app fails with ALREADY_EXISTS; removing a URI that isn't on the app exits 0 with a message and makes no API call. Supports --dry-run and --json.
The OAuth client_id is public and always shown. The four sensitive credentials — client secret, verification token, test access token, distribution token — are hidden by default. In plain mode each of those lines renders a (hidden — pass --include-secrets to reveal) hint; in --json / --ndjson the clientSecret, verificationToken, distributionToken, and testToken keys are omitted from the payload entirely. With --include-secrets, the values are rendered / emitted normally — in that mode a non-existent test token reads as (not created). Webhook configuration is always included when configured (callback URL, event list, version); a missing webhook renders as (not configured) in plain output and null in JSON.
td billing # subscription (default subcommand)
td billing subscription --json
td billing plan
td billing prices
td billing pricing --formatted
The billing command surface is read-only and requires the billing OAuth scope — re-run td auth login --additional-scopes=billing to grant it. A normal login grants billing:read_write; adding --read-only narrows it to billing:read. Either satisfies these read commands. Without the scope, calls fail with a MISSING_SCOPE error whose hint preserves any previously used flags. All subcommands accept --json / --ndjson, which dump the raw SDK payload verbatim.
td billing subscription (the default subcommand) shows the current plan, status, activation method, expiration date, plan price, invoice credit balance, and billing-portal URLs when present. td billing plan shows Pro plan status, downgrade date, and the per-cycle price list. td billing prices lists available Pro and Teams prices by billing cycle. td billing pricing shows current and legacy pricing keyed by version; --formatted returns localized price strings instead of minor-unit numbers.
td stats
td stats goals --daily 10 --weekly 50
td stats vacation --on
td settings view
td settings update --timezone "America/New_York" --time-format 24 --date-format intl
td settings themes
td config view
td config view --json
td config view --show-token
td completion install zsh
td completion uninstall
td view https://app.todoist.com/app/task/buy-milk-abc123
td view https://app.todoist.com/app/today
td doctor
td doctor --offline
td doctor --json
td update --check
td update --check --json
td update --channel
td update switch --stable
td update switch --pre-release --json
td changelog --count 10