Model Hub

Model Hub is Avibe’s default local model gateway. It keeps upstream credentials and routing on your machine, lets several Agent backends share the same source, and moves a request to the next configured source when the current one can recoverably no longer serve it. Open Models > Sources & gateway. The page has two parts:

• Sources lists the subscriptions and API keys you own. It is an inventory, not a priority list.
• Gateway shows each Agent backend and the effective Route chain for each model, inherited from default routing or saved as a manual override.

​

Choose gateway or direct mode

Gateway mode is the default on a fresh installation. An existing installation with no Model Hub configuration stays in Direct mode until you switch each backend from the Models page. The choice is per backend and reversible. Switching back to Direct keeps your Sources and Route chains, but that backend resumes using its own native configuration. A Native hop inside a Gateway Route chain is still Gateway mode: Avibe owns fallback and recovery for that chain.

​

Add a Source

​

Add a subscription

1. In Sources, select Add subscription and choose the vendor.
2. Choose where the credential stays.
3. Select Sign in and complete the vendor flow.

The recommended choice depends on the vendor:

• Claude: Use natively is recommended. Claude Code uses its local login. You can explicitly choose Sign in as a gateway source to supply other Agents, but Avibe shows the account-restriction warning before sign-in.
• ChatGPT: Sign in as a gateway source is recommended. It makes usage, quota, and takeover visible. Native Codex sign-in remains supported, but quota exhaustion will not trigger Gateway takeover and its usage stays outside Model Hub.

Each backend can have only one Native Source because its official CLI exposes one current login. Add additional accounts as gateway-held Sources. You can keep both channels by adding them one at a time.

​

Add an API key

1. Select Add API key.
2. Enter an optional name, a Base URL, and the API key. A custom Base URL can point to a relay, aggregator, or self-hosted compatible service.
3. Select Add. Avibe connects once, authenticates, identifies the interface, and fetches the model list before saving.

Fetch models runs the same check without saving anything. If Avibe connects but cannot identify the interface, choose a one-time interface hint and retry. The hint only changes probe order; Avibe still requires a successful response before it can save the Source. The identified interface is fixed after save. To change it, create a new Source. If the interface is identified but the model list does not return, you can retry or select Add anyway. The Source is saved without a discovered inventory, and you can add models manually from Source details.

​

Maintain the model list

After a Source is added, Avibe opens Source details > Models. From there you can:

• Select Refetch to test the saved Source, update its health, and refresh discovered models. This is the only saved-Source refresh action.
• Add a model manually when discovery cannot find it.
• Edit the exact reasoning tiers accepted by any discovered or manual model. No tier is selected or filled by default.
• Remove models you added manually. Models reported by the upstream are managed by refetch instead.

Refetch preserves manual models and the reasoning tiers you edited. Inventory changes can change automatic matching. If a change would remove effective hops or leave models without supply, Avibe shows the affected hops and models before asking you to confirm. A failed fetch keeps the last list the page actually read. For API-key Sources, the model list is matching evidence, not a list of the only models they may serve. A missing entry does not block an API-key request, and removing a manually added model does not delete a saved route. An explicitly retired Source/model pair cannot be used. Backend model support, Source compatibility, credentials, and health still apply; an unknown model does not acquire reasoning tiers that the Source has not declared for that exact model. Subscriptions, whether signed in as gateway Sources or used natively, keep their existing model support. They still participate in automatic matching and manual routes, but new or changed subscription hops must pass the existing model-list and retirement checks. Routing does not extend the models supported by the Gateway or native CLI for a subscription.

​

Configure default routing

In Gateway, choose a backend and open Default routing to select its default Sources and arrange their order. Models without a nonempty saved manual override follow these defaults; an empty saved chain also inherits them. Each effective Route chain is an ordered list of exact pairs: a Source and the upstream model it should call. For example, suppose two API-key Sources have the default order A, then B, and you request model-x. If only B lists model-x, the chain contains only B. If neither Source lists it, the chain is A, then B, using model-x unchanged at each hop. It does not try an unmatched A before a known match on B. Avibe first includes all eligible matches in default order, including matching subscriptions. Only when there are no matches does it use eligible default API-key Sources with the requested model ID unchanged. Subscriptions are not candidates for unknown-model passthrough. Native Claude matching recognizes its supported aliases and versions; other backends and API Sources use exact model IDs. Temporary unavailability does not turn a matched chain into passthrough. New models follow defaults automatically. Changes to default membership, order, or matching evidence update inherited routes; they leave saved manual chains unchanged. The dialog shows how many models inherit defaults and how many have saved overrides. Changes apply only to the selected backend. If changing default membership would remove effective hops, leave a model without supply, or affect an active request, Avibe shows the exact impact for confirmation. Reordering the same Sources needs no removal confirmation. Removing a Source from defaults keeps manual routes that use it; deleting the Source itself removes its references through a separate guarded change.

​

Edit a model route

Open a model in Gateway to inspect its chain. For an inherited route, select Edit route to start a manual draft. You can:

• add or remove a hop;
• reorder hops;
• change a hop’s explicit upstream model mapping, including an exact ID absent from an API-key Source’s model list; and
• select Save to store a nonempty chain as a manual override.

Manual hops may use compatible Sources outside this backend’s defaults. Saving a nonempty chain creates a manual override, even if it is identical to the automatic result. An empty chain is treated as no override: saving it restores inherited routing, not a disabled model. If a configuration Save requires a Gateway restart, Avibe waits for existing request transfers, including streams, to finish or close before restarting. New requests wait while the change is applied; saving does not cut off an active stream. The first runnable hop is used. Avibe walks the remaining hops when a hop is already blocked, or when it hits a fallback-eligible quota, rate, upstream, or network failure before output begins. Blocked hops stay visible in their planned positions; temporary health changes do not reorder the chain or substitute another model.

​

Restore automatic routing

In the route dialog footer, select Restore automatic to preview the inherited chain. Removing the last hop from a manual draft opens the same restore preview. This changes only the draft, and the result may be Passthrough or Unconfigured. Undo restore brings back the preceding manual draft. On Save, Avibe checks the effective route’s impact and asks you to confirm if needed before removing the override and applying inherited routing. The saved route stays unchanged until saving succeeds. Cancel or closing the dialog writes nothing. If saving fails, the draft stays available to retry.

​

Read the status

Each model’s route badge explains where its chain comes from: Hover over or focus a badge for its explanation, or tap it on touch devices without opening the route dialog. Escape or interaction outside the help dismisses it. These badges describe routing, not Source health or a guarantee that the upstream accepts the model; stopping the Gateway does not change the route’s origin. If inheritance produces no eligible hops, the model shows Unconfigured. This includes an unmatched model whose defaults contain only subscriptions. Use Configure default routing to choose eligible default Sources, or save a nonempty manual route. Health changes and request errors do not change the route’s origin. Source rows use these states: Each Gateway backend shows one supply status for its selected model: Taken over appears only when a recoverably unavailable first hop has handed the request to a later hop. A successful takeover is silent in the conversation. The Models page shows the current Source, the paused path, and the temporary replacement; the next turn returns to the first hop after it recovers, without changing your saved order.

​

Understand errors and recover

​

Latest recorded turn

The route dialog checks the latest retained, settled turn that Avibe can attribute exactly to this backend and model. If it ended with a terminal error, Latest recorded turn shows the recorded time and historical Source/model. View error details opens that same record’s safe structured details, including the reason and, when available, HTTP status and an observed error code. Raw upstream messages and credentials are excluded. A later recorded success or cancellation, or no retained record, leaves no old error panel. Failed reads offer Retry. This is not a record of every request: OpenCode’s shared-process requests remain untracked when they cannot be attributed to an exact turn. Error codes depend on what the upstream protocol actually returns. An observed model_not_found gets a model-not-found explanation; a generic Anthropic not_found_error is not rewritten to that code. Without a specific code, the panel uses the recorded reason. Route badges and Source health are separate from these details.

​

Messages on the Models page

​

Messages in a turn

​

Recovery by cause

• Cooldown or takeover: wait for the displayed retry time. Recovery and the return to the first hop are automatic and do not change the chain.
• Expired subscription login: follow Sign in again for that Source.
• Exhausted balance: top up with the vendor, then open Source details and select Refetch.
• Revoked API key: replace the key in the existing Source, then refetch. The Source identity and every Route position stay intact.
• Restricted account: follow the vendor remedy or move the affected model to another Source.
• Unclassified Error: fix the suspected upstream problem, then use Refetch. A successful current check clears the blocker.
• Model rejected by the upstream: verify the exact model ID and upstream support, then edit the model or route. Absence from an API-key Source’s fetched list alone does not mean the model is unusable; subscriptions retain their existing model checks.
• Source missing: edit the Route chain. Adding a new Source does not repair a hop that refers to the removed Source.
• Native CLI unavailable: restore the backend’s local CLI and login, then retry.
• Need an immediate escape hatch: switch only the affected backend to Direct. Your Sources and Route chains remain saved for when you switch back.