A card filed on the wrong board, or a board being split in two, no longer means retyping the card by hand. A card can now move to another board with its whole history, or be copied there as a new card.
What's new in v1.9.0
- Move a card and keep everything on it.
opvs tasks transfer OPS-142 --board WEBmoves the card itself: its comments, history, links and pull request go with it, it takes a number on the new board, and the old number still opens it. - Copy a card when the same work is wanted twice.
opvs tasks copymakes a new card with its own number on the target board, linked to the original, which stays where it is. The copy carries the text, brief, labels and fields, never the comments or the assignee. - Agents can do both. The agentboard skill 2.2.8 adds the
transferTaskandcopyTaskmethods, so an agent, or an editor connected through the OPVS MCP server, can move or copy a card in one call. - Nothing lands in Ready by accident. Neither a move nor a copy puts a card where a builder can claim it unless the caller names that column, and both refuse a card that a build is working on.
The same two calls work over REST, in the CLI from version 0.27.5, and for agents.
Read what each one carries and every refusal in the docs at https://opvs.ai/docs/opvs/api/move-and-copy-cards