Tutorial

Your first agent task

Hand a change to a coding agent, follow every step it takes, answer what it asks, then review and commit the result. About fifteen minutes.

Before you start

A task runs on a coding agent you already use, such as Claude Code or Codex, installed and signed in on this computer. Deska does not run a model of its own for tasks: the agent works with your account and your plan.

Open Settings → Agents (Cmd/Ctrl,) to check. Each agent under Connected agents shows its account once it is signed in, and New tasks use picks the agent a new task starts on. Expand an agent to install it, sign in or run a check.

Settings, Agents page: Dex answers with, Dex reasoning effort, New tasks use, and the connected agents with their accounts

Open a project first (see Your first project): the agent works in that folder.

1. Describe the task

Click New task at the end of the crumb, or press Cmd/CtrlI. Write what you want done the way you would ask a colleague: what is wrong or missing, and how you will know it is right.

The New task composer asking What should we build in storefront, with a prompt typed in and the model, mode and branch controls

The model chip (here Sonnet 5.5) picks the agent and the model for this task.
Build lets the agent edit files. Switch it to Plan (or press ShiftTab) and the agent researches and proposes a plan first, without touching anything.
The settings chip (here Full access, the default) sets what the agent may do without asking: Supervised asks before it acts, Auto accept edits and Auto ask less, Full access never asks.
The branch chip (main) says where the task runs: the checkout you are in, or a new worktree of its own. See Run tasks in parallel.
The microphone dictates the prompt instead of typing it.

Press Start or Enter.

2. Follow the work

The task opens as a thread. Your request sits at the top, then everything the agent does, in order: what it reads, what it edits, the commands it runs, and what it tells you along the way. The header shows the agent, where the task stands (Done here), the branch and how many files changed.

A finished task thread: the request, the files the agent read and edited, the test run and the agent's summary of what changed

Want something different? Type in Message this agent at the bottom and send a follow-up; the agent keeps the whole conversation. You can close the panel at any time: the task keeps running and stays in the Inbox.

3. Answer when it asks

Depending on its mode, an agent stops to ask before it runs a command or changes something. The thread shows exactly what it wants to do and waits for you.

A task waiting for approval to run npm install nanoid, with the buttons to approve, always allow, decline or cancel the turn

Approve once lets this one action run.
Always allow this session stops it asking again for the same kind of action in this session.
Decline refuses this action; Cancel turn stops the turn altogether.

Sometimes the agent needs a decision instead. A question comes with its options; pick one, or write your own answer.

A task asking Should gift cards expire, with the options After 12 months and Never

TipYou do not have to watch. The Inbox chip at the bottom of the window lights up when a task needs you, and your phone can get a notification too.

4. Review and commit

When the agent is done, open Source Control from the Tools rail on the right. Changes lists every file that changed, with the lines added and removed; click a file to read its diff.

Source Control with two changed files, cart.ts modified and currency.test.ts untracked

Stage what you want to keep: + on a file, or Stage all.
Write the commit message, or press Generate message to have your agent draft one from the diff.
Press Commit. Then Publish branch sends a new branch to your git host; once it is there the button reads Push. The arrow beside Commit does both in one step (Commit & Push).

Source Control with both files staged, a commit message written and the Commit button ready

Not happy with a change? Discard on a file throws its changes away after you confirm, or send the agent a follow-up from the thread.

5. Keep track in the Inbox

Every task you start lands in the Inbox. The chip at the bottom right says how many tasks need you; click it for the short list, with tabs for Needs you, Working and Landed.

The Inbox popover with four tasks: one waiting for approval, one for input, one working and one finished

Open inbox shows the whole board, grouped by what each task wants from you: Needs you, Working, Landed and Idle. The scope buttons narrow it to this worktree, this project or everything, and Filter picks statuses and agents.

The Inbox board with Needs you, Working and Landed groups, each task with its status and agent

Press Cmd/CtrlShiftJ to jump straight to the next task that needs you. More in Agent threads.

Run tasks in parallelGive each task its own worktree and keep several agents busy at once.Coding agentsSetup, models, modes and what each supported agent can do.Agent threadsThreads, the Inbox, the queue and every way to steer a task.Code, Git & filesThe editor, Source Control and the file browser in depth.