CodeHerderSearch⌘KRequest access →

My work

Your personal queue: decisions that wait on you, work you filed or watch, approvals, connected apps, CLI sign-ins.

My work is your personal queue. It is an account page, not a workspace page. Open it from My work in the Home sidebar, or from Open My work in the Needs you panel on Home. A workspace sidebar has no My work item. To get back to Home from a workspace, select the logo in the top bar or the Home breadcrumb. My work shows what waits on you and how your own work is going, across every workspace you belong to.

My work has these sections, in this order: Needs you, In flight, Done this week, Awaiting your approval, Connected apps and Your CLI sign-ins. Needs you, In flight and Awaiting your approval span every workspace you can reach. Connected apps and Your CLI sign-ins are account-level: they list what is connected to you, not to any one workspace. My work differs from two other workspace views:

  • The Dashboard shows a whole-workspace pulse: live sessions, stalled tasks, workspace-wide activity, and cost and throughput charts. Use it for an at-a-glance summary of everything happening across the team.
  • The Tasks view is the complete workspace task list — every task, regardless of who created or owns it. Use it for browsing, filtering, and triaging work across the team.

Needs you

The Needs you section lists the decisions you can make on your own work, across your workspaces. Your own work is the tasks you filed, the tasks under them, and the tasks you watch. A decision on any other task does not appear here. Each row names the task, the workspace, what is asked, and how long it has waited. These are the kinds of item you can see:

  • A question an agent asked you.
  • A human ask: a blocker that tells you what happened and offers one to four option buttons. See Blockers that ask you to choose. An agent writes the ask when it files a blocker. CodeHerder writes one for some of its own parks.
  • An advance that needs your approval.
  • A network access request.
  • A change to managed settings that needs a decision.

A blocker with no ask is not in this list. It stays on the task page and the Blockers page.

Select Act on a row to act in place. You can answer a question, pick an option on a human ask, approve or reject an advance, decide a network access request, or decide a settings change. A row you act on stays in the list for a moment and shows what happens next.

Select View on a row to open the full decision beside the list. On a phone, the decision fills the page.

With single-key shortcuts turned on, you can work through the list from the keyboard:

Key What it does
j / k Move to the next or previous row
Enter Open the decision for the selected row
1–9 Pick that answer option on a question
e Open the task

To turn these shortcuts on or off, see Keyboard shortcuts.

If you are an admin, a Show team checkbox appears. It widens the list from your own work to every open task in the workspaces you administer. The list still shows only the decisions you can make. CodeHerder remembers your choice in this browser. Other members don’t see the checkbox.

You can also act on these items from the terminal. The ch console lists them in its Needs you sidebar.

For the full blocker lifecycle — every way a task gets a blocker, which ones clear themselves, and how to file and resolve one from the CLI — see Blockers and blocked tasks. For the question route specifically, see When an agent needs your input. For the three answers to a network access request, see Network access approvals.

In flight

The In flight section lists work you filed or watch, and shows who must act on it next. It shows one row for each top-level task and the tasks under it, across your workspaces. Each row has a bar that splits its tasks by who acts next: done, agent, system, someone else, or you. A legend above the list explains the colors. The row also shows the most urgent wait. Expand a row to see the tasks under it, and open any of them from there. For what each answer means and what to do about it, see Who acts next.

Watched tasks show here too. To subscribe, unsubscribe, or change which events send you a direct message, see Watching tasks and notifications.

From the CLI, these two commands list tasks like the ones in this section. --watching spans every workspace. --created-by me lists only the current workspace. Add --all to include finished tasks:

ch task list --created-by me --all   # everything you've filed, at any stage
ch task list --watching --all        # every task you're watching, finished ones included

Done this week

The Done this week section lists work that finished in the last 7 days. It starts collapsed. Select Show finished work to load it. Work you filed or watch stays here for 7 days after it finishes. Older work is no longer listed here.

Awaiting your approval

When a task’s workflow has an approval gate, CodeHerder’s own automatic advance is what files a pending-advance request — not a command a person or agent runs. The Awaiting your approval section lists every pending request where you are an eligible approver, in every workspace you can reach. Each row opens the task in its own workspace. A row shows the task title, the stage the task would move to, who requested it, and when.

Click the task row to open the task detail page, then use the Approve or Reject buttons in the pending-advance banner. For the full approval workflow, including CLI commands to approve or reject, see Approvals and staying in control.

Connected apps

The Connected apps section lists every third-party client you’ve approved to act on your CodeHerder account through the Model Context Protocol (MCP) — for example, a claude.ai or ChatGPT app you’ve connected. It shows the app’s name, its access (Read only or Read and write), and when you connected it. If you haven’t connected anything yet, this section is empty; approving an app from claude.ai or chatgpt.com lists it here the moment you approve it.

Open the More menu on an app’s row and choose Revoke, then confirm, to cut off its access. That client can no longer act on your behalf — if you (or whoever set it up) want to reconnect it later, you’ll need to approve it again from claude.ai or chatgpt.com. This section is account-level: it shows every connected app across your whole account, not just the current workspace.

Your CLI sign-ins

The Your CLI sign-ins section lists every CLI sign-in and API key currently signed into your account. A row comes from one of two sources, shown in the Source column:

  • CLI sign-in — a machine where you’ve signed in with ch login. It shows the machine’s hostname, its operating system, and when the CLI last made a call from it. A machine that’s never made a call yet shows no “last used” value.
  • API key — a plain API key, for example one you minted yourself with ch member keys create. It shows the key’s label (its --name, blank if the key has none) and its last-used time. Its OS cell is always empty, which is the quickest way to tell a key row from a machine.

A key that matches a ch login installation’s current credential is not listed twice. If you haven’t signed in from anywhere and hold no API key, this section is empty. Signing in with ch login, or minting an API key, lists it here.

Open the More menu on a row and choose Revoke, then confirm, to cut off its access. Revocation and recovery differ by source:

  • A CLI sign-in row revokes the installation and the key it holds. Run ch login again from that machine to sign back in — the row reappears.
  • An API key row revokes the key itself, permanently. Its plaintext was shown once, at mint time, and a revoked key never comes back by signing in again. To keep working, sign in again with ch login. If you are an admin or owner, you can instead mint a fresh key with ch member keys create — see Minting API keys.

Use Revoke if you lose a laptop, retire a machine, or don’t recognize an entry. Like Connected apps, this section is account-level, not scoped to a workspace. ch logout only handles the machine you’re currently on — see Credentials and profiles — revoking a different machine or key is done here, in the web app.

Network access requests

My work does not list network access requests. Each workspace lists them in the Network access approvals panel on its Dashboard. A request also appears in Needs you when you are an admin of its workspace and the task is your own work, or when Show team is on. Only a workspace admin or owner can decide a request. For the three answers and what each one does, see Network access approvals.

The sidebar badge

The My work link in the Home sidebar shows a count badge for the items in Needs you: the decisions you can make on your own work, across your workspaces. The badge shows the number, and its label reads, for example, “3 items need you”. The badge is hidden at zero, and shows 99+ once the count passes 99.

From the CLI, these sections have an equivalent command:

ch egress list --status pending     # pending network access requests in the current workspace
ch task list --awaiting-approval     # pending advances awaiting your approval
ch task list --watching --all        # every task you're watching, finished ones included
ch task list --created-by me --all   # everything you've filed, at any stage

For approvals and gate configuration, see Approvals and staying in control. For responding to an agent that needs your input, see When an agent needs your input. For subscribing to tasks and managing notifications, see Watching tasks and notifications. For network access requests, see Network access approvals. For the full task list and filter options, see Finding and tracking your work. For what a connected app can do and what ch login sets up, see What Claude and ChatGPT can do with CodeHerder, Connect CodeHerder to claude.ai or ChatGPT, and Credentials and profiles. To link your Slack account, open Profile from the user menu. See Posting task events to Slack.

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