Skip to content

Tasks

The work inside a workspace: what was asked for, what state it is in, and a note timeline saying how each piece was done.

Where
A workspace → TasksIn the app (sign-in required), opens in a new tab.
Reading time
2 min read

How it works

A task is one piece of work in a workspace. It has a title, a description, a status (todo, in progress, delayed, done), an optional due date, an assignee and a parent, so a list of subtasks under one heading is a real structure rather than a convention.

The part worth knowing about is the note timeline. Agents do not just flip a task to done; they leave a note saying how, and notes carry attachments, a document, a shared file, a link, or a recorded video of the change working. A video attached to a note plays in the timeline rather than arriving as a link somebody has to decide to open, which is the difference between a walkthrough people watch and one they do not.

That is what makes the board readable weeks later: "what was done" and "how it was done" are in the same place, and neither is in someone's memory.

Steps

Following along? Tick each number off as you go.

  1. Open a workspace and choose the Tasks tab.

  2. Type a title in the composer at the bottom and press Add.

    Assign it to a person, or leave it for whoever picks it up.

  3. Click a task to open it.

    The title and description are editable in place.

  4. Read the note timeline under the description.

    Each entry says what happened; attachments render inline, and a recorded demo plays right there.

  5. Add your own note with the composer, attaching a doc, a file or a link if there is one.

  6. Change the status with the status control, or press Mark done and write the note that says how.

    The note is the point, a task closed with no explanation is a task nobody can audit.

  7. Use Recheck against implementation to have the agent compare the board with what is actually built.

  8. Press Auto-complete (the sparkles in the Tasks header) to hand the open tasks to the agent one at a time, only the filtered group's, when the list is filtered to one.

    Jev or OpenAI (Settings → AI → Task checker) checks each is really done before the next; a line above the board shows how far it is, with Stop.

Commands

The same job from a workspace's box, for people who live in the terminal.

devbenchinside the box
  • $ devbench task add "<title>"Add a task from inside the workspace's box.
  • $ devbench task listEvery task on the board.
  • $ devbench task show <id>One task in full, with its note timeline.
  • $ devbench task note <id> "text" --video <url>Add context, or a recorded demo, without changing the task.
  • $ devbench task done <id> --note "how"Close it, recording how it was done.
  • $ devbench todo "<list>" <item>…A parent task with subtasks under it, in one command.

Read next

Getting startedTasks for youAction items that need a person, as opposed to the workspace board, which is work for the agents.Knowledge and filesRecorded demosDevBench records a narrated video of a change and posts it where you will see it, because a green test says the code does not break, not that it does what you asked.Getting startedThe workspace boardEvery workspace as a card, in the column that says what is happening to it, with card, calendar and per-person views.
Report a problem