Conversation context
Recent messages from the conversation you continue can accompany your new message. The selection is bounded, so the model may not receive every earlier detail.
GALACTRE / CONVERSATION CONTEXT
Pick up a conversation with relevant recent messages, revisit saved work and understand what the next reply can draw on. Clear boundaries help you keep the discussion useful.
01 / THREE DIFFERENT IDEAS
A conversation can contain more material than the next request includes. Knowing the difference helps you decide what to restate and what to preserve yourself.
Recent messages from the conversation you continue can accompany your new message. The selection is bounded, so the model may not receive every earlier detail.
Completed exchanges can be saved and listed for the current guest or account identity. A message may remain in saved history after it falls outside the context sent with a later request.
Galactre does not create an automatic profile across your chats. Signed-in users can explicitly connect private text sources to one conversation through Workspace > Knowledge.
02 / SEE THE BOUNDARY
Move the slider to explore a count-only illustration. Every tile is a synthetic prior message. The most recent 510 may fit by count; actual selection can be smaller because of byte limits.
20 recent messages within the count limit. 6 older messages outside it.
Illustration only. No conversation is read, sent or modified. Excluded tiles do not mean saved messages were deleted. This is not a token counter or a guarantee that all highlighted messages fit.
User and assistant entries both count. A normal exchange adds two messages.
An oversized history message can stop selection of that message and older messages.
Includes product instructions, your new input and the selected history. Bytes are not tokens.
Model context and output specifications are separate. See published model limits
03 / FOLLOW A MESSAGE
Context is assembled for a request. Saved history is updated after a completed response, when storage succeeds.
Read the request contractThe request identifies a model family and may include a conversation ID. A new chat has no earlier conversation messages to include. Your current identity is checked server-side.
For a continued conversation, recent saved user and assistant messages are selected from that conversation. Older material may be excluded by message count or byte limits.
The current message, permitted recent context and product instructions travel through the governed model path. This does not give the model access to other conversations, files or browser tabs.
The user message and completed answer are stored together, encrypted at rest. If saving fails, the response can report history as unavailable; do not assume the exchange will appear after reloading.
04 / KNOW WHICH HISTORY YOU ARE USING
Guest and account histories are separate. Switching access mode does not merge them or move one conversation into the other.
05 / KEEP THE CONVERSATION USEFUL
Use chat history to choose the conversation you want to continue. Preserve important decisions in a brief you can inspect, rather than relying on every old message being included.
A new conversation has no previous conversation ID. It does not include a different chat as context and does not delete any existing saved history.
Open the chat history and use the delete action for that conversation. After confirmation, its saved messages and conversation record are removed from the active conversation store.
Conversation deletion does not erase separate payment, security or operational audit records. Backup retention and approved service-provider processing require their own policies.
Keep passwords, API keys and information you are not authorized to share out of messages. Encryption at rest does not prevent approved service providers from processing the context needed for a reply.
A BETTER HANDOFF
When a conversation grows, provide a concise source-of-truth brief. Verify the facts before sending it. This example is editable text, not an automatic summarization or memory feature.
Prepare a context brief in chatContinue our discussion using this brief as the current source of truth.
Goal: [what we are trying to achieve]
Confirmed decisions: [verified decisions only]
Constraints: [runtime, scope, limits]
Open questions: [unresolved details]
Next task: [the specific result needed now]
If an earlier detail is missing from this brief or the available conversation context, ask me instead of inventing it.06 / FOR DEVELOPERS
Conversation access follows the current identity, tenant and workload. A conversation ID is not permission. Do not store service credentials in the browser or assume a guest ID can access account history.
/api/v1/chat/conversationsReturns the recent list for the current identity. The list is bounded to 30 conversations.
/api/v1/chat/conversations/{id}Reads an owned conversation. The current response is bounded to 100 saved messages.
/api/v1/chat/generateInclude conversation_id to continue; omit it for a new conversation. Send a current CSRF token.
/api/v1/chat/conversations/{id}/deleteDeletes the owned conversation and its saved messages. Requires a valid session and CSRF protection.
Read limits are separate from the context assembly limit. Handle not-found and temporarily-unavailable responses explicitly.
// Same-origin browser. Use a current session for each mutation.
const session = await fetch('/api/v1/chat/session', {
credentials: 'same-origin'
}).then(r => r.json());
if (!session.chat_available || !session.csrf_token) {
throw new Error('Chat is temporarily unavailable.');
}
// Recent conversations for the current identity only.
const historyResponse = await fetch('/api/v1/chat/conversations', {
credentials: 'same-origin'
});
if (!historyResponse.ok) throw new Error('History unavailable.');
const { conversations } = await historyResponse.json();
// To continue a conversation, use its owned ID in a generation request:
// { family: 'Lunar', message: '...', conversation_id: conversations[0].id }
// Omit conversation_id to start a new conversation.
// Send X-CSRF-Token from the session on every mutation.
// Review the generation contract before sending a request.07 / QUESTIONS, ANSWERED
Saved assistant messages retain the GT release that answered them. Restoring history does not rewrite earlier model identities. Your next message uses the model currently selected in chat; choose an exact version if you want to keep that release for subsequent requests.
No. Saved history and the context included in a new request are different. The current implementation selects a bounded recent portion of the conversation you continue. Older facts may need to be restated, even when earlier messages remain in saved history.
No cross-conversation retrieval is implemented. A new chat does not supply a previous conversation ID. Continuing an existing chat supplies recent messages from that owned conversation only. Product instructions still apply to both.
No. A message is one user or assistant entry. A typical completed exchange adds two messages. The count limit is an upper bound on prior messages included, and byte limits may reduce it further. It is not a token-based context-window specification.
Guest and account history use separate identities. Signing in does not automatically transfer the guest conversation into your account. Preserve any important non-sensitive information yourself before changing sessions.
Check whether you are in the same browser guest session or the correct signed-in account. Guest expiry, deletion and an unavailable history service can affect access. The current recent-history list is bounded; it is not a complete export tool.
Signed-in users can add a private text source or connect an existing authorized document through Workspace > Knowledge. Selected excerpts and source versions accompany the reply. PDF/binary file extraction and automatic long-term fact memory are not provided.
Deletion removes that conversation and its saved messages from the active history store. It does not retrain a model, undo actions in external systems or delete separate billing, audit or backup records. Review the privacy policy for the processing boundary.
KEEP THE THREAD
Continue a saved conversation or start a new one with a focused brief.