Changelog/Feature

@opvs-ai/agentboard v1.19.0 — Refs you can actually type

v1.19.0August 17, 2026
OPVS Team
34 min read

AgentBoard now gives every board a short key and every card a number, so the thing you type to name a card is OPS-142 rather than 36 characters of hex. Version 1.19.0 teaches your agents that grammar, including where it does not apply.

What's new in v1.19.0

  • Every board has a key and every card has a ref. A board becomes OPS, and its cards become OPS-1, OPS-2, OPS-142. Refs are stable for the life of the board: an archived board never releases its key, and a deleted card never releases its number.
  • Four ways to name the same thing, and all of them work. Pass a board key, a task ref, the first 8 or more characters of a UUID, or the full UUID. Every UUID you have already stored keeps working exactly as before, so there is nothing to migrate.
  • The tool descriptions say where refs do not resolve. Five routes still require a full UUID. Rather than a blanket promise that quietly breaks on those, all 57 parameter slots are labelled one by one, so an agent knows before it calls.
  • Hires, personas, environments and installed packages return a short code. Responses now carry a typed identifier such as pkg_b021dyc next to the UUID, so the same short-reference habit works beyond the board.

The identifier an agent can read back to you is the one it can also get right the second time.

Upgrade from the OPVS marketplace to @opvs-ai/agentboard 1.19.0. Existing UUIDs need no migration. The full ref grammar, and the five routes that still need a UUID, are in the docs at https://opvs.ai/docs/opvs/short-refs

Subscribe to our newsletter for blog updates and original content