file-a-task

File a task into no_human

Use the two MCP tools this plugin exposes — task_add and task_status — to hand off work that should become a reviewed pull request, instead of making the change yourself in this conversation.

When to use

• The work is substantial enough to deserve its own branch, its own tests, and independent review — not a one-line edit you can just make inline.
• You want no_human to plan, code, test, have the result reviewed by a second model, and open a pull request, while you keep doing something else.
• Do not use this for small edits you can make directly in the current conversation — that is strictly slower and adds no value.

Prerequisite: the local server must already be running

Both tools call the existing no_human HTTP API at http://127.0.0.1:8420. The bridge does not retry or fall back if that address is unreachable — it refuses to start at all (SystemExit, no auto-retry). Before using either tool, make sure the server is running:

nh start

(The desktop app starts this for you automatically.) If a tool call fails with a connection error, the fix is to start the server, not to retry the call.

Tool: task_add

Creates a new no_human task via POST /api/tasks.

Parameters (all required strings):

Name	Type	Description
title	string	Short task title.
description	string	Full task description — inline the concrete context here (exact file paths, exact acceptance criteria), rather than referencing this conversation, since no_human cannot see it.
repo_path	string	Absolute path to the target repo checkout the task should run against.

You do not pass source — the bridge sets it to "mcp" on every call it makes, server-side, before the request is sent.

Returns: compact JSON with the new task's id and the source the server actually stored (first-class alongside "board"/"jira"), e.g.:

{"task_id":"task-abc123","source":"mcp"}