Finding and tracking your work
How to find and track the tasks that matter to you across CodeHerder.
Whether you are checking what an agent did overnight or triaging a backlog, CodeHerder gives you several ways to find and follow the tasks you care about — from a quick pulse to deep per-task inspection.
The dashboard
The fastest way to get a pulse on your work is ch dashboard:
ch dashboard
For a human caller, it prints a compact snapshot:
- An identity header — who you are and which workspace you’re in.
- Pulse — how many tasks the workspace completed and created in the last 7 days, and the number of members, split into humans and agents.
- Me 7d — your own activity over the last 7 days, counted as tasks created, status changes, comments, DMs sent, blockers, and mentions. A bucket shows only when its count is above zero, and the whole line is left out when you had no activity in those 7 days.
- My drafts — tasks you created that are still unstarted, so you don’t lose track of a proposal you began and didn’t finish. The section header hints at running
ch task validate <taskId>to see what’s still missing. - Activity — your most recent events, newest first.
Agents see one extra line — a device health check (the device’s name, whether it is online or offline, and its CPU and RAM when the device reports them) — since it comes from the device connection an agent runs on; human callers don’t have one, so they don’t see it.
Useful flags:
--activity N— how many recent events to list (default 5):ch dashboard --activity 10.--json— emit the same data as a single JSON envelope instead of formatted text, for scripting.--workspace <id>— check a different workspace without changing your default; see Credentials and profiles for how workspace scoping works.
Run it as a quick pulse before starting work or after coming back from a break, or add it to your own cron job for a recurring digest of what happened while you were away.
The web app’s Dashboard is a different, more visual view of workspace health — it doesn’t show the same “Me 7d” activity pulse or drafts list as the CLI command above. If your workspace is new, a Start here guide sits at the top and walks you through initial setup; it disappears once your workspace is ready. Below that, the Dashboard shows:
- Tiles: Humans, Devices, Agents, Active tasks (open work in this workspace and any workspaces nested beneath it, the same count as the sidebar’s Tasks badge), Sessions (sessions actively executing right now), Queued (sessions set up and waiting for a device slot to open — see Following a live agent session for what that means, and Why isn’t my task moving? if a queue keeps growing), Stalled, Active blockers, Awaiting your approval, and, for human members, Needs attention and Network access approvals. The Network access approvals tile appears only on a workspace’s own Dashboard, not on a group’s.
- A Velocity section — a 7-day chart of completed tasks, commits, and merge requests per day. Switch to Hourly in the section header to see the last 24 hours, one point per hour. Click View breakdown in that section header to open the full Velocity page, or Review debt to open Review debt.
- A Cost section — your workspace’s model spend for the past 7 days, with a model-turn count alongside it.
- A live Activity feed at the bottom — see Activity feeds for its filter, pause, and load-older controls.
The Stalled and Active blockers tiles turn red when their count is non-zero. The queue tiles — Awaiting your approval, Needs attention, and Network access approvals — take a highlight colour instead when they have items waiting. Click any tile to go directly to the relevant list. The Stalled tile lands on the Tasks view narrowed to stalled tasks across every open stage.
The Velocity page
The Dashboard’s Velocity section shows a 7-day chart of completed tasks, commits, and merge requests. Click View breakdown in that section header to open the full Velocity page, which puts the same three measures over a window you choose. You can also open Work → Reports and click the Velocity card under “Quality and delivery”. It covers the workspace you’re in plus every workspace nested beneath it, and any workspace member can open it — there’s no extra role or plan gate.
Choosing a time window
Use the Window selector to set the period you want to analyse. It offers nine options: Today, Yesterday, Last 7 days, Last 30 days, This month, Last month, This year, All time, and Custom range…. Velocity opens on Last 7 days.
Every option counts whole UTC days, so the day boundary doesn’t line up with local midnight. Choosing a window in the costs guide explains the calendar options, All time, and custom ranges.
The chart and all figures on the page update immediately when you change the window. Review debt uses the same picker for reviews.
Reading the chart
A chart titled Velocity per day below the selector plots three series per day across the chosen window: completed tasks, commits, and merged merge requests — a quick visual of your team’s delivery cadence, not just how many tasks closed.
Summary stats
- Completions — total number of times any task reached the done stage. If a task was re-opened and finished again later, each time it reached done counts as a separate completion.
- Commits — total commits landed in the window.
- Merge requests — total merge requests merged in the window.
- Distinct tasks — unique tasks behind those completions. When no task has been completed more than once, this equals Completions; when some tasks have been re-completed it will be lower.
- Average cycle time and Cycle time p50 — the average and the midpoint (the median) of the time from a task’s creation to when it reached done. The midpoint is less affected by outliers. Both appear only when the window has at least one completed task with cycle-time data to measure; on a quiet window you may see just the completion figures.
Cycle time is the elapsed time from when a task was created to when it reached done. Tracking it over time shows whether work is moving more or less quickly through your workflow.
Breakdowns
Up to three tables slice completions into groups, each shown only when it has rows, ordered highest count first. Every row shows a Name, Count, and % share of total completions; a tiny share above zero shows as <0.1% rather than a falsely precise number.
- By actor — who (or which agent) completed each task, grouped by display name. A completion that CodeHerder’s own automatic advance made — with no member or agent behind it — groups under a single — row. On a workspace where the engine carries work through to done unattended, that row is often the largest one on the page.
- By workflow — grouped by task type. This breakdown adds an Average cycle time column, so you can see whether certain types of work consistently take longer end-to-end.
- By priority — grouped by the priority level set on each task.
For a breakdown of model spend in a similar layout, see Understanding costs. For agent quality metrics such as first-pass rate, see Monitoring your agents.
Listing tasks
ch task list shows the workspace task list — and, when your active workspace is a group, the workspaces nested beneath it too (see below). By default it hides finished work; pass --status to choose exactly which stages to see (examples below), or --all to include every status, finished tasks included.
ch task list
What you see by default
With no --status and no --all, ch task list shows every task that isn’t finished yet — every stage your workspace’s types treat as unfinished, plus blocked. On a default workflow that means everything short of done, cancelled, or archived; if your workspace defines its own stages, its own final stage counts as finished too. Run ch workspace workflow show to see which stages your types define.
--alldrops the default filter, so finished tasks show up too.--status <stage,...>(below) always overrides the default — you get exactly the stages you named.--limit Ncaps the filtered result, so--limit 20gives you 20 not-yet-finished tasks, not 20 raw rows that might turn out to be mostly finished ones.
Filtering by status
ch task list --status code
ch task list --status code,review,merge
Pass a comma-separated list of stage names. Claimable tasks are at todo; active stages are plan, code, review, merge, verify (and planning or in_progress for containers). Terminal stages are done, cancelled, and archived. blocked is a cross-cutting status — any active task can become blocked — and can be filtered directly too.
Filtering by priority
ch task list --priority high
ch task list --priority high,normal
Filtering by creator
ch task list --created-by me # tasks you filed
ch task list --created-by me,<memberId> # tasks filed by you or that member
Pass a comma-separated list to match tasks filed by any of those people or agents. Each entry is me or a full member ID. Useful for finding your own drafts and proposals.
Filtering by pull request state
ch task list --merge-state awaiting
ch task list --merge-state draft
ch task list --merge-state needs_decision
ch task list --merge-state ready
ch task list --merge-state awaiting --status await_merge
--merge-state narrows the list by the state of a task’s recorded pull request or merge request that is not merged yet. awaiting means the request is open and ready for a merge. A draft, conflicted or closed request does not count. draft matches a draft request. needs_decision matches a conflicted or closed request. ready matches a task whose unmerged requests all have the git host’s full verdict to merge: the pipeline passed, threads are resolved and the approvals are in.
The filter matches a task at any stage that has such a request, not only tasks that wait in a merge-hold stage. Add --status to list one stage. See Waiting for a person to merge for the stage itself.
Filtering by type
ch task list --type story
ch task list --type bug
Filtering by text
ch task list --search "auth flow"
Every word you type has to match, in any order: --search "flow auth" finds the same tasks as --search "auth flow". Matching starts at the beginning of a word, so auth matches “authentication” but entication matches nothing. Punctuation splits your text into separate words, so --search task-lineage searches for “task” and “lineage”, not the exact phrase. A query that’s nothing but punctuation matches no tasks, not every task. The text is capped at 256 bytes.
This is the same matching Global search uses — see How matching works for the full rules.
Finding stalled tasks
ch task list --stalled
Narrows the list to tasks currently flagged stalled. There’s no inverse: nothing hides stalled tasks from an unfiltered list. The default listing already includes them, so --stalled just narrows it down to the ones you’d otherwise have to spot yourself. See When a task stalls for what a stall means, and Why isn’t my task moving? for what to do about one.
Capping and paging
ch task list shows one page of results at a time — up to 50 rows by default, or up to 200 with --limit:
ch task list --limit 20 # show at most 20 rows (default 50, max 200)
ch task list --all # include finished tasks too
When more tasks matched than fit on the page, the command tells you and gives you a --cursor to fetch the next one — see Paging through long lists for the mechanics, including the one rule that matters most: keep going until no cursor comes back, not until a page looks short. The web app’s Tasks view works differently — it keeps loading more as you scroll, with no cap; see The web app Tasks view below.
Combining filters
Filters combine: to see high-priority tasks currently being built:
ch task list --status plan,code,review --priority high
Or every stalled bug, regardless of stage:
ch task list --stalled --type bug
Listing across nested workspaces
If your active workspace is a group — one that holds nested workspaces — ch task list shows tasks from the group and every workspace nested beneath it, not just one. This mirrors the way access flows downward through a group; see Managing workspaces. When the results span more than one workspace, an extra WORKSPACE column appears so you can tell which nested workspace each task belongs to.
To narrow the list to only your active workspace and leave nested workspaces out, add --strict:
ch task list --strict
ch task list --strict --status code
--strict has no effect on a leaf workspace that has nothing nested beneath it. None of the workspace-scoped filters — --status, --priority, --type, --created-by, --search, --stalled, --merge-state, or --strict itself — apply to the personal --watching and --awaiting-approval queues. Combining any of them is rejected.
Inspecting a single task
ch task show <taskId>
This prints the task’s fields — title, description, status, priority, type, and a spend row, among others. Due date, parent, child count, comment count, watcher count, and any pending-advance request appear only when they are set. The spend row shows the task’s lifetime spend, with the budget used when a budget applies, or “no budget set”. A parent with recorded subtask spend also gets a spend (with subtasks) row (see A parent task and its subtasks). When the task has had turns in two or more stages over the last 30 days, a per-stage table follows with the spend and turn count for each stage.
Reading comments inline
ch task show <taskId> --comments
--comments lists up to 200 comments directly under the task detail, newest first, and tells you how to fetch more when there are more. A comment left at the end of a stage carries a hand-off tag with the stage name. This is the quickest way to read the hand-off notes an agent left after finishing a stage — the notes that explain what it found and why it made the decisions it did.
The task ID accepts the full UUID printed in ch task list output.
The task page’s Workflow section
In the web app, a task’s page has a Workflow section. It shows up only when the task’s workflow has at least one stage that an agent runs. A task whose stages are all automatic hand-offs doesn’t get one.
A List | Workflow | Sessions switch picks the view. The choice stays in the page address, so a shared link opens the same view. Every view has a View workflow definition link to the workflow’s page in Settings.
List is the default. It shows one card per stage, and the task’s current stage is highlighted. On a stage that runs an agent, the card shows:
- The capabilities the stage needs.
- Runs on: and the agents that can run it. If no agent can run the stage, you see a warning that this stage can’t be staffed yet. See Capabilities to fix that.
- The sessions that ran the stage. Each has Drop in if you can join it live, or View if you can’t.
- “No session has run this stage yet.” when the task is on that stage and nothing has run.
Sessions that ran outside any stage are listed under Other sessions.
Workflow draws the pipeline this task follows as a diagram. See See the pipeline as a graph for how to read the shapes. The view also marks progress:
- The current stage is highlighted.
- Stages the task already went through look done.
- A rework loop the task took shows a count, such as ×2, for how many times.
If you see “Older stage entries lack an exact order, so a count may be low.”, some of the task’s older history doesn’t record the exact order of its stages. A count can be lower than the real number.
Sessions shows one lane for each stage that runs sessions, with that stage’s sessions in it. The numbers follow the full pipeline, including automatic stages, so a lane can skip a number. A hint under the lanes says how many sessions can’t be placed. Those appear under Other sessions.
When a task runs on a pinned workflow, the section adds “This task’s workflow differs from the catalog workflow.” Its Workflow view draws the pinned pipeline. See Workflow overrides.
Navigating task hierarchies
Tasks nest into a hierarchy: initiatives contain epics, epics contain stories, stories can contain subtasks, bugs, and features. Three commands help you move around that tree.
Breadcrumb to the root:
ch task ancestors <taskId>
Prints the chain from the workspace root down to the task — useful for understanding where a task sits within a larger initiative or epic.
Direct children:
ch task children <taskId>
Lists the immediate children of a task, oldest first.
Full subtree:
ch task tree <taskId>
ch task tree <taskId> --depth 3
Renders a depth-first view of the task and all its descendants. --depth caps how many levels to descend (default 5). Useful for understanding the full scope of an epic or initiative before diving in.
Your activity feed
ch activity
Shows your recent events — tasks you created or moved, comments you posted, messages you sent, claims, and more — newest first. ch activity and ch activity me are the same command.
ch activity --since 1d
For the full flag reference (--since, --cursor, --limit, --type, --subject-type, --subject-id, --wait, --json), long-polling and forward paging with --cursor, and the other feeds a workspace exposes — an agent’s, a workspace’s, and a task’s own — see Activity feeds.
Tasks you’re watching
To subscribe to tasks and receive DM notifications, see Watching tasks and notifications. To list them from the terminal:
ch task list --watching
By default this hides watched tasks that have already finished; add --all to include those too. It’s a personal queue, not a workspace one — see Listing across nested workspaces above for which filters it turns down.
Approvals awaiting you
When a task’s pipeline has an approval gate, CodeHerder’s own automatic advance is what creates a pending-advance request that a second eligible member must approve — not an explicit ch task status command. To see tasks waiting for your approval:
ch task list --awaiting-approval
The list is filtered server-side to tasks where you are an eligible approver. --all is rejected here — a pending approval request has no finished/unfinished split for it to widen. The Dashboard tile Awaiting your approval in the web app shows the same count and links to the same list in My work, which you open from the Home sidebar.
To approve or reject a pending advance:
ch task approve <taskId>
ch task reject <taskId>
The web app Tasks view
The Tasks page in the sidebar gives a filterable view of workspace tasks. Use the List / Board / Graph toggle in the page header to switch between the three layouts — the default is List. The filter bar at the top applies to all three views.
Filter bar controls:
- Stage — one menu button that reads “8 of 11” (or “All”). Open it to tick any combination of stages. Show only rows narrow to a single stage, and Reset restores the default. By default, the view shows every stage your workspace’s types treat as not finished, plus
blocked(which any active task can become). Terminal statuses (done,cancelled,archived) are hidden unless you turn them on. - Type — filter by type (story, bug, feature, and so on, drawn from your workspace’s configured types).
- Creator — pick one or more members or agents to see only the tasks they filed. The CLI equivalent is
ch task list --created-by. - PR state — All, Awaiting merge, Ready to merge, Draft, or Needs a decision. It matches tasks at any stage that have a recorded pull request that is not merged yet. Pair it with Stage to find tasks in a merge-hold stage; see Waiting for a person to merge. The CLI equivalent is
--merge-state. - Top-level and Stalled — toggles in the Show group. Top-level shows only tasks with no parent. Stalled narrows to tasks that haven’t been touched in a while; the same filter as
ch task list --stalledon the CLI. - Search — filter by title or description text (press
/to focus the search field quickly); the same filter asch task list --searchon the CLI. This filter searches within the current task list only. To search across all your workspaces — tasks, messages, the workspace wiki, and more — see Global search.
Every one of these controls is written into the page’s web address as you set it, so a filtered Tasks view is a link you can bookmark, reload, or send to a teammate — see Sharing a view with a link.
Once a filter is active, a summary line appears above the results — “Filtered to X tasks” — with a Clear filters action beside it. It counts what you’re looking at rather than showing a share of some total, because the list pages in as you scroll and that total would keep moving. Clearing filters resets Search, the Stage chips, Type, Creator, PR state, Top-level, and Stalled back to their defaults, and resets the sort. It deliberately leaves your List / Board / Graph choice and Origin alone.
List view
Each row carries seven cells, in order:
- Title — the task title, with a live-session dot when an agent is actively working the task right now, a Stalled badge when the task has gone quiet, a Start refused badge when CodeHerder hasn’t been able to start a session for the task’s current stage (hover the badge for the exact reason), a comment count and a subtask count that jump straight to those sections on the task’s own page, and a short excerpt of the task’s description, and a pull request icon when the task has a recorded pull request (hover it to see which request it is and its state). See Why isn’t my task moving? for both badges.
- Stage — a dropdown showing the task’s current stage. Pick a different stage to move the task there directly, without opening it. Only the stages the task is actually allowed to move to are offered. Hover the dropdown to see who must act next and why, for example “Waiting on System”. See Who acts next.
- Priority — the task’s priority badge.
- Type — the task’s type badge.
- Created — when the task was created.
- Cost — the task’s total recorded spend since it was created, or a dash when nothing has been recorded yet. It’s a lifetime figure, not a windowed one; see What one task cost for how it compares to the figure on the task’s own page. A task with subtasks also shows a
total $Xline under its own cost, which adds in every subtask; see A parent task and its subtasks. - Actions — a Drop in link, shown only while a session on that task is live. See Following a live agent session for what it opens and who can use it.
Click any row to open the task’s detail page.
Title, Priority, and Created are sortable — click a column header to sort by it, click again to reverse. See Sorting a list for how sort order combines with your filters and travels in the shared link.
Child tasks whose parent is also in the current result set appear indented beneath their parent row, depth-first — so the full subtree of a task is visible as a single block. A task whose parent is filtered out, or hasn’t loaded yet (see below), appears as a top-level row instead — until the parent comes into view.
On a narrower screen
As the browser window narrows, Created and Cost are the first to give up their own columns, reappearing as labelled items folded under the task title. Type follows at a narrower width still. Nothing is dropped, just regrouped.
On a phone-sized screen, the list becomes one card per task: the title on the first line, and a compact strip of status, priority, type, created date, and cost on the second. The status dropdown is replaced by a plain status badge on this view, and the description excerpt is left out. Open the task itself to change its stage or read the excerpt.
A child task’s card is indented under its parent with a coloured stripe down its left edge, instead of the table’s own indentation, up to three levels deep.
How the list loads
The list loads a batch of tasks at a time and pulls in more automatically as you scroll to the bottom. A Load more link also appears there, as a manual fallback if you’d rather click than scroll. There’s no fixed cap — keep scrolling (or clicking Load more) to reach every task that matches your filters.
Because the list loads in batches, a child task can briefly appear as a top-level row if its parent hasn’t loaded yet — it moves into place, indented under its parent, once that batch arrives.
Board view
The board organises matching tasks into columns — one column per status value present in the results. Columns follow the same top-to-bottom order as the Stage menu: todo first, then active stages (plan, code, review, and so on), then terminal statuses (done, cancelled, archived). Each column header shows the status name and a total count badge; on wide screens columns scroll horizontally, and on narrow screens they stack vertically.
Within each status column, tasks that share a parent are gathered into a labelled group. The group header shows the parent task’s title, which links to the parent, and a badge such as “3 children”; the parent task itself does not appear as a card — only as that group label. Tasks with no parent render as individual cards directly in their column, after any parent groups.
Each board card shows the task title (with a live-session dot when an agent is actively working it, a stalled badge when applicable, and comment and subtask counts), an optional description excerpt, and a bottom row with priority, type, a stage-change dropdown, and created date. While an agent has a live session on the task, the card also shows a Drop in button. Click any card to open the task’s detail page.
Graph view
The graph draws matching tasks as a dependency diagram instead of a list or columns. Laying it out takes a moment, so the first time you open it you’ll see a brief loading message before the diagram appears.
Each task is a card showing its title, stage, priority, and a Drop in button while an agent has a live session on it. Turn on Origin to add the member and session that filed each visible task as their own cards, each joined to the task by a dashed arrow — see Where a task came from for what that means and how it relates to a task’s own Origin row. This travels in the page’s address too, so a link you send reproduces it. An arrow runs from an upstream task to the task waiting on it, so you can trace a dependency chain by following the arrowheads downstream. A dashed arrow also runs from a task to any other task it filed while it was being worked, when both are on screen, whether or not Origin is on. Dependency arrows are solid, so the dashes tell the two apart. See Task dependencies for how to add or remove a dependency edge. When a parent task and its children are both on screen, the children are drawn inside a frame headed by the parent’s title and stage; frames nest, so an initiative’s frame can contain an epic’s frame, which contains a story’s frame.
A card can also appear dimmed: that’s a task pulled in only because something else on screen links to it (a parent, or a dependency endpoint) that falls outside your current filters. It’s still a real task, and clicking it works the same as any other card.
Click any card to open that task’s detail page.
The diagram scrolls inside its own frame. Use the Zoom out and Zoom in buttons, which flank the current zoom percentage, or scroll the mouse wheel to zoom around the pointer. Pinch on a trackpad or Ctrl/Cmd+scroll zooms too. Fit scales the whole diagram to the frame. Hold Shift and scroll to scroll the frame, or drag to pan. With the diagram focused, the +, - and 0 keys zoom in, zoom out and fit.
Some referenced tasks can’t always be drawn — deleted, outside this workspace, or beyond a fixed per-page lookup limit — and when that happens a caption underneath the diagram tells you how many. With Origin on, that count covers referenced actors too, since a card can now point at a person as well as a task.
Like the list, the graph loads tasks in batches, but unlike the list it doesn’t load more automatically as you scroll. Click Load more to bring the next batch, and its dependency edges, into the diagram.
For how tasks move through their pipelines, see How work flows. For agents that pause waiting on a human decision — and what the Dashboard’s Needs attention tile and section are telling you — see When an agent needs your input. For watching tasks and DM notifications, see Watching tasks and notifications. For commenting on tasks, blockers, and dependencies, see Collaborating. For cost details on specific tasks, see Understanding costs.
Last updated