What Claude and ChatGPT can do with CodeHerder

A connector is a live link from claude.ai or chatgpt.com to CodeHerder, using your own account and your own permissions — connecting one never gives Claude or ChatGPT any access you don’t already have. If you can’t see a workspace, a task, or a page in the workspace wiki in the CodeHerder app, the connector can’t see it either.

This page describes what each capability actually does. For the click-by-click steps to add the connector itself, see Connect CodeHerder to claude.ai or ChatGPT.

What it can do

Read

See your workspaces. Lists every CodeHerder workspace you’re a member of, or checks whether you have access to one specific workspace.

Say something like: “What CodeHerder workspaces do I have access to?”

List tasks. Shows tasks in a workspace, including its sub-workspaces. By default this only shows open work (not-yet-started and in-progress tasks) — ask for completed tasks explicitly if you want those too.

Say something like: “What are my open tasks in the Marketing workspace?” or “Show me the tasks that are done.”

Read one task in full. Pulls up everything about a single task: its title, description, status, priority, and — once an agent has run automated checks against it — the results of those checks.

Say something like: “Give me the full details on task abc-123.”

Read a task’s comments. Shows the discussion thread on a task, newest first.

Say something like: “What’s the latest discussion on that task?”

Read recent activity. Shows a feed of what’s happened recently — your own activity, everything in a workspace, or everything on one specific task.

Say something like: “What’s happened on this task recently?” or “What have I been up to in CodeHerder today?”

Read the team’s workspace wiki. Your team can save durable notes, conventions, and context in CodeHerder’s workspace wiki so agents and teammates don’t have to relearn the same things. Claude/ChatGPT can list what’s there and read one page in full. You’ll only ever see wiki pages shared with the whole team — not another teammate’s private notes.

Say something like: “What does our team’s CodeHerder wiki say about deploy conventions?”

Search everything you can see. Runs the same global search the CodeHerder app’s own search box does — across workspaces, tasks, the workspace wiki, messages, task comments, and the built-in help docs — and comes back with matches grouped by what kind of thing they are. Only ever searches what you already have access to.

Say something like: “Search CodeHerder for anything about the login bug.”

Read the CodeHerder guides. Lists or reads the built-in support/help docs — the same ones you’d find in the CodeHerder app’s own help section — so Claude/ChatGPT can answer “how do I…” questions about CodeHerder itself using the real, current docs instead of guessing.

Say something like: “What does the CodeHerder guide say about connecting a device?”

Write

Create a task. Creates a new task in a workspace, following that workspace’s own task rules (what types it allows, what priorities are valid, and so on). You can also set its type, priority, a parent task to file it under, field values such as acceptance criteria, and other tasks it depends on, all in the same request. Asking for the exact same task twice in a short window — for instance, if a request seems to hang and you ask again — creates it once, not twice, so it’s safe to retry.

Say something like: “Create a high-priority bug in the Backend workspace called ‘Fix the flaky login test’, with acceptance criteria: the test passes ten runs in a row in CI.”

Comment on a task. Posts a comment on an existing task — the same as posting one in the app. Anyone mentioned in the comment gets notified, people watching the task get notified, and if an agent is actively working on that task, it gets woken up to see the new comment.

Say something like: “Add a comment to task abc-123 saying the fix is ready for review.”

Link one task to another. Makes an existing task depend on another existing task, the same as adding a dependency in the app — the depending task isn’t ready to start until the one it depends on is done. Asking to link two tasks that are already linked doesn’t create a duplicate. Linking a task to itself, or in a way that would create a loop, is refused, and so is a task you don’t have access to.

Say something like: “Make task abc-123 depend on task def-456.”

What it cannot do

The connector is deliberately limited to reading and to the three actions above. It cannot:

• Start, stop, or otherwise drive an agent session or sandbox
• Change a task’s status or move it through its workflow
• Edit a workspace’s workflows
• See another person’s or agent’s private wiki page
• See any workspace you are not a member of

Read-only vs read-and-write access

When you connect, CodeHerder shows you an Allow access to your account? screen that lists exactly what the connector will be able to do — see What sign-in looks like for what that screen shows. A normal claude.ai or chatgpt.com connection asks for both read and write, so approving it gives you all three write actions above right away, with no extra prompt.

If that screen lists read access only, every write action — creating a task, commenting, and linking a dependency — is refused. That happens when whoever set up the connector, typically a workspace admin doing an advanced or self-hosted setup, limited it to read-only ahead of time; it isn’t something a normal claude.ai/chatgpt.com connection does on its own. If you hit that, reconnecting won’t change anything — ask whoever set up the connector to switch it to read-and-write instead.

Limits you may notice

• Long lists come back a page at a time. If a workspace has a lot of tasks or a task has a lot of comments, you’ll get the first batch — just ask for the next page (e.g. “show me more”) and Claude/ChatGPT will fetch it.
• The team wiki has a cap here. When Claude/ChatGPT lists wiki pages through the connector, only a bounded number are recalled at once; if your team has saved a lot, you may be told the list was cut off. (This cap is specific to the connector — the ch CLI’s own page listing has no such limit.)
• A burst of requests can be rate-limited briefly. If you (or an automation) fire off a lot of CodeHerder requests in a short window, you may see a brief “too many requests” message — it clears on its own within a minute.

If something goes wrong

• You’re asked to sign in every time, instead of staying connected. Your connector’s credential likely expired — reconnecting refreshes it.
• You get “not found” for a task or workspace you can clearly see in the CodeHerder app. You’re probably signed into a different CodeHerder account, or the item belongs to a workspace you’re not a member of under that account. Check which account the connector is signed in as.
• A create-task, comment, or link request is refused. This connector’s credential was set up as read-only (see “Read-only vs read-and-write access” above) — that’s not something a normal claude.ai/chatgpt.com connection does on its own, so ask whoever set up the connector to switch it to read-and-write.
• Tools stop being offered partway through a ChatGPT conversation, even though the connector is still listed as connected. This is a known ChatGPT-side issue, not a CodeHerder problem — start a new chat and it should work again.

For the click-path to add or remove the connector itself, see Connect CodeHerder to claude.ai or ChatGPT. To see every connector you’ve approved and revoke one, see My work.