Sessions and sharing

A session contains the conversation, tool activity, model usage, and relationship to any child sessions. Sessions are stored locally by the embedded runtime.

Start and resume sessions

  • Select New Task to start with a clean conversation.
  • Open History to resume, rename, archive, or delete a local session.
  • Use Open in Tab when you want a larger view of the same workflow.
  • Start a new session when the goal changes substantially.

The sidebar, editor tabs, and Agent Manager use the same local session store in the current VS Code extension host.

Export a transcript

Run /export in chat or choose Export session transcript from the session menu. BIGGI saves the complete local session as Markdown, including content that may no longer be loaded in the visible message list.

Review the file before sharing it. A transcript can contain:

  • Source excerpts and file paths
  • Prompts and model responses
  • Commands and tool output
  • Error messages and environment details

When session sharing is enabled and the configured sharing service is available, choose Share session or Publish from the session menu. Anyone with the link may be able to read the published content.

⚠️Warning

Publishing is a networked action. Remove secrets, private source, internal URLs, personal data, and sensitive tool output before creating or distributing a link.

If sharing is disabled or the service is unavailable, export a Markdown transcript and share it through a channel you control.

Delete or archive

Archiving hides a session from the active list without removing its history. Deleting removes the local session record and should be treated as irreversible.

Git branches, worktrees, and files are separate from session history. Removing a session does not automatically revert code.

Parallel sessions

For multiple active tasks, use Agent Manager. Managed worktree sessions add branch, terminal, and diff state around the same underlying local agent workflow.