Sessions & History

How Sessions Work

Every interactive YeePilot conversation is stored locally as a session. Sessions keep:

• your prompts
• AI responses
• command proposals
• approval decisions
• execution output

When you open YeePilot again, it resumes the most recent session by default.

Start Fresh Or Return Later

Create a new session:

/new

List and switch sessions:

/sessions

Rename the current session:

/rename nginx-audit

These same tasks are also available in the Neural HUD Sessions tab.

Search And Browse Sessions In The HUD

The Sessions tab is the easiest way to work with a larger session library.

You can:

• search saved sessions
• switch sessions with Enter or click
• create a new session quickly
• see compact metrics such as message and token totals

If you work across many servers or projects, the HUD is much faster than relying on memory alone.

Export A Session

Use:

/export

YeePilot exports the current session so you can keep a record, share the outcome, or attach it to a ticket or incident note.

History Inside The Current Session

Use:

/history
/history search nginx

This is useful when you want to find something you already asked or a command that ran earlier in the same conversation.

Where Sessions Are Stored

Sessions are stored on your machine under:

~/.yeepilot/sessions/

They are local client data, not public website content.

Good End-User Habits

• create a new session for each distinct task
• rename important sessions while the context is still fresh
• export sessions that matter for audits, reports, or incident reviews
• use the HUD search when your session list starts to grow

Separate sessions keep YeePilot focused and make it easier for you to return to the right context later.