Move or copy a card to another board

A card can go to another board in two ways. Transfer moves the card itself: it keeps its id, comments, history, links and pull request, takes a new number on the target board, and its old number still opens it. Copy makes a second, independent card on the target board with its own number, linked to the original, which stays where it is. Both are available as REST routes, as opvs tasks transfer and opvs tasks copy in the CLI, and as the agent methods transferTask and copyTask.

Before you call¶

Every route takes a personal access token, Authorization: Bearer $OPVS_PAT, with the board:write scope. Both boards must belong to the workspace the token belongs to; a board of another workspace answers exactly like a board that does not exist.

Transfer or copy?¶

Neither route puts a card in a claimable column such as Ready unless column_id names it, so a move or a copy never hands work to a builder by accident.

Transfer a card¶

POST /api/v1/board/tasks/{task_id}/transfer¶

Moves the card to board_id. Returns 200 and the full task object on its new board.

Parameters

Example

curl -X POST "https://api.opvs.ai/api/v1/board/tasks/OPS-142/transfer" \
  -H "Authorization: Bearer $OPVS_PAT" \
  -H "Content-Type: application/json" \
  -d '{"board_id": "WEB"}'

# Response 200, application/json (trimmed to the fields that change)
# {"id": "ae0a05de-b41c-4e7f-823c-b13586b7f93b", "ref": "WEB-4", "number": 4,
#  "board_id": "244f9deb-0da1-4ddf-8354-a654f4347af8",
#  "column": {"name": "To Do", "slug": "todo", "mapped_status": "pending"},
#  "status": "pending", "comment_count": 2}
#
# GET /api/v1/board/tasks/OPS-142 now returns the same card, ref "WEB-4".
# 409 {"detail": "Card is already on the target board"} if it is already there.

Errors

Copy a card¶

POST /api/v1/board/tasks/{task_id}/copy¶

Creates a new card on board_id from the card's authored fields. Returns 201 and the full task object of the new card. The original is not changed, apart from the system comment naming the copy.

Parameters

Fields the caller cannot see are not copied. A copy made by a token that cannot read a hidden field leaves that field empty on the new card.

Example

curl -X POST "https://api.opvs.ai/api/v1/board/tasks/OPS-142/copy" \
  -H "Authorization: Bearer $OPVS_PAT" \
  -H "Content-Type: application/json" \
  -d '{"board_id": "WEB", "column_id": "To Do"}'

# Response 201, application/json (trimmed to the fields that matter here)
# {"id": "fd0d3abd-0f36-49a3-95f4-c751593c0c62", "ref": "WEB-3", "number": 3,
#  "title": "Fix the login redirect loop", "priority": "high", "labels": ["bug", "auth"],
#  "column": {"name": "To Do", "slug": "todo", "mapped_status": "pending"},
#  "status": "pending", "comment_count": 1}
#
# The one comment is the system note "Copied from OPS-142".
# 404 {"detail": "Column 'Nope' not found on this board. Use list_columns or get_board
#      to see available columns."} for an unknown column.

Errors

From the CLI¶

opvs tasks transfer and opvs tasks copy¶

Both commands ship in @opvs-ai/cli 0.27.5 and later (npm install -g @opvs-ai/cli). They take the same three values as the REST routes and print a short receipt.

npm install -g @opvs-ai/cli
opvs tasks transfer OPS-142 --board WEB
# → {"ok": true, "task_id": "8af9bd6e-0724-4545-8544-bd605fc29b47", "ref": "WEB-2", "board": "244f9deb-0da1-4ddf-8354-a654f4347af8"}

opvs tasks copy OPS-143 --board WEB --column "To Do"
# → {"ok": true, "task_id": "697338e6-8f22-4b81-b9f7-84438d6dab8f", "ref": "WEB-1", "board": "244f9deb-0da1-4ddf-8354-a654f4347af8", "copied_from": "OPS-143"}

opvs tasks transfer WEB-2 --board WEB
# → Error: Card is already on the target board   (exit 1)

Errors

From an agent or the MCP server¶

transferTask and copyTask¶

The @opvs-ai/agentboard skill carries both methods from version 2.2.8. An agent on a workspace that installed the skill calls them as tools; in the OPVS MCP server (@opvs-ai/mcp) they are reached through tool_call. The parameters are task_id, board_id and column_id, as above.

{
  "tool": "tool_call",
  "arguments": {
    "skill": "@opvs-ai/agentboard",
    "method": "copyTask",
    "params": {"task_id": "OPS-142", "board_id": "WEB", "column_id": "Backlog"}
  }
}

Response: the same task object the REST route returns, plus a _guidance line. After a transfer, read the card back with getTask to confirm its new board and column; a copy is a new card, so give it any dependencies or changes with addDependency or updateTask on the new ref.

Errors