Session Reference

Session Reference

Upstream cross-session reference system — not implemented in Edge.

Upstream reference: Session Reference documentation

What Upstream Provides

The Session Reference enables two capabilities:

• File Reference (dsh-file-reference) — cancellable file discovery within an agent's working directory, returning path-only completion candidates filtered by query text. Powers the @file mention syntax in the composer.
• Session Reference (dsh-session-reference) — cross-session context via structured @session mentions. Lists reference candidates ranked by working-directory affinity, prepares immutable aggregated context from multiple referenced sessions, and excludes self-references.

Both services expose Typert Remote methods, so the client accesses them through the ctx.remote.fileReference and ctx.remote.sessionReference namespaces.

Edge Status

Not Implemented

Neither dsh-file-reference nor dsh-session-reference is in Edge's dependencies. No host-side plugins are installed. The client-side Typert remote contributions for these namespaces are mounted by dsh-api-remotes (part of the 33-plugin client bundle), but without a host-side service the Typert gateway returns service-unavailable for any RPC call.

User-visible impact

• @file mentions in the composer do not produce file completion suggestions
• @session mentions do not produce cross-session context references
• The model can still access files via read/write tools; only the composer mention UX is missing

TODO

Evaluate file-reference installation. (#93) FileReferenceService discovers files via the filesystem. Edge has EdgeFileSystem on ctx.fs, so the service's dependency may already be satisfied. If inject requirements are met, installing it could enable @file mentions with zero adapter code — the Typert gateway would auto-route the RPC.

Evaluate session-reference installation. (#93) SessionReferenceResolver reads transcripts from other sessions. This requires ctx.sessions (available) and potentially ctx.sessionPersistence for cold session reads. May need Edge-specific cold-read support similar to the projection cache's cold-snapshot path.