Project Management

Tasks

A task board your AI agents work directly — assigning a task spawns the terminal, sends the work, and binds the run to it, so the board and Mission Control describe the same thing. Plan and done approval gates reach you wherever you are, and every task is a markdown file in `.1devtool/tasks/` that diffs and travels with your branch. The board itself is two views behind a segmented control — Board, a kanban where every card names its owner, and By agent, a roster reading Working, Waiting for approval, Idle or Offline — with filters for agent, priority, tag and project, a Blocked column that appears only when there is blocked work, and drag-and-drop treated as a request rather than a silent write.

Tasks

More Screenshots

Click any image to zoom in

The Tasks board with one card in the RUNNING column on the grok swimlane
A plan approval gate showing the agent's goal and constraints, waiting on Approve, Request changes or Decline before implementing
The done-gate review dialog showing the agent's report of what it changed and how it verified it, with Approve and Request changes side by side
A Grok terminal receiving the message that it has been assigned a 1DevTool task and loading the tasks skill to fetch the full record before planning

Why You Need This

How this feature boosts your daily productivity

Once you have more than two agents running, the work only exists in your head and in scrollback. You retype a task into a terminal, watch it boot, then go check the other panes — and miss the one that stopped to ask a question ten minutes ago. Tasks makes assignment the same act as dispatch: pick a target and the terminal opens already holding the work, while the card tells you whether that agent is live, waiting on you, idle, or lost. Agents read and write the board through ten MCP tools, but cannot assign themselves work — creating a task is not taking it. Nothing auto-approves either: if nobody answers a gate in time the task blocks, because silence is not consent. And because tasks are markdown in your repo, the plan and the acceptance criteria arrive in the same diff as the code instead of being reconstructed from a chat log afterwards.

How It Works

Get started in 4 simple steps

1
1

Open Tasks on a project

It opens as its own full window like the Git client. A segmented control switches between Board — a kanban where every card names its owner — and By agent, a roster reading Working, Waiting for approval, Idle or Offline.

2
2

Fill the board

Right-click a stack trace or editor selection and Add task, describe a goal and accept the proposed set, or let an agent call tasks_create from the terminal you are already in.

3
3

Assign and run

Picking a target is dispatch — the terminal opens, receives the task, and the run binds to the card, which then reports what that agent is doing right now.

4
4

Answer the two gates

The agent asks before implementing a plan and before closing the task. Approve and Request changes sit as equals, and nothing auto-approves if you do not answer.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# Three agents running
# The work only exists in your head
# Pick a terminal, retype the task
# Watch it boot, go check the others
# One stopped to ask 10 minutes ago
# You never saw it
# Answer, then go check the others again

The 1DevTool Way

Describe the work once on the board.
Assign — the terminal opens already holding it.
The card says live, waiting on you, idle, or lost.
Approve the plan from your phone.

Key Capabilities

Everything included with Tasks

Assign a task and have the terminal spawn, receive the work, and bind the run in one action
Read live agent state on every card — live, waiting on you, idle, or lost
Work a full-window board with Backlog, Ready, Running, Blocked, Review and Done columns
Filter by agent, priority, tag and project, each option carrying a count
Drag a card as a request — a move that skips a pending review is refused and names what holds it
Switch the views rail between Needs me, All projects, and Captured, each with its own count
Approve or request changes on a plan before the agent implements it
Review what an agent claims it finished before the task closes
Answer gates from a review queue, a status-bar badge, or the phone page
Capture a task by right-clicking a stack trace in a terminal or lines in the editor
Describe a goal and have an agent propose a task set you edit and accept
Merge duplicate tasks so one survives and old ids still resolve to it

Why It Matters

The productivity impact of having project management built into your workspace

Assignment Is Dispatch

Picking a target spawns the terminal, sends the task and binds the run, so the board and Mission Control describe the same work instead of two versions of it.

Nothing Auto-Approves

If nobody answers a gate in time the task blocks. Silence is not consent, so an agent never ships an unreviewed plan while you are away.

Agents Cannot Self-Assign

tasks_create always creates UNASSIGNED — creating work is not taking it. That single rule is what stops an agent from filing and claiming its own work for hours.

Tasks Live In Your Repo

Markdown files under .1devtool/tasks/ diff, show up in review, and travel with a branch, so the plan arrives in the same diff as the code.

Ready to boost your workflow?

Download 1DevTool for free and experience Tasks along with 170 other features — all in one app.