Code work and pull requests

Minddy tracks the work; your own coding agent, such as Claude Code, Codex or Cursor, changes the code. Copy a prompt from the issue, let the agent read and update the issue through minddy MCP, then review the linked pull request in Minddy before merging. Numo does not write code, open branches or run tests.

Hand an issue to an external coding agent

Connect your agent to minddy MCP first so it can read the plan and update its tasks; see Connect an external assistant to minddy MCP. The agent runs on your computer or in its own service, with its own subscription or API costs. Minddy does not supply it with repository access.

1. Open the issue and describe the expected behavior, constraints and acceptance checks. Write or review the plan in its Plan tab when the work has several steps.
2. Open the issue's actions menu and choose Copy as prompt. Choose Generate a plan (or Review the plan when one exists) to scope the work without coding, Implement the issue to start the change, Verify the implementation to have the agent review finished work against the plan and comments, or Custom… to write your own instruction.
3. Paste the prompt into your agent in the repository's working copy. Copying runs no AI model and uses no AI allowance.
4. Follow the plan progress in the issue as the agent updates its tasks through MCP. Answer its questions in the agent, or add decisions to the issue so the next prompt carries them.

The prompt contents, branch suggestion and language rules are described in Copy a prompt for another coding agent.

Keep the work linked to the issue

When the repository is linked to the project, keep the issue identifier in the branch name, the pull request title or a Fixes MIN-42 line. Minddy then attaches the pull request to the issue, and later prompts tell the agent to continue the open pull request on its branch. To attach an issue by hand, use Link an issue on the pull request. Its search accepts an identifier or title words, and a description also lists issues of the project found by meaning under Related by meaning.

From a board, right-click an issue without an open pull request and choose Link to a pull request to pick one of its project's open pull requests, drafts included. The entry appears only when that project has at least one such pull request to link to. With several issues selected, Actions offers the same choice for the whole selection, and Link the other issues to #N when some of them already have pull request N. Link to a pull request is not offered once a selected issue has any linked pull request; Unlink N issues from their pull requests removes every link of the selection first, after you confirm. Links show on the cards immediately, and a refused link is put back when the board refreshes. A card with an open pull request shows its number, coloured by state, and its merge readiness, the same indicator as on Code review.

In Account settings → Issues → Starting an issue, Start the issue or task when I copy its prompt moves an issue or notebook task that has not started yet into progress when you copy its prompt. Leave it off if you copy prompts only to read them.

Review a linked pull request

Open the pull request linked to an issue, or find it in the pull request list. Repository access is still required; project membership alone does not grant forge permissions.

Read the description and activity, then inspect changed files and diff hunks. Open unresolved conversations and respond in the relevant thread rather than creating an unrelated comment. To hand the remaining feedback back to your agent, open View conversations, then Fix all and Copy prompt. File review marks help track your reading; they are not a provider approval. Check commits, CI results and linked issues to confirm the proposed change covers the requested work.

In a description, a comment or the diff of an image, click an image to open it across the whole window; an image diff opens its Before and After sides separately. Use Close or Escape to return to the pull request.

Mention @numo in a pull request comment to ask Numo for a read-only review in a conversation. It reads the pull request and answers; it does not push commits. A mention written on the forge counts only when its author is linked to the owner or a Member (not a reader) of a project that links the repository, and its usage is charged to that project's owner.

Demonstration PR that remains open and unmerged. Its diff trims the name and uses World for an empty value. This instance cannot request user GitHub authorization; the readiness label does not grant merge permission or prove successful provider CI.

Review and merge

Use Request a review to choose a reviewer when a second review is needed. Check the draft or ready-for-review state, unresolved discussions, requested reviews and provider merge policy.

Merge only after the applicable checks and reviews are satisfied and your provider account has permission. Merge with Numo lets Numo write the merge commit title and description from the pull request, then merges as soon as they are ready. A visible action can still be rejected by the forge. If the displayed state is stale, refresh and inspect the provider before repeating an action. A linked preview depends on a real provider deployment.

Right-click a pull request in the list to change its state, merge it or ask for a fix without opening it. An open pull request offers Convert to draft and Close pull request, a draft offers Ready for review and Close pull request, and a closed one offers Reopen; each change asks for confirmation. A merged pull request offers no state change. Write actions appear only when your provider account can write to the repository, and stay unavailable until the menu has re-read the pull request. Merge appears when the pull request is open, not a draft and ready to merge; it opens the pull request on its usual merge confirmation. Copy fix prompt and Fix with Numo appear when a check fails, a conversation is unresolved, or the branch conflicts or is out of date. Fix with Numo sends that prompt to Numo with the pull request as context. Numo can read the pull request, answer a review conversation that needs no code change and resolve conversations the branch already addresses, but it does not change code or push commits; for the code changes, use Copy fix prompt and paste it into your coding agent. Permissions and mergeability are checked again when you confirm.