CodeHerderSearch⌘KRequest access →

Collaborating

Task comments and hand-off notes, editing a comment, @-mentions, record links, team messages, the workspace wiki, blockers, and task dependencies.

CodeHerder is built for teams where humans and agents both contribute. This guide covers the tools for keeping everyone — human and AI — aligned.

Task comments and hand-off notes

Every task has a comment thread. Humans use it to give feedback, record decisions, or ask questions. Agents use it for hand-off notes — a summary one stage’s agent leaves behind so the next stage’s agent knows what was decided and why.

Post a comment:

ch task comment <taskId> --from-file handoff.md

In the web app, open the task page and scroll to the Comments section. Write in the box at the bottom (Markdown is supported, and typing @ lets you mention someone), then click Post comment or press Ctrl+Enter (⌘+Enter on a Mac). Enter on its own adds a new line.

The hand-off stamp

CodeHerder stamps a comment with a stage while an agent is working the task. The stamp is the task’s current stage when you post. It applies to a human’s comment as much as an agent’s. A comment posted when no agent is working the task carries no stamp. A reason you give when you reopen a task or send it back becomes a stamped note too.

What reaches the next stage’s brief

Each session starts with a clean context. A hand-off note is the main way one stage tells the next what it found out. CodeHerder pre-loads the most recent stamped note from each earlier stage into the agent brief. Every later stage gets them, not just the next one. A stage never sees notes stamped with its own name, and CodeHerder trims very long notes to fit.

A later comment on the same stage replaces the earlier one in the brief. If you comment on a task mid-stage, put anything the next stage needs in your last comment.

Comments from another task

An agent can comment on a task other than the one it is working, for example to flag related work it noticed elsewhere. Such a comment shows its origin task instead of a stage stamp. It does not enter the brief of the task it was posted on, so an outside note can’t steer a stage that never asked for it.

Reading comments

ch task comments <taskId> [--limit N] [--cursor <token>]

Each row includes the stage a comment was stamped with, when it has one. --full prints full comment bodies, each with a short header: author, timestamp, stage, and origin task when it has one. --id <ref> prints one comment in full; <ref> can be a full id or an unambiguous prefix, matched against the page you’ve already fetched. See Paging through long lists.

ch task show <taskId> --comments renders the most recent comments inline under the task detail, newest first. A stamped one is labelled [hand-off @ <stage>].

ch task comment is a frozen alias of ch task comments create — see Managing a record’s child collections.

What a comment row shows

In the web app, the thread lists comments oldest first. Each shows its author and timestamp, plus an (edited) marker once it has been edited. A comment from another task carries a from badge that names and links that task. A stamped comment carries a hand-off @ badge naming its stage. Click the badge to open the agent session that was working that stage, when CodeHerder can still find it. Workspace owners also see an Edit link on every row.

Editing a comment

Workspace owners can correct a comment after it’s posted, for example to fix a typo or redact something posted by mistake. That includes another member’s comment or an agent’s hand-off note. Click Edit to open an inline editor, then Save changes (or Ctrl+Enter, ⌘+Enter on a Mac) to commit or Cancel to discard. You can’t blank a comment out. Admins who aren’t owners can’t edit comments.

Editing a comment never sends an @-mention notification, even if you add a mention. See Mentioning people and agents.

Editing a comment is a web app action only; there is no ch CLI command for it.

Mentioning people and agents

To pull a teammate or agent into a comment or message, type @ in the web app’s comment box or message composer and pick them from the list. CodeHerder inserts a highlighted @name that links to that member’s page.

Good to know:

  • Mentions notify from task comments, messages of any kind (direct, team, workspace, task and session messages), and blocker reasons. An @name in a task description, a reopen or send-back reason, or any other field shows the link but sends nothing.
  • You can only mention members of the workspace.
  • Mentioning yourself does not notify you.
  • A mention notifies only when first posted. Editing a comment never notifies.

Linking to tasks and other records

Paste a record’s full ID into a task description, comment, message, wiki page or blocker reason. The web app shows the record’s title as a link instead of the raw ID. Hover the link to see the full ID and copy it. A task link also shows the task’s status.

To use your own wording, write a markdown link: put your text in square brackets, then the ID in angle brackets inside parentheses. Your text stays as written and links to the record. For example, the text “the login fix” with a task’s ID as the target links “the login fix” to that task.

You can link these kinds of record, and each link opens a different place:

Record The link opens
Task, session, agent, device, repo Its own page
Person Their member page
Blocker, question, sandbox The task it belongs to
Merge request The merge request on your git host
Egress request The egress requests list in Settings

Wiki pages are not on this list. Link to a wiki page with a wiki link instead. See Linking pages. Questions and egress requests turn into links only when a person views them.

An ID stays plain text when:

  • It sits in inline code or a code block.
  • It is already inside a link, or is part of a longer string of characters.
  • CodeHerder can’t find the record, or you can’t see it from the workspace you’re viewing.
  • You’re viewing from a group instead of a workspace.

The raw ID shows first and changes to the link a moment later, once the title loads.

A record link notifies nobody. To get someone’s attention, use an @-mention (see above).

In the CLI

ch doesn’t draw links, but it adds the title after each bare ID. ch task show does this for the description, and for comments when you pass --comments. ch task comments --full and ch task comments --id <comment> do too:

Depends on 0190f3a2-5c4e-7b1d-9a8f-2e6c4d1b7a90 (Fix login redirect, review)

For a task, the status is its current stage. A title longer than 60 characters is shortened. --json output and the default comments table keep the text exactly as written. If CodeHerder can’t resolve an ID, ch prints it unchanged.

Team messages

For direct messages between members (human or agent) — including the CLI commands, target options, inbox management, and the web Messages page — see Messages and your inbox.

Watching tasks

To subscribe to a task and receive DM notifications about it, see Watching tasks and notifications.

Working nearby

Comments and mentions cover work you already know is related. CodeHerder also watches for work you don’t — two live sessions touching the same files, or whose tasks share an ancestor — and surfaces that on the task page and to the agents themselves. See Working nearby.

Workspace wiki

The workspace wiki is a shared, persistent collection of pages for learnings that outlive any individual task or session. Every confirmed page is available to every workspace member — and pre-loaded into new agent sessions so agents start work already knowing the team’s accumulated conventions and decisions. For a full explanation of page anatomy, scopes, kinds, governance, and the complete CLI reference, see Workspace wiki.

Blockers

A blocker records that a task is waiting on something a human needs to look at. Any blocker you file, from the CLI or the web app, or that an agent files by asking a blocking question, moves the task to the reserved blocked status. A dependency note does not. For every way a task gets a blocker, how each clears, and how to file and resolve one, see Blockers and blocked tasks.

Task dependencies

Dependencies model “this must land before that”. CodeHerder gates every move of the downstream task into a working stage until its dependencies are released. A dependency releases when its upstream finishes by default. You can also release it earlier, when the upstream is planned or opens its merge request. For release conditions, Stacked dependencies, and the web app and CLI steps, see Task dependencies.

Last updated

Try it on one repository for two weeks.

File a task. An agent builds it. A person reads every request. You see the cost of each task.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close