Tasks

A task is what you mean to do next, written down where you or your agents will find it. Tasks › Add Task… (⌃⌘T) turns a prompt into one Markdown file in the project’s todo/ folder, with - [ ] boxes and where you were, so tomorrow’s agent session in that project reads it with its own file tools. There is no account and no service: the files are yours, in a format any program, agent or person can read.

Each project can send its tasks somewhere else instead: an app on this Mac (Reminders, Things, a Shortcut, Todoist or OmniFocus), a tracker’s new-issue page in your browser (GitHub, GitLab, Linear, Trello or Azure Boards), or your own agent, which posts it with its own tracker tools. Next Term makes no network request for any of it, and you read the exact text before it leaves.

At the end of a day, Wrap Up asks your agent tabs for a handoff and turns their next steps into tomorrow’s tasks once you have read them, and Post Update drafts what you did, what is next and what is blocked, for you to copy, save or hand to an agent.

Add a task

Press ⌃⌘T in a project’s window. A sheet opens over it:

• The prompt starts as what you selected: text in the terminal, else in the editor, else the question an agent in the window is waiting on. Write what to do; the rules below make it a task.
• When: Tomorrow unless you pick Today, Next Week (the coming first day of the week), No Date or Choose Date…. It is the day the task is planned for, never a deadline.
• Include where you are (project, branch, tab, agent) starts as Settings › Tasks has it. On, the file names the branch, the tab, the agent in it and the command that resumes that agent’s session.
• Destination: where this task goes, starting as the project’s choice. Changing it here changes this task only; the project keeps its own. Under it, one line says exactly where the task goes and what happens there, such as “Opens a new issue in acme/shop on github.com, filled in: nothing is created until you press Create”.
• What’s sent shows the exact text or link that leaves Next Term, as the destination gets it. It opens by itself when the text had to be cut to fit.
• Before anything is written, two lines say what the task will be and where it goes: “Finish the login fix · 2 steps · notes · Tomorrow, Fri 16 Oct”, then, for the todo folder, “Saves to todo/2026-10-15-finish-the-login-fix.md in shop”, with “and makes the todo folder” for the first one.
• The button says what it does: Add Task for the todo folder, Reminders, Things and a Shortcut, Open Page for a tracker’s page, Open Quick Add for Todoist and OmniFocus, and Type into Tab for Through Your Agent. ⌘↩︎ presses it, and ⎋ cancels. A notice at the bottom of the window says what happened, such as “Added to todo/” or “Added to Reminders”, with Undo for both.
• When the destination can’t be used now (an app that isn’t installed, Reminders not allowed, a shortcut that is gone, details missing), the line says why and Use Todo Folder adds this one task to the todo folder instead.
• A page or Quick Add opens once per task, so a prompt that is a list of more than 5 tasks is refused there; split it, or add it to the todo folder.
• The same title twice in a minute asks Added a minute ago. Add again?, so a double press never adds a task twice, wherever it goes.

While no default is set and the project has no destination of its own, a line in the sheet asks “Tasks go to the todo folder. Send them to Reminders or Things instead?”. Choose… asks Where should tasks go? and makes your choice the default for every project; the × keeps the todo folder. Once you choose, or press ×, it never asks again; Cancel in Where should tasks go? leaves the line for next time.

The Tasks menu also has Wrap Up… (⌃⌘W, Wrap Up) and Post Update… (Post Update), Show Todo Folder, which selects the folder in the project sidebar, or shows it in the Finder when the sidebar doesn’t hold it (a worktree’s main checkout, or one folder for every project), Send Tasks To ▸ (where tasks go), Connect a Tracker to Your Agents… (connect a tracker) and Task Settings…, which opens Settings › Tasks.

How a prompt becomes a task

Fixed rules read the prompt; no model does.

• The title is the first plain line, without a trailing :. A prompt that starts with a list takes its first item instead.
• Steps are the lines that start with -, *, +, 1., 1) or a box ([ ], [x]), a [x] one done. An indented one is nested under the step above it.
• Notes are every other line, and code blocks whole, word for word.
• A prompt that is only a list adds one task per item, with what is nested under each item as its steps.
• Stored keys are masked. A key you keep in Secrets shows as ••• in the file, and the sheet says so. Masking is best effort: a key under 12 characters is missed (what masking misses).

So this prompt:

Finish the login fix:
- Write the test for expired tokens
- Ask Sam about the refresh endpoint

Branch is fix/login, see PR 512.

is one task with two steps and a line of notes.

The todo folder

• In the project: todo/ at the top of the project, made with the first task. Every .md file in it is a task file, one you wrote by hand included.
• In a worktree: the main checkout’s todo/, so tasks outlive the worktree and every worktree of the repository shares one list. In a worktree of a bare repository, which has no main checkout, it is the worktree’s own.
• Another folder: Settings › Tasks › Todo folder takes a path inside each project, such as docs/todo, or one absolute folder for every project. A path in the project must stay inside it, and never in .git. An absolute folder must be there already, since Next Term never makes it, and each file in it names its project (project and path).
• A window with no project: a task there needs Settings › Tasks › Outside a project to name a folder. With None, the sheet says so and adds nothing.
• Nothing is written over. Each file is new; a name taken meanwhile gets the next number, -2, -3 and so on.
• Git: Next Term never edits .gitignore, and the todo folder shows in git status like any new folder. To keep your tasks to yourself, add todo/ to the project’s .gitignore, or to .git/info/exclude, which only your checkout reads. To share them with your team, commit the folder: each task is its own file, so adding one never changes another.

The file

One task is one Markdown file named <the day it was added>-<the title>.md, such as 2026-10-15-finish-the-login-fix.md: the title in lower case, letters of any script kept, and spaces as -, cut at a word to 50 characters. The name never changes after it is made. The text is UTF-8 with LF line endings: flat front matter, then the task’s - [ ] line, its steps nested under it, and the notes after a blank line.

---
created: 2026-10-15T18:42:07+06:00
scheduled: 2026-10-16
branch: "fix/login"
tab: "api"
agent: claude
resume: "claude --resume 7f3c2a"
added_by: you
---
- [ ] Finish the login fix
  - [ ] Write the test for expired tokens
  - [ ] Ask Sam about the refresh endpoint

Branch is fix/login, see PR 512.

Key	Meaning
created	When the task was added
scheduled	The day it is planned for; never a deadline
project, path	Only in a folder outside the project
branch	The branch at the time
tab	The tab’s title
agent	The agent’s kind, such as claude or codex
resume	The command that resumes that agent’s session
added_by	you, or who asked: an agent in a tab, or a connection

Empty keys are left out. Tomorrow, an agent lists todo/*.md, reads the open boxes and uses scheduled: for the day; ticking a task changes the one character between its brackets, which is what a click on its box does in Next Term’s Live Preview. The format is open, with its full rules in docs/todo-files.md.

Undo

Undo, in the notice after a task is added, moves its file to the Trash, and removes the folder made for it while that folder is empty. A task you edited since stays, and the notice says so.

For a task sent to Reminders, Undo removes the reminder while it is as it was saved. A task handed to another app, a page, a shortcut or an agent is that place’s from then on: undo it there.

Where tasks go

By default a task is a file in the project’s todo folder. Each project can send its tasks to one other place instead, and you choose it in three places:

• Tasks › Send Tasks To ▸ shows where the front project’s tasks go, ticked, and changes it in one click. Its first line says whose choice it is, such as “For “shop””, with “and its worktrees” added in a worktree’s window; in a window with no project it shows and changes the default. Every destination is listed in a fixed order. One that needs details opens Settings at them (Run a Shortcut…, GitHub Issues…, GitLab Issues…, Azure Boards…, Through Your Agent…), and one that can’t be chosen now stays in the list, greyed, with why: “not installed”, or “not allowed in Privacy & Security”. Use the Default (…) clears the project’s own choice, and Set Up Destinations… opens Settings › Tasks.
• Settings › Tasks, under Destinations: Default: for every project with no choice of its own and for windows with no project, This project: for the project in front, and below them the details of the destination you picked (a Reminders list, a shortcut, a repository, a Linear team key…). A destination with nothing to fill (the todo folder, Todoist, OmniFocus, Trello, and Linear with no team) is saved as soon as you choose it; details you type are saved with Save, and Revert puts back what is saved.
• The Add Task sheet’s Destination, for one task only.

A project’s choice is kept in Next Term’s own settings, keyed by the project’s main checkout, so every worktree of the project shares it. It is never written into the repository, so nothing in a project you clone can send your tasks elsewhere. A project with no choice of its own uses the default, and the default is the todo folder until you change it.

What each destination gets

Destination	What is sent	The day	Limit
Todo Folder	A Markdown file in the project’s todo folder (the file)	scheduled in the file	None
Reminders	The title; the notes hold the steps as - [ ] lines, then the notes, then where it was added	An all-day due date	None
Things	The title, the notes, the steps as checklist items, the day, and the list when you set one	Today, tomorrow or the date	Notes 10,000 characters, 100 checklist items
Run a Shortcut	The shortcut’s input: the title, then the steps, the notes and where it was added	A line Planned: <date>	None
Todoist	Quick Add with the title and a description	Set it there	Link 6,000 bytes
OmniFocus	Quick Add with the name and a note	Set it there	Link 6,000 bytes
GitHub	The repository’s new-issue page with its title and body, the steps as task-list lines	None	Link 6,000 bytes
GitLab	The project’s new-issue page on gitlab.com with its title and description	None	Link 6,000 bytes
Linear	The team’s new-issue page (or linear.new, with no team) with its title and description	None	Link 6,000 bytes
Trello	The Add Card page with the name only; you choose the board there	None	Name 300 characters
Azure Boards	The new work item page of the type you chose, with its title and description	None	Description 2,000 characters, link 6,000 bytes
Through Your Agent	One request typed into an agent tab you pick, with no Return	In the request’s text	None

• Cut to fit. A text longer than its destination takes is cut at a line end and ends with a line saying so, such as “(Cut by Next Term: Things takes 10,000 characters.)”. The sheet’s line says “cut to fit”, and What’s sent shows the cut text before you press anything.
• Where it was added. With Include where you are on, Reminders, Things, Todoist, OmniFocus and the shortcut get the project, the branch, the tab, its agent and the agent’s resume command. A tracker’s page and the agent request get the branch only: a tab’s title or a resume command means nothing to a teammate.

Send tasks to Reminders

Tasks go to a list named “Next Term”, made on the first task if it isn’t there, unless you pick another list in Reminders’ details. Reminders has no field for the day you plan to do something, and its Today and Scheduled lists go by the due date, so the planned day becomes an all-day due date and the sheet’s line says “due”, as in “Adds to Reminders, list “Next Term”, due tomorrow, Sat 19 Oct”. No alert is set unless you tick Alert at 9:00 on the day.

Next Term asks macOS for Reminders only when you first choose it, after a sheet, “Add tasks to Reminders?”, that says why (Continue, then macOS asks). In Settings › Tasks the same starts from Allow Reminders…. It reads only the names of your lists, for the picker, and the reminders it added, for Undo, and adds only what you add, but macOS has no add-only access: what you allow is access to your reminders. macOS gives this permission to Next Term, and commands running in its tabs share it. If you said no, Open Privacy & Security takes you to where it is turned on. The notice after a reminder is added has Undo, which removes the reminder while it is as it was saved.

Things, Todoist and OmniFocus

Each gets a link opened only in the vendor’s own app, never in another app that claims the same kind of link. Things adds the task, with its day and list, to its Inbox or the list you set; the first link makes Things ask once whether to enable Things URLs. Todoist and OmniFocus open their Quick Add, filled in, and nothing is added until you press Add there; set the day there too.

Run a Shortcut

Pick one of your shortcuts in its details (Reload reads them again). Each task runs it as shortcuts run with the task’s text as its input, with no shell, and stops it after 60 seconds. The shortcut decides where the text goes, with its own permissions, so it can reach any app or service a shortcut can.

Linear and GitHub issues, and other tracker pages

GitHub, GitLab, Linear, Trello and Azure Boards open their new-issue page in your browser, filled in. Nothing is created until you press the page’s own Create or Save, signed in as you are in that browser. GitHub takes an owner and repository (Use This Project’s Remote fills them from the project’s origin), GitLab a project path on gitlab.com, Linear an optional team key such as ENG, and Azure Boards an organization, a project and a work item type.

Through Your Agent

For a tracker with no page Next Term can fill, or one you would rather post to with your agent’s own tools (Jira, Notion, Asana…), choose Through Your Agent… and name the tracker. The sheet then has an Agent tab: row, and Type into Tab types one request into the agent tab you picked, in this window:

Add this task to Jira with your Jira tools, exactly as written, then tell me its link.

followed by the task. Only agent tabs that are ready are offered: one that is working, or has your own text at its prompt, is greyed with why. Next Term never presses Return. You read the request in the tab and send it, and your agent posts it with its own sign-in; its answer, with the link, is in that tab. An agent with no bracketed paste gets the task on one line, joined with “ / ”, and one task at a time.

What leaves the Mac

Next Term makes no network request for any of this, and holds no account, token or API key for any destination.

• An app (Reminders, Things, Todoist, OmniFocus) gets the task on this Mac; what that app does with it, such as its own sync, is the app’s.
• A page opens in your default browser with the task in its link. The browser loads it; nothing is saved until you submit it there.
• A shortcut gets the text as its input, and does what you built it to do.
• An agent’s request is typed into its tab for you to send.
• Stored keys are masked first. A value kept in Secrets reads ••• in the sheet, in What’s sent, in the approval window and in what the app, page, shortcut or agent gets: a task that held token=••• arrives as token=•••. Masking is best effort, as above.
• This Mac’s details stay off team pages. GitHub, GitLab, Linear, Trello, Azure Boards and the agent request never get the tab’s title, the agent or its resume command.
• No logs. The task’s text, its link and where it went are never written to a log or a crash report.
• Wrap Up and Post Update make no request either. Wrap Up types its one fixed request into the tabs you ticked, and the handoffs are files your agents write in your project. Nothing from a handoff leaves until you press Add in the review. Post Update reads today’s handoffs, today’s posted record and your own commits on this Mac, and its draft goes nowhere until you press Copy, Save to Project or Send Through an Agent Tab…, which types it with no Return. Stored keys show as ••• in the handoff, the review, every task and the draft, and in what Copy, Save and Send give out. Handoff text and the draft are never logged.

Next Term hands each task over once. It doesn’t read your tracker or app, and doesn’t keep tasks in step with them afterwards.

The posted record

Each task sent anywhere, the todo folder included, adds one line to Tasks.noindex/posted.jsonl in Next Term’s folder in Application Support, readable only by you: when, the destination’s kind and its key (the list or the repository), the masked title and the project. Lines older than 30 days are dropped. It is used for three things only: the warning when the same task goes to the same place again within a minute, Reminders’ Undo, and what was posted today, which Post Update lists under Next. Next Term never sends the record anywhere; today’s lines leave only inside a Post Update draft you copy, save or send yourself.

Connect a tracker

Tasks › Connect a Tracker to Your Agents…, also Connect a Tracker… in Settings › Tasks and beside Through Your Agent’s details, sets your agents up to post to a tracker themselves. Pick the tracker, and the sheet shows, for Claude Code, Codex, Gemini CLI and OpenCode, the line that agent’s own docs or the tracker’s own page give to add the tracker’s MCP server.

• Copy puts the line on the clipboard.
• Open in a New Tab, shown when the agent is on this Mac (else “Not found on this Mac”), types the line into a new tab with no Return. Next Term never runs it, never reads or writes an agent’s settings, and that tab refuses text typed by an agent. You read it and press Return, and the agent’s own command adds the server.
• Signing in is the agent’s: /mcp in Claude Code, codex mcp login <name> in Codex.
• Claude Code’s lines add --scope user, so the tracker works in every project. OpenCode adds a server by asking its questions one by one, so its row has Show how, a link to OpenCode’s own page. A line is never guessed: an agent and tracker with no line on either page get none.

The lines: Linear, GitHub, Jira, Notion and more

The lines for Claude Code and Codex, as they are typed:

claude mcp add --transport http --scope user linear-server https://mcp.linear.app/mcp
codex mcp add linear --url https://mcp.linear.app/mcp
codex mcp add github --url https://api.githubcopilot.com/mcp/ --bearer-token-env-var GITHUB_PAT_TOKEN
claude mcp add --transport http --scope user atlassian https://mcp.atlassian.com/v2/mcp
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp
claude mcp add --transport http --scope user notion https://mcp.notion.com/mcp
claude mcp add --transport http --scope user plane https://mcp.plane.so/http/mcp
codex mcp add plane --url https://mcp.plane.so/http/mcp
claude mcp add --transport http --scope user shortcut https://mcp.shortcut.com/mcp
claude mcp add --transport http --scope user ticktick https://mcp.ticktick.com
codex mcp add ticktick --url https://mcp.ticktick.com
claude mcp add --transport http --scope user todoist https://ai.todoist.net/mcp

Codex reads GitHub’s token from GITHUB_PAT_TOKEN in its own environment; Next Term doesn’t set it or see it.

Wrap Up

Tasks › Wrap Up… (⌃⌘W) ends a day of work with agents. It asks the agent tabs of the window for a short handoff file each, and once you have read them, turns the next steps they wrote into tomorrow’s tasks. It needs a project window in front; with none it is greyed, and its tooltip says “Open a project window first.”

Who is asked

The sheet lists the window’s tabs that run an agent (Claude Code, Codex, Gemini CLI and the rest), in tab order. A tab that is ready is ticked. Every other one is greyed and can’t be ticked, with why:

• working: the agent is busy, or input went in moments ago.
• asking: it waits on a decision of yours.
• has your text in its prompt: you typed something there and haven’t sent it.
• on a server, locked, exited, can’t see its prompt: Next Term can’t type there safely.
• not in this project’s top folder: the handoff’s path is relative to the project, so it would land somewhere else.
• today’s handoff names are used up: 99 handoffs from that tab today already.

A tab that becomes ready while the sheet is open stays unticked: only you add it. A ticked tab that starts working is unticked with its reason. At Ask (Ask 2 Agents, say) each tab is checked once more, and one that stopped being ready is skipped and gets nothing.

The request

Ask types one fixed line into each ticked tab and presses Return, so the agent starts at once. This is the one line in Tasks typed with its Return, and it is the same line every time: it goes only to the tabs you ticked, never off the Mac. For a tab titled “API tab” on 18 October 2026 it reads:

Write a short handoff for this session to docs/handoffs/2026-10-18-api-tab.md (create the folder if needed) with exactly these sections: ## Done, ## Next (one "- " line per next step, each a task someone can start tomorrow), ## Open questions, ## How to resume. Write only that file; change nothing else and don't commit it.

It holds no task text, no project name and no stored key, and the path is relative, so no home folder or user name is typed. A handoff in that shape looks like this:

## Done
- Moved the acme/shop cart total into one function
- [x] Fixed the rounding of discounts

## Next
- Add a test for a cart with only free items
- Show the total with tax on the checkout page
- Ask the payments team about refunds over 30 days

## Open questions
- Should a voucher apply before tax?

## How to resume
Open cart/total.ts and run the cart tests.

Its three Next items become three tasks to review.

The handoff file

• Its name is the day and the tab: 2026-10-18-api-tab.md, then -2 up to -99 when the name is taken by a file already there or by another tab in the same Wrap Up. The tab’s title is masked before it becomes a name, and only letters, digits and - are kept.
• Its folder is docs/handoffs in the project, unless the project has its own: Settings › Tasks › Handoff folder (settings). The handoffs are files in your project, and stay there whatever you do in the review.
• Waiting. Wrap Up looks for each named file once a second. A row reads Asked until the file is there, Writing… while it still grows or the agent still works, then Ready to review. After 5 minutes it reads Still writing, with Skip and Keep Waiting. Only the file named in the request is read, and never through a link.

Odd files are read too

Agents don’t always follow the shape, so the reader is lenient:

• A heading is a # heading of any level, a line in bold alone (**Next**), or a line ending in : (Next steps:). “Next steps”, “To do” and “Follow-ups” all count as Next; “Blocked” and “Questions” as Open questions.
• Next items are list lines (-, *, +, 1., 1)), with or without a box. An item ticked [x] is shown unticked. A wrapped line joins its item; prose under Next with no list becomes one item per line.
• An item is cut to 200 characters at a word, and repeats are dropped.
• A file over 256 KB is read only to 256 KB, and the review says so. A file that isn’t text isn’t read.

Review, then Add

The review shows one section per tab, with the file’s path, Show File (the masked text) and Reveal (the file in the Finder). Each Next item is a ticked, editable task for tomorrow, going to the project’s destination (where tasks go). A handoff with no Next items, or a tab skipped, shows why and one empty row, and Add Row adds more by hand.

Nothing is posted until you press Add 3 Tasks (the count is what is ticked). It sends the ticked tasks the way Add Task does: the one-minute duplicate warning, What’s sent, Undo, and Through Your Agent typed with no Return. Cancel posts nothing.

Post Update

Tasks › Post Update… drafts a Done / Next / Blocked update from today’s work, for you to copy, save or hand to an agent. Like Wrap Up, it needs a project window in front.

It opens with “Gathering today’s work…” and fills one editable draft: a heading such as ## Update: shop, 18 October 2026, then ### Done, ### Next and ### Blocked, each with - items, or - None. The draft comes from three places, all on this Mac:

• Today’s handoffs in the project’s handoff folder: their Done, Next and Open questions (as Blocked). An item ticked under Next counts as Done.
• Today’s tasks sent from this project, under Next, with where each went (Reminders, acme/shop), from the posted record. A task that opened a page says “page opened”, since Next Term can’t know you created it.
• Today’s commits, under Done. git runs once, read-only, in the project’s main checkout, across every branch and worktree, and only for commits whose author is your own git config user.email. Never everyone’s commits. With no email set there are no commit lines, and the sheet says “No commits: git has no user.email in this project.”

Every character can be changed, and Start Over builds it again. Then:

• Copy puts it on the clipboard as plain text.
• Save to Project writes docs/updates/2026-10-18.md in the checkout the window shows, then -2 and on. It never writes over a file, refuses a linked folder, and never stages or commits it.
• Send Through an Agent Tab… asks Where to post: (such as “Slack #team”) and an Agent tab:, then types Post this update to <where>, exactly as written: and the update into that tab, with no Return. You read it there and send it, and your agent posts it with its own tools. A draft over 4,000 characters is refused: copy it instead.

Next Term never posts the update anywhere itself.

Agents add tasks: add_task

An agent in any tab can leave a task too, with Next Term’s MCP tool add_task (see Orchestrate agents). It takes a title, and optionally notes (Markdown; list lines become steps), when (today, tomorrow, the default, or a date as YYYY-MM-DD), project, reason and destination.

• destination is project (the default) or todo_folder. With project, the task goes where the project’s tasks go; with todo_folder, always to the todo folder, for a task meant for tomorrow’s agent in this project. An agent can’t name an app, a page or an agent tab: where your tasks go is your choice. Anything else is refused, and nothing is added.
• It asks on the Mac first. A window like the one for the other tools that change things names the tab that asks and the agent’s reason. For the todo folder it shows the exact file it would create: its name and every line. For any other destination it shows the same line and the same masked text the Add Task sheet would, and that window is always on the Mac: a task never leaves Next Term before you Approve it there. Decline, or no answer in about 50 seconds, adds nothing.
• Stored keys are masked as ••• before you see the task, and it is written or sent masked, best effort as above.
• Where you were comes from the tab, never from the agent’s words: the branch, the tab, its agent and its resume command, as Settings › Tasks says. added_by names who asked, such as “Claude Code in tab “api””.
• The project is the one the agent names, else its window’s, else the only project open. A call with something wrong, such as no project to put the task in, an app that isn’t installed or a destination with details missing, is refused before you are asked, and nothing is added. A project whose tasks go Through Your Agent refuses project and tells the agent to post it with its own tools or pass todo_folder.
• The answer says where the task went (todo_folder, reminders, things, shortcut, todoist, omnifocus, github, gitlab, linear, trello or azure_boards), its title, how many steps it has and the day it is planned for. The todo folder’s answer gives the file’s path; a page or Quick Add says "waiting_for_user": true, since nothing is added until you submit it. The notice shows in the window too.
• Claude Code finds it through its tool search when you ask for a task, so it costs nothing in a session that never adds one.

Not yet

Not yet These are not offered yet. The held destinations wait until each is checked by hand on a real account:

• Jira’s prefilled new-issue page. It shows in Send Tasks To ▸, greyed: Atlassian turns off Jira’s prefilled create page in Jira 9 and later. Post to Jira Through Your Agent instead.
• TickTick. Its add link hasn’t been checked with its Mac app yet, so it shows greyed too.
• Self-managed GitLab and GitHub Enterprise. Each needs a host field and its own check. GitLab here is gitlab.com, and GitHub is github.com.
• Some Connect a Tracker lines. Asana (its server needs an OAuth app of your own), ClickUp and Azure DevOps (no line from their own page yet) are under “Not listed yet:”. In a tracker’s own rows, GitHub has no Claude Code line (GitHub’s line writes your token into Claude Code’s settings file), and Gemini CLI has no line for any tracker (“No line from <tracker>’s own page yet.”).

A deadline you set yourself (due) isn’t offered yet either: the day a task has is the day it is planned for.