CodeHerderSearch⌘KRequest access →

Connect the tools your team already runs

Four routes bring work into CodeHerder. Two routes send news back out to a tool you run.

4 ways work reaches CodeHerder

Pick the one that fits. The claude.ai or ChatGPT route needs no terminal and no CodeHerder login screen.

  • The web app and the ch CLI

    Your whole team. The web app needs no terminal; ch adds scripting for a developer who wants it.

    Create a task, check its status, or read an update, directly in CodeHerder.

    Read the full doc →
  • The claude.ai or ChatGPT integration

    A product person with an idea. They ask Claude or ChatGPT to file it, with no CodeHerder login screen to learn.

    Reads your tasks. It also reads your activity feed and workspace wiki pages. It writes in exactly two ways: it creates a task and it posts a comment.

    Read the full doc →
  • Slack threads and buttons

    A leader or product person who already works in Slack.

    Answer an agent, approve a task or clear a blocker from the task thread. A reply in the thread becomes a comment.

    Read the full doc →
  • Inbound webhooks

    A team running its own CI pipeline, monitoring tool, or issue tracker.

    An external system sends CodeHerder a signed payload. A rule you write turns it into a comment, a new task, or a merge-outcome report.

    Read the full doc →

2 ways news leaves CodeHerder

Point an outbound webhook at your own endpoint. Or install the HTTP endpoint plugin. Either route carries the event to whatever you run behind it: a chat channel, a paging tool, a dashboard.

  • Outbound webhooks

    A team that wants its own tools to react to CodeHerder activity.

    CodeHerder sends a signed payload to your own endpoint each time a chosen event happens.

    Read the full doc →
  • Plugins

    A team that wants an agent or an event to call an outside service. By default, a person approves each write.

    The HTTP endpoint plugin sends a JSON body to one HTTPS endpoint when an event you choose happens. An agent can also call an approved action as a tool.

    Read the full doc →

4 of 5 providers ready to connect today

A GitHub or GitLab connection checks merge-request status only, and only for a workflow stage built to wait on an outside merge. Opening and landing a merge request stays with the device's own gh or glab. Looking for a coding agent instead of a connection? See works with.

Ready to connect

  • GitHub

    Available

    Read-only: it checks whether a linked merge request is open, merged, or closed. It never opens, merges, or writes to your repository.

    Read the full doc →
  • GitLab

    Available

    Read-only: it checks whether a linked merge request is open, merged, or closed. It never opens, merges, or writes to your repository.

    Read the full doc →
  • Slack

    Available

    Each task gets a card in a channel you choose, with its events in a thread. A person can approve, answer or unblock from Slack.

    Read the full doc →
  • Jira

    Available

    A Jira Cloud issue that enters a status you choose creates one linked task. Comments sync both ways, and a task stage change moves the Jira issue to the status you map.

    Read the full doc →

Coming soon

  • Datadog

    Coming soon

    Datadog is coming soon. It is not available to connect yet.

Bring your tools into the herd.

Connect a provider from Admin → Integrations, or point a webhook at your own endpoint.

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

↑↓ move · ↵ open · esc close