Skip to main content
Different AI platforms have different page structures, behaviors, and account models. Ophel lets you configure settings independently for each site rather than applying a single global configuration. Go to Settings → Site Settings and select a site from the left sidebar to see its available options.

Model lock

Model lock solves a common annoyance: manually switching back to your preferred model every time you open an AI platform. Once configured, Ophel checks the model selector after the page loads and switches to your target model automatically. If the target model isn’t available on your account, Ophel leaves the current selection untouched. To set up model lock:
  1. Open Settings → Site Settings
  2. Select the site you want to configure
  3. Find the Model Lock section and toggle it on
  4. Enter a keyword from the target model’s name (matching is case-insensitive)
You only need part of the model name. Entering flash matches Gemini 2.0 Flash. If multiple models match, the first match is selected.
Each site’s model lock setting is independent, so you can configure different target models for different platforms. You can also toggle model lock for the current site quickly from Toolbox Model Lock.
If you manually switch to a different model during a session, model lock only kicks in again on the next page load — it won’t override your manual selection mid-session.
Supported sites:

Markdown rendering fixes

Some AI platforms have intermittent Markdown rendering bugs — bold text failing to render is a common example. Ophel provides site-specific toggles to patch these issues without affecting other platforms. Enable the fix for a site only if you actually see rendering problems — it is off by default on sites where the issue is less common.

Gemini watermark removal

When you export or screenshot a Gemini conversation, Gemini appends a “Created with Gemini” watermark. Ophel can strip this watermark automatically. Settings → Site Settings → Gemini → Remove watermark
Watermark removal requires the <all_urls> host permission, which Ophel will ask you to grant the first time you enable this setting. This permission lets Ophel intercept and modify the export request before it reaches the page. The setting is off by default.
The same watermark removal option is also available for AI Studio under Settings → Site Settings → AI Studio → Remove watermark.

Additional Gemini settings

Settings → Site Settings → Gemini: Settings → Site Settings → Gemini Enterprise only:

AI Studio settings

Settings → Site Settings → AI Studio provides controls for the initial state of various sections on the AI Studio page, so you don’t have to collapse them manually every time you open it:
The Default model setting on the AI Studio page is separate from the general Model Lock feature. Configure AI Studio’s default model here in the site-specific settings, not on the Model Lock section.

Claude session key management

Claude accounts have usage rate limits. When one account hits its cap, you normally have to wait for a reset. If you have multiple Claude accounts, Ophel can store Session Keys for all of them and let you switch instantly — keeping the conversation going without logging out and back in. A Session Key (sk-ant-sid... format) is the authentication token your browser session uses on claude.ai. Ophel injects the specified key into requests so you can switch accounts without a full logout cycle. Keys are stored locally in your browser and are never sent to Ophel’s servers. Adding a session key — go to Settings → Site Settings → Claude:
Switching between accounts:
Go to Settings → Site Settings → Claude and select a key from the current Session Key selector, or use Set as current on a key row.
After switching, Ophel refreshes the current Claude page to apply the new key. Managing the key list:
Exported JSON files contain the full Session Keys. Anyone with the file can use your account’s quota. Be careful when sharing WebDAV backups or local files that contain exported keys.

Usage monitor

For AI services with daily usage limits, Ophel provides a local counter that shows how many conversation turns you have used today and roughly how many tokens were consumed. The usage monitor runs entirely locally — it does not call any external APIs or rely on usage data from the platform. Ophel counts turns and estimates tokens by observing messages on the page. Settings → Features → Usage Monitor: When enabled, the widget displays:
  • Number of conversation turns today
  • Estimated input token count
  • Estimated output token count
  • A progress bar showing used / daily limit
Token estimates are based on character counting and may differ from the platform’s actual billing. Treat them as a rough reference, not an exact measure.
Last modified on June 18, 2026