Preloaded objects put useful project documents, sheets, saved sheet views and connected text files into the agent's conversation history once. Open Chat resources in a project chat and find Preloaded objects in the sidebar.
Add and reuse a source
- Click Add source and choose a readable source linked to the project.
- Choose Chat to include it in this conversation or Agent to include it in this agent's conversations in the project. Persistent-team projects use agent scope.
- Send your message. The agent can use the snapshot directly without another read call.
Hover over or focus the scope label to switch between Chat and Agent. Before a chat exists, add sources at agent scope. Your selections remain preferences until you remove them; the loaded snapshots have a shorter lifecycle.
JEV can preload additional useful objects before the agent starts. Objects already in the current conversation history are not loaded again. The agent can also preload a newly discovered source when it will help across several steps, or release an unneeded automatic preload. It cannot remove your Chat or Agent selections or override a source you excluded.
Snapshot lifecycle
A snapshot stays in history across model calls and nearby runs. It is cleared when the context is compacted or the configured inactivity window expires. This window depends on the model and provider; GPT-6.1 Sol uses 30 minutes by default, while routes with unknown cache lifetimes use a configurable one-hour fallback. Useful sources can then be selected and loaded again. The underlying files and your explicit selection preferences remain.
Snapshots do not refresh automatically after writes or external edits. The agent uses confirmed write inputs and receipts for its changes, and reads again when it needs missing data, external updates or required safe-edit checks. Document drafts remain unpublished until committed.
Standard context allows 5 objects, and max context allows 10. All preloaded snapshots share 10,000 tokens. Large documents and sheets may include only selected passages, columns or rows. Partial coverage is not the whole source; the agent reads additional data when needed.
Remove a source
Use the remove icon. Chat scope removes the selection here; Agent scope removes it from this agent's conversations in the project. Removing an automatic source excludes it from future automatic selections at that scope until you add it again. The source file and completed work remain.
Preloaded objects are inputs; Artifacts are files the agent created or updated. A file can appear in both sections. Appearing under Artifacts does not preload it.
For durable project records, see Shared state and memory. For semantic-search settings, see Agent knowledge.