Skip to content

Waiting

KeyTypeDescription
for list of text or text Whose attention the card needs: a handle such as kim, the word human (or operator) for any human, or a list like [kim, bob]. If it is missing or an empty list, any human is meant.
since timestamp When you set the flag, as a timestamp like 2026-09-13T01:29:48Z. A human comment later than this clears the flag; without a readable since the app never clears it.
comment text The bare uuid of the ask comment on this card's own thread, not a path. A human reply to that comment clears the flag.

waiting is a card key that says the card is blocked on a human’s reply. An agent (or anyone writing the card file) sets it in the same pass as the comment that asks the question. Until a human answers, the card face wears a mark and the lane header counts the card, for the person it names.

It is a mapping, and a mapping is the only shape.

A card whose ask is waiting on kim:

title: Choose the sync interval
waiting:
for: kim
since: 2026-09-13T01:29:48Z
comment: 973cda84-5f0a-4c3e-9b1d-2a7e6c4d8f10

comment is the id of the ask on the card’s own thread, for example the comment 973cda84-5f0a-4c3e-9b1d-2a7e6c4d8f10 in the card’s comments folder, which opens with a mention of the person asked:

@kim Should the sync interval be 5 or 15 minutes?

See Comment for the comment file and how @handle mentions work.

Write waiting in the same pass as the ask it points at.

since is when you set it, in the same timestamp form the other stamps use. comment is the comment’s own id, bare, never a path.

for can be written three ways:

  • a single handle, such as for: kim, matched case-insensitively;
  • the word human (or operator), for any human;
  • a list, such as for: [kim, bob], to ask several people.

With a list, every listed handle’s machine draws the mark, counts the card and chimes, and nobody else’s does. A list that contains human or a blank entry, or an empty list, means any human. A missing for also means any human.

Name each person with an @ on the first line of the ask as well, so their option buttons are drawn. The list only widens who is alerted: any person’s answer clears the whole flag.

Only the app clears waiting. On its next load it removes the key when either of these holds:

  • a human’s comment has landed on the card later than since, or
  • a comment replies to the ask (its in-reply-to is the comment id), whatever either timestamp says.

Nothing else on the card changes when it clears. An agent’s reply never clears it. Without a readable since, the app never clears it.

Do not remove the key yourself when the reply arrives: the app already has. If it cleared before the reply you needed, set it again.

While it is set, the card face wears the mark and the lane header counts the card, for the person whose handle it names. A card waiting on somebody else’s handle shows nothing on this machine.

You can also filter by it: see Grouping and filtering for the by: waiting clause.