Command reference
oko tasks link
Attaches a genuine operator message to an existing task or registered defect without changing its reading. Use this for a historical question, consent or correction about existing work, rather than inventing a new task from it.
Invocation#
oko tasks link <session> <message-number> <task-or-defect> --by operator|SESSION [--reason TEXT] [--json]Inputs and options#
- The canonical source session and message number; a current task identity, a registered `defect-` end, or the defect's whole UUID. --by names operator or the recording session. --reason explains the association when useful. Example: `oko tasks link <session> <number> task-<identity> --by operator --reason 'This question concerns the existing request'`.
Output and state effect#
- Prepares the message's durable source identity from Transcript Lake when that session is archived, even if a shorter live transcript exists; otherwise it uses the available live or stored source. It writes the explicit work link in the shared register and reads it back. It does not classify the words, create another task, or erase a ruling. Oko Desktop → Rulings → Operator messages and their records offers Attach on each message and rereads its links after the native write.
Refusals and safe exits#
- A missing --by, wrong number or argument count is refused before a database connection. An absent original source, ambiguous legacy timestamp, changed archived body or unreconciled identity refuses by source and message. An unknown task or defect refuses `no current task or registered defect names <id>`; a shortened defect end naming several registered defects names the conflicting IDs and refuses instead of choosing one. A whole defect UUID whose canonical short relation end collides with another registered defect also refuses rather than storing an ambiguous attachment. A database write or missing read-back names the failed operation and target.