Mentions and context
Mention a steering record in a work item and see what the agent receives when you send it.
A mention points a work item at a steering record. The agent that gets the work reads those records with the brief.
Mention a record
Type @ in the description and search. A save accepts a mention only for a record that is active and in the item's own workspace. A mention for any other record stays plain text.
The send checks more. A record that is retired, superseded, past its valid_until, or limited to another repository is left out of the send, and the dialog says why. An item holds up to 50 mentions.
A mention is a row on the item. It does not live only in the text. If someone edits the mention out of the text in GitHub, the record still shows in the list under the description.
Agent context
Nothing is pinned until you send. The send dialog lists the records that would go, at the version each has now. It names each record it leaves out and why: for example deleted, retired, superseded, expired, or limited to another repository.
When you choose Send, the dialog's request carries the versions you saw. Oxagen checks them again inside the send. If a record changed or became ineligible meanwhile, nothing is sent. The dialog shows the current list, and you confirm again.
On a match, Oxagen pins each record at that version. A later edit of the record does not change what a sent run was told, and a retried claim builds the same prompt.
The agent's first prompt then holds a block that starts with "Context records the person chose for this work:". It sits after the item's own section and before the issue text. Each entry shows the record's name, kind, version, and published body. The block also names any mentioned record that was not sent. The run's steering manifest lists each record as included with the reason mentioned.
- Records are never cut for budget. You chose them, so they always go. A send is refused instead when the records hold more than 64 KiB, and the refusal names the largest records.
- Memory and fact records sit inside a quoted-data fence. Their text may have been written by an agent or a tracker, so the agent reads it as data.
- A batch pins once. A batch send prints each version once across the batch, and the 64 KiB limit counts the whole batch.
The title and description of a collected item are outside text. Oxagen shows them as data and the agent never follows them as instructions.
Attachments
The agent does not receive a work item's attachments, and its prompt does not list them. A later decision will say how a run reads a file.