ModelPanel gateway 0.7.0 — the registry belongs to the user

A gateway that ships a provider list has already made a decision for you. It knows which providers you might use, which models they expose, and how those facts change. The list is convenient right up until it is wrong. Then it is just a stale config with a confident interface.

ModelPanel gateway 0.7.0 takes that decision back. The repository ships no provider roster. Your routes live in your registry, on your machine, where they can be reviewed like any other configuration.

The empty state is the feature

The important change is what happens when the registry file does not exist:

npx modelpanel registry add groq/openai/gpt-oss-120b \
  --base-url https://api.groq.com/openai/v1 \
  --tier free-permanent \
  --context 131072

The command previews the route before writing it. Re-adding a route updates it through the same locked, auditable path as other registry changes. Deleting a route records a tombstone, so a later catalog update does not silently bring it back.

That last detail matters more than it sounds. A delete command that only removes today’s row is not a delete command if the next refresh can resurrect it.

The registry can now be absent, empty, or populated. A missing directory or invalid registry bytes still fail closed. An absent file is the normal empty state. The fusion route remains intrinsic to the gateway instead of being another line in the user’s roster.

One adapter, many providers

The registry entry carries the provider base URL and the quirks needed to talk to it. The gateway continues to use one OpenAI-compatible adapter rather than growing a new code path for every service. That keeps the boundary honest: provider differences belong in configuration, while request normalization, fallback, and policy stay in the gateway.

The result is a smaller default product with a clearer contract:

• your keys stay in your vault;
• your routes stay in your registry;
• the gateway does not pretend to know which free tier is healthy today;
• the fusion sidecar remains available when you choose to use it.

Why this is a breaking release

Older gateway versions expected a shipped or managed roster. A registry containing removed markers is not safe to hand to a gateway at or below 0.6.0, because those versions do not understand the field. Keep the downgrade path explicit: upgrade the gateway before pointing it at a 0.7.0 registry.

That is the tradeoff. The gateway gives up a list that was convenient but wrong, and gets a registry that is smaller, inspectable, and owned by the person who knows their keys.

The ModelPanel gateway README documents the install, add, delete, and serve path. The ModelPanel product page shows how the gateway fits beside the rest of the stack.