# Hand coding tasks to an agent from your board | IonBin

> A coding agent reads a task from ClickUp or a GitHub issue through MCP, makes the change in a branch, and opens a pull request for review.

Canonical page: https://ionbin.com/workflows/agent-picks-up-dev-tasks/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

## Hand coding tasks to an agent from your board

[Build](https://ionbin.com/use-cases/dev-it/)Checked 2026-10-18

Clear small engineering tasks without context-switching your team.

- [01**ClickUp**](https://ionbin.com/workflows/agent-picks-up-dev-tasks/#workflow-step-1)

- [02**Your coding agent**](https://ionbin.com/workflows/agent-picks-up-dev-tasks/#workflow-step-2)

- [03**GitHub**](https://ionbin.com/workflows/agent-picks-up-dev-tasks/#workflow-step-3)

- [04**You**](https://ionbin.com/workflows/agent-picks-up-dev-tasks/#workflow-step-4)

Recipe context

A coding agent reads a task from [ClickUp](https://ionbin.com/tools/clickup/) or a [GitHub](https://ionbin.com/tools/github/) issue through MCP, makes the change in a branch, and opens a pull request for review.

**Independent review.** Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. [Disclosure](https://ionbin.com/disclosure/).

Editorial shortlist

### Compare your options.

**For implementing small tasks from a backlog.**

Confirm acceptance criteria and restrict repository access. Choose one for implementing and reviewing code changes; switching may need setup changes.

**Used by Ion** · separate from rank.

Unpaid picks. No partnership with [OpenAI Codex](https://ionbin.com/tools/openai-codex/), Cursor, [Google Antigravity](https://ionbin.com/tools/google-antigravity/).

- 1 · Primary / high
  #### [OpenAI Codex](https://ionbin.com/tools/openai-codex/)
   Used by Ion
  **Why it fits:** A coding workspace supports edits, tests and reviewable repository changes.
  **Tradeoff:** A development environment and capable reviewer remain necessary.
  Choose it when the result should be a small patch with test evidence.
  Evidence for OpenAI Codex
  The linked [IonBin review](https://ionbin.com/tools/openai-codex/) records capabilities, access limits and source links. Review date: 2026-10-18. [Primary product reference ↗](https://developers.openai.com/codex)

- 2 · Secondary / medium
  #### [Cursor](https://ionbin.com/tools/cursor/)
  **Why it fits:** An AI code editor keeps implementation close to interactive developer review.
  **Tradeoff:** The team must work with code; model availability depends on the plan.
  Prefer it when a developer wants to steer changes while navigating the editor.
  Evidence for Cursor
  The linked [IonBin review](https://ionbin.com/tools/cursor/) records capabilities, access limits and source links. Review date: 2026-10-21. [Primary product reference ↗](https://cursor.com/)

- 3 · Third / lower
  #### [Google Antigravity](https://ionbin.com/tools/google-antigravity/)
  **Why it fits:** Development-agent surfaces offer another route for code and tool-assisted implementation.
  **Tradeoff:** Capabilities differ across desktop, CLI and other surfaces.
  Prefer it when the team already uses its environment and can validate the needed tools.
  Evidence for Google Antigravity
  The linked [IonBin review](https://ionbin.com/tools/google-antigravity/) records capabilities, access limits and source links. Review date: 2026-10-18. [Primary product reference ↗](https://antigravity.google/)

How this shortlist was chosen

Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.

Inspectable file changes come before editor convenience. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.

**Setup and portability:** Use scoped repositories, tests and human review. Switching agents does not migrate settings, credentials or model access.

Reviewed 2026-10-21. This page applies a shared comparison for “implementing and reviewing code changes” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.

See [our review method](https://ionbin.com/editorial-policy/), [MCP connections](https://ionbin.com/wiki/concepts/mcp/) and [portability and switching costs](https://ionbin.com/wiki/questions/how-to-avoid-ai-vendor-lock-in/).

**Connects through:** MCP

### Steps

Follow the handoff

Select a stage or scroll the steps.

- #### [ClickUp](https://ionbin.com/tools/clickup/)
  Holds the task and acceptance criteria
  MCPConfirmed[Source ↗](https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server)

- #### Your coding agent
  Implements the change on a branch
  AI platformConfirmed

- #### [GitHub](https://ionbin.com/tools/github/)
  Hosts the pull request and checks
  [GitHub](https://ionbin.com/tools/github/) hosts a remote MCP server; it can read code and create, update and manage issues and pull requests.
  MCPConfirmed[Source ↗](https://github.com/github/github-mcp-server)

- #### You
  Review and merge
  Human stepConfirmed

Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.

Human approval

Nothing merges without review.

Watch out for

Nothing merges without review. Keep tasks small and the acceptance criteria written down; vague tickets produce confident, wrong pull requests.

### Starter prompt

```
Pick up ClickUp task [ID]. Read the description and acceptance criteria, implement the change on a new branch, run the tests, and open a pull request that explains what changed and why. Do not merge. I will review and merge.
```

Written for this workflow. Paste it into your AI platform and adjust it to your situation.

### Tools in this workflow

| Tool | Role | Official site |
| --- | --- | --- |
| [ClickUp](https://ionbin.com/tools/clickup/) | MCP | [clickup.com ↗](https://clickup.com/) |
| [GitHub](https://ionbin.com/tools/github/) | MCP | [github.com ↗](https://github.com/) |

### Which AI platforms can run it

| Platform | Status | Why |
| --- | --- | --- |
| [Claude (incl. Claude Code)](https://ionbin.com/platforms/claude/) | To verify | [ClickUp](https://ionbin.com/tools/clickup/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; [GitHub](https://ionbin.com/tools/github/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it |
| [OpenAI Codex](https://ionbin.com/platforms/codex/) | To verify | [ClickUp](https://ionbin.com/tools/clickup/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; [GitHub](https://ionbin.com/tools/github/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it |
| [Google Antigravity](https://ionbin.com/platforms/antigravity/) | To verify | [ClickUp](https://ionbin.com/tools/clickup/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; [GitHub](https://ionbin.com/tools/github/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it |
| [ChatGPT](https://ionbin.com/tools/chatgpt/) | To verify | [ClickUp](https://ionbin.com/tools/clickup/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; [GitHub](https://ionbin.com/tools/github/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it |
| Gemini | To verify | [ClickUp](https://ionbin.com/tools/clickup/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; [GitHub](https://ionbin.com/tools/github/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it |
| [Perplexity](https://ionbin.com/tools/perplexity/) | To verify | [ClickUp](https://ionbin.com/tools/clickup/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; [GitHub](https://ionbin.com/tools/github/): MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it |

What the platform statuses mean

**Confirmed:** documented access meets the recorded requirements. **Inferred:** a reviewed note describes a plausible, untested pairing. **To verify:** a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.

### What we checked

[ClickUp](https://ionbin.com/tools/clickup/)’s MCP server works on all plans and lets an agent read tasks with their assignees, priorities and due dates. [GitHub](https://ionbin.com/tools/github/) runs a remote MCP server, alongside a local version, that lets an AI tool read repositories and code and create, update and manage issues and pull requests. [ClickUp](https://ionbin.com/tools/clickup/)’s [GitHub](https://ionbin.com/tools/github/) integration is on every [ClickUp](https://ionbin.com/tools/clickup/) plan. When a valid [ClickUp](https://ionbin.com/tools/clickup/) task ID, written with an accepted prefix (for example #1abc2de or CU-1abc2de), appears in a branch name, commit message or pull request, [ClickUp](https://ionbin.com/tools/clickup/) links that activity to the task and posts a link to the task in the pull request. Workspace owners/admins attach the repository and link it to the relevant [ClickUp](https://ionbin.com/tools/clickup/) Space. Guests and limited members cannot use this integration. This workflow calls for a person to review and merge. Enforce required reviews in repository settings if that boundary must be technical rather than an instruction.

### Set it up

- Have the appropriate admins connect the repository to the Workspace and relevant Space. Review whether Workspace Connected Search should expose repository content.

- Connect [ClickUp](https://ionbin.com/tools/clickup/) MCP and [GitHub](https://ionbin.com/tools/github/) MCP in your coding agent.

- Ask the agent to read the task, create a branch using [ClickUp](https://ionbin.com/tools/clickup/)’s suggested ID format (such as CU-1abc2de),, make the change and run the tests.

- Have it open a pull request with the task ID in the title so [ClickUp](https://ionbin.com/tools/clickup/) links it.

- Review, request changes if needed, and merge yourself.

### Verification limits and implementation checks

The page is documentation-reviewed; the complete workflow has not been run by IonBin.

- Test the task-to-PR link and repository review rules; no coding outcome is guaranteed.

### Sources

- [Connect an AI assistant to ClickUp’s MCP server](https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server) · [ClickUp](https://ionbin.com/tools/clickup/) · official · accessed 2026-10-18

- [GitHub MCP server](https://github.com/github/github-mcp-server) · [GitHub](https://ionbin.com/tools/github/) · official · accessed 2026-10-18

- [GitHub integration](https://help.clickup.com/hc/en-us/articles/6305771568791-GitHub-integration) · [ClickUp](https://ionbin.com/tools/clickup/) · official · accessed 2026-10-18

No affiliate links on this page. No paid placements in workflows. [How IonBin makes money](https://ionbin.com/disclosure/).
