Sessions

A session is a single conversation with the RebelCore™ Agent. The Agent keeps your sessions across visits, so you can step away from a complex piece of analysis and pick it up tomorrow without losing context.

What a session contains

Each session captures:

• The prompts you’ve sent.
• The Agent’s responses, including any inference results.
• The data context that was active for those prompts (which datasets / specs were in scope).
• The timestamps for each exchange.

Because the data context is part of the session, opening an old session restores not just the conversation but also which gold vectors the Agent was working over at the time.

Finding past sessions

The Agent shows a session list in its side menu. Each entry usually shows:

• The session title (auto-generated from the first prompt or one you set yourself).
• When it was last active.
• A short preview of the most recent exchange.

Click any session to reopen it.

Starting a new session

Use the New session button (typically near the top of the session list). A fresh session starts empty — no history, no prior context. If you opened the Agent from a spec in the Tree, the new session starts with that spec already in scope.

Why sessions matter for governance

Sessions are also the unit of audit. Every prompt belongs to a session; every session belongs to a user; the Audit panel traces activity back to the session that produced it. This is what makes the Agent’s RAG-style answers traceable, even months later.

Tips

• Name your sessions. A session called “Q4 reconciliation — outliers” is easier to find than “Untitled”.
• Don’t be afraid to start fresh. If the conversation has wandered off course, a new session with a focused prompt is often faster than trying to redirect a long thread.
• One topic per session. Sessions stay readable when each one has a single purpose; mixing unrelated questions makes the audit trail harder to interpret.