Additional AI Service Support Is Reviewed Without Changing the Core

When considering adding AI services outside the current official support scope, we review expansion possibilities following the Adapter separation principle to avoid contaminating existing Providers and the memory Core.

New AI services continue to appear and existing services' screens change frequently. If the only goal is to quickly increase the support list, per-Provider exceptions can mix into the Core and even existing services can become unstable. When reviewing additional support, 5BY.AI prioritizes the principle of isolating detection logic in the Adapter.

Supporting one new Provider should not require changing existing Providers and the memory structure together.

What Changed in This Update

• Investigating conversation DOM, conversation identification, and completion events of candidate AI services in read-only mode.
• Checking whether Provider-specific selectors and detection logic can be separated as Adapter options.
• Logical pair, Pack, Saved, Anchor, and Handoff use the existing Core contract as is.
• Separately verifying that there is no regression in existing officially supported Providers.
• Confirming that actual collection, storage, and reentry flows are stable before announcing as officially supported.

How to Verify

1. Users should primarily use AI services in the current official support scope.
2. New service support requests can be left at /feedback with the intended use case.
3. Even if a support candidate is disclosed, the experimental state and official support state are distinguished.
4. When confirmed as officially supported, the Provider contract on the homepage and guide pages is updated together.

Example in Actual Usage Flow

For example, when the user checks the current improvement status, users primarily use AI services in the current official support scope. New service support requests can be left at /feedback with the intended use case. Then when confirmed as officially supported, the Provider contract on the homepage and guide pages is updated together. In this process, the following scope should not be confused with the current completion status. Providers are not added without stability verification just because there are many support requests. Checking this way helps distinguish between already provided features and parts still being stabilized.

Before and After the Change

Before the improvement, the currently provided scope and parts still being stabilized could appear mixed within a single sentence. In this update, when considering adding AI services outside the current official support scope, we review expansion possibilities following the Adapter separation principle to avoid contaminating existing Providers and the memory Core. Already provided features are preserved as is, and only improvement targets are described separately so users can understand the current status without exaggeration.

Scope and Things to Note

• Providers are not added without stability verification just because there are many support requests.
• Provider-specific DOM selectors or exception branches are not put into the Core.
• Unofficial experimental states are not expressed as public support.
• The AI service's own policies, regional restrictions, and account features are not controlled by 5BY.AI.

Why This Change Matters in the Overall 5BY.AI Structure

The purpose of expanding support scope is not to increase the number of Providers but to maintain the user's thinking continuity in more environments. Maintaining the Adapter boundary reduces the risk of one service's UI changes affecting other services and the Core memory structure.

Criteria for Verifying This Update

• The scope being improved and the scope already stably provided should not be mixed in the same sentence.
• UI and Provider compatibility improvements should not change the memory Core's storage units and user choice contract.
• Items not yet completed should not be expressed as currently provided features and should be updated in subsequent updates.

Related Pages

• Why Provider Changes Are Absorbed in the Adapter
• Continuity Across Supported AIs
• Leave Support Requests