Feature request: Add “Temporary Chat” action in Multi-Panel

[ji3g4m6zo6]

Hi! Thanks for building this extension, it’s very useful.

I’d like to propose a Temporary Chat action in Multi-Panel mode.
Some providers support temporary/private conversations (not saved to history), which is handy for quick tests or sensitive prompts without cluttering history.

Proposed UX

• Add a new toolbar button in multi-panel (near “New Chat for All”).
• On click:
  1. Run existing New Chat flow first.
  2. Wait for provider page transition/render.
  3. Trigger provider-specific Temporary/Private chat button.

Why this helps

• Better privacy control for comparison sessions.
• Less history pollution on provider websites.
• Consistent one-click workflow across panels.

Technical notes (DOM findings)

Important timing note:

• ChatGPT / Claude / Grok may need a short post-NEW_CHAT wait before temporary/private controls are interactable.
• Gemini may require opening side menu first in some layouts.

Useful selectors found during testing:

// Provider-specific temporary chat button selectors
const TEMP_CHAT_BUTTON_SELECTORS = {
  chatgpt: [
    '#conversation-header-actions button:has(svg use[href*="#28a8a0"])',
  ],
  claude: [
    'div.fixed.right-3.z-header button.Button_ghost__BUAoh',
  ],
  gemini: [
    'button[data-test-id="temp-chat-button"]',
  ],
  grok: [
    'a[href="/c#private"]',
  ]
};

const GEMINI_SIDE_MENU_SELECTORS = [
  'button[data-test-id="side-nav-menu-button"]',
];

Suggested implementation shape

• Reuse existing message architecture:
  • Host sends NEW_CHAT
  • After wait, host sends ENABLE_TEMP_CHAT
• Content script handles ENABLE_TEMP_CHAT with provider-specific selectors and retries.
• For Gemini:
  • If temp button is not found, click side-menu button first, then retry temp button.
• Unsupported/not-found cases can fail silently (log only), without breaking other panels.

If you decide to build this feature, feel free to reference my quick testing notes above—use whatever’s helpful and ignore the rest.

[Manho]

Thanks for the detailed write-up and the DOM research — really appreciate the effort! 🙌

This would be a really useful addition — having a one-click temp chat across all panels is something I've wanted too. The extension already relies on provider-specific selectors throughout the content scripts, so adding temp chat support is consistent with the existing maintenance model. And since broken selectors can fail silently without affecting core functionality, the risk is low.

A few things to keep in mind for the implementation:

1. Selector robustness — Some of the selectors (e.g. Button_ghost__BUAoh) look like build-generated class names that could change frequently. Consider using more stable attributes where possible (e.g. aria-label, data-testid), and add fallback selectors with retry logic.
2. Timing — The wait between NEW_CHAT and ENABLE_TEMP_CHAT should use a retry/poll approach rather than a fixed delay, since load times vary across environments.
3. Graceful degradation — Agreed with your suggestion to fail silently. If a provider doesn't support temp chat or the selector breaks, just log it and move on.

Feel free to open a PR if you'd like to take this on — or if you'd prefer to leave it as a feature request, I can pick it up when I have bandwidth. Either way, happy to move forward with this! 🎉