Context references
Context references
Context references let you attach a source to a message without pasting it into the composer.
Holaryn resolves the source when you press Send, records exactly which version was used, labels
where it came from, and keeps that information with the conversation.
What you see
An attachment chip states its source, approximate size, and trust label. Removing the chip removes
it from the pending message. Sending announces whether each reference was included, changed,
missing, denied, duplicated, or left out because the context budget was full.
Messages with context have a Context disclosure. Each source row shows:
- the kind and label;
- resolution state and freshness;
- trust and size;
- a safe reason when it could not be used;
- a source link only when Holaryn has a validated location for it.
If an answer contains a citation marker for one of those validated sources, the transcript turns
that marker into a link. Text that merely looks like a citation or contains a made-up URL stays
plain text.
Supported sources
The first release resolves workspace files, folder listings, source symbols, staged attachments,
artifacts, URLs, URL-backed issues, memories, prior chats and runs, canvases, and exact annotation
snapshots queued from the review desk. The shared
reference format also reserves diagnostics, git objects, model/profile, and peer sources for
future resolvers; selecting a kind without a resolver reports it as unavailable.
Workspace sources must remain inside the current code-session workspace. Attachments must belong
to the current chat. A changed file or artifact can be reported as stale instead of quietly using
different content. Holaryn checks those rules again every time the reference is used.
An annotation action resolves the exact saved annotation version and its exact target version.
Review text remains untrusted data and cannot grant authority; the resulting agent turn still uses
normal policy and approvals.
Trust and privacy
Referenced text is data, not an instruction source. Local files, external pages, attachments,
memory, and earlier run output retain provenance and untrusted-data labels through replay and
summarization. Those labels help the approval and security layers decide whether a consequential
action needs review.
External URLs are saved without credentials or query strings. This protects signed tokens and
tracking values, but it also means a URL that requires a query string cannot yet be used as a
durable reference. Paste its safe content as an attachment instead.
The host applies a bounded per-source and total context budget. A source omitted because of the
budget remains listed, so you can remove other references or select a smaller excerpt and retry.