Day to day
Tasks
ClickUp tasks and GitHub issues in a single list, ready to become a session with one click and to come back as a comment when the agent is done.
The inbox
The tasks screen, at ⌘⇧T, joins two sources and groups everything by stage, always in the same order: to do, in progress, in review, done and dropped. The last two start collapsed.
| Source | What comes in |
|---|---|
| ClickUp | Tasks assigned to you, plus the lists you choose to follow. Open ones, and the ones closed in the last seven days. |
| GitHub | Issues assigned to you, plus the repositories you follow. Pull requests never come in. |
There are three filters: the tab per account, the search by title, reference or list, and the option to see only what is yours. The sort order is fixed, by most recent update. The list refreshes on its own while the screen is in view, and opens with the last snapshot when the source is slow.
Connect the accounts
- ClickUp. In Settings, under connections, paste your personal token. It is encrypted in the system keychain, never in plain text. Then pick which lists to follow, on top of what is already assigned to you.
- GitHub. There is no token to paste: it is the same GitHub account the GitHub CLI uses for pull requests. You pick which repositories to follow.
Create a task
The new task button opens a short form: the list it is born in, with the recent and followed ones at the top, the title, the description in markdown, and the pills for status, priority and assign to you, which comes checked.
There are two finishing buttons: create, or create and delegate to an agent right away. The list of the last task is remembered for the next one.
A GitHub issue is always born open and with no priority, because GitHub has no such fields. The pills apply to ClickUp.
Delegate to an agent
Delegate opens the new session dialog already filled in, and still editable before you confirm:
- Project, the one you used last time for that list.
- Isolated session checked, with the branch name derived from the reference and the title of the task.
- First prompt built from reference, link, status, labels and description, ending with the instruction to answer with a short summary, because that summary is what goes back to the task.
- Session title equal to the reference plus the title.
As soon as the session exists, it is linked to the task and Deck moves the task to in progress, if it was still to do and the list has an equivalent status.
The prompt text is a template, in Settings, under agents, with variables for reference, title, description, link, status, list, labels and source. You can rewrite it your way and go back to the default whenever you want.
Delegate several
Check the tasks in the list and use the delegate button. The dialog asks for one project and one agent for the batch, and warns that each task gets a worktree and a session of its own, opened in the background.
They run one after another and stop at the first failure, saying how many went through and why it stopped, instead of leaving things half done with no explanation. A task that already had a session drops out of the selection on its own.
Send the result back
When the agent finishes, the tasks icon gets a counter of what is ready to send back. Send back opens a comment already drafted with facts from git: the branch, how many commits it brought, how many files changed and the pull request number, if one exists.
- Review the draft, or use the button that asks the agent for a summary and swaps the text for its answer.
- Pick which status the task goes to, or keep the current one.
- Send. Deck posts the comment, changes the status and marks the session as sent back.
If something fails halfway, the app says exactly where it stopped, such as the comment going through but not the status. And the same session never posts the same comment twice, not even after you restart the app.
The comment goes as plain text, and sensitive data the agent may have repeated is masked before sending. Even so, read it before you send: it lands on the ticket, not in your terminal.
Inside the session, the task pill in the header opens the same path: view at the source, view in tasks, ask for a summary and send back.
What agents can do
With the task tools turned on, the agents in your sessions can list, create, move and comment on tasks from the connected accounts, and ask which task belongs to the session they are in.
- Read reaches what the screen already shows, plus the repositories of the open projects.
- Create only works in the lists and repositories you follow. Outside them the tool refuses and explains why.
- Turning it off takes the tools out of every session, in Settings, under connections.
If what you want is the other direction, leaving the task and arriving at reviewed code, see Pull requests.