Sessions

Sessions maintain conversation context between you and the AI agent. Understanding session management helps you work more effectively.

Session Basics

What's in a Session

• Conversation history (all messages)
• Tool call results
• Node name registry (for referencing created nodes)
• Agent state (model, mode)

Session Lifecycle

1. Start: Click Connect or send first message
2. Active: Conversation continues with full context
3. End: Click Disconnect or close window

Managing Sessions

New Session

Start fresh with a new session:

• Click the New Session button
• All previous context is cleared
• Node references are reset

Use when:

• Starting a new task
• Context has become confused
• Want clean slate

Continue Session

Sessions persist within an editor session:

• Close and reopen chat window: Session continues
• Restart editor: Session ends

Save Session

Save conversation for later:

1. Click Save Session
2. Enter a name
3. Session saved to project

Load Session

Resume a saved session:

1. Click Load Session
2. Select from saved sessions
3. Conversation history restored

Node References

During a session, the tool tracks created nodes:

Agent: Created node "PrintString_a1b2c3d4"
You: Connect that node to the Branch True pin
Agent: [Knows which node you mean by "that node"]

Node references are:

• Valid within the session only
• Lost when session ends
• Based on asset + graph + name

Context Window

AI models have limited context windows. Large conversations may:

• Truncate older messages
• Lose early context
• Require session restart

Tips for long conversations:

• Start new sessions for new tasks
• Summarize completed work
• Keep individual requests focused

Multi-Agent Sessions

When switching agents mid-session:

• Conversation history transfers
• Tool results preserved
• Node references maintained

Note: Different agents may interpret history differently.

Troubleshooting

"Lost context"

The AI forgot earlier conversation:

• Context window exceeded
• Start new session with summary
• Reference specific assets by name

"Node not found"

The AI can't find a referenced node:

• Node reference from previous session
• Asset was modified externally
• Use asset path instead of session reference

Slow Responses

Long sessions accumulate context:

• Start fresh for faster responses
• Clear irrelevant history
• Consider smaller, focused sessions