Sessions

What is a Session?

Every time a shim connects to Conduit, a new session is created. A session groups all messages from one proxy connection — typically one AI client conversation with one MCP server.

The session rail on the left side of the Traffic tab shows all sessions with:

• Server name
• Message count and error count
• Start time
• Pin and rename controls

Managing Sessions

Pin & Rename

• Pin a session to keep it at the top of the list under the “Pinned” group
• Rename a session by clicking its title — useful for labeling test runs (e.g. “before refactor”, “after fix”)

Delete

Delete a session to remove it and all its messages from the database.

Clear Messages

Clear all messages from a session without deleting the session itself.

Export & Import

Export

Export a session as a .conduit file — a portable SQLite database containing the session and all its messages.

1. Right-click a session (or use the session actions menu)
2. Choose Export
3. Pick a save location

Import

Import a previously exported .conduit file:

1. Click Import in the session rail header
2. Select the .conduit file
3. The session appears in the rail with an import indicator

Tip

Use export/import to share interesting traffic captures with your team, attach them to bug reports, or archive test sessions.

Diff View

Compare two sessions side-by-side to spot differences — useful for regression testing or comparing server behavior before and after changes.

1. Select two sessions for comparison using the diff-select controls in the session rail
2. Switch to Diff mode in the Traffic header
3. The diff view shows:
   • A summary bar with counts of added, removed, and changed messages
   • A virtualized entry list showing matched message pairs
   • A Monaco diff editor for changed payloads, highlighting exactly what changed

The diff uses LCS (Longest Common Subsequence) matching with JSON-normalized payload comparison to identify meaningful changes.