Xorin documentation

Chat, context, and project memory

The chat composer controls both what Xorin is allowed to do and which project information is emphasized for a request.

Choose an interaction mode

Mode	Use it for	Behavior
Ask	Explanations and guidance	Read-only inspection tools are available when project context is needed. Project mutations are blocked.
Plan	Large or sensitive changes	Xorin proposes steps first. You can disable, edit, or reorder steps, add instructions, answer questions, then approve or cancel.
Agent	Direct execution	Xorin can inspect the project and run tools immediately. This is the default mode.

Automatic project context

Each request includes a compact snapshot of the active scene, current selection, scene statistics, recent console errors, render pipeline, scripting backend, tags, and layers. It is useful orientation, not a complete dump of your project.

Use @mentions for precise context

Type @ and at least two characters to search. Mention chips can refer to:

Project files and assets, including scripts and prefabs.
GameObjects from the current scene scope.
@selection for selected objects.
@console for recent logs and errors.
@scene for the current scene hierarchy.

Good practice

Mention the smallest set of relevant files or objects. More context is not always better, and it consumes model context.

Attach visual context

Select the paperclip attachment button beside Send to upload an image or capture the current Scene View, Game View, or a four-angle Scene View composite. Xorin can also request Scene or Game View captures while diagnosing a task.

Attachments are visual evidence. They do not replace checking the hierarchy, Inspector, console, or runtime state.

Project memory

Open Memory from the Xorin header or choose Xorin → Memory to save instructions that should accompany every request in the current project. Rules are stored in .xorin/rules.md. Good rules describe conventions such as namespaces, folder layout, input system, target platform, or art direction.

The Memory panel shows a word counter and allows up to approximately 1,600 words.

Keep rules short and stable. Task-specific instructions belong in the request rather than project memory.

Chat history and context usage

Chats persist locally and can be reopened, renamed, or deleted.
History, Memory, and Settings open in integrated side panels from the Xorin header.
Responses render Markdown, including tables, lists, and code blocks with Copy controls.
Tool rows show the current action, completion state, and elapsed time.
The context ring reports the most recent model call's estimated context usage and changes color as the conversation approaches its limit.

Select the context ring to see free space and usage attributed to conversation messages, the system prompt, project memory, tool definitions, provider or format overhead, and cache activity.

Context indicator limitation

The ring is informational and does not provide full-chat summarization. Xorin may compact older ephemeral tool results and remove old screenshot data internally, but long-lived conversation messages still consume context. Start a new chat or reduce attached context when a conversation becomes too large.