Test app against Geo Designated Services — AI Gateway Beta surfaces x-geo FMs

[dgokeeffe]

Symptom

When the CODA app runs on a workspace with Geo Designated Services (GDS) configured, the AI Gateway Beta still exposes cross-geo (x-geo) foundation models in Claude Code's /model picker. Observed entries include:

• databricks-claude-sonnet-4-6
• databricks-claude-opus-4-7
• databricks-claude-haiku-4-5

These should be filtered to the workspace's designated geo when GDS is in effect.

Expected

GDS-enabled workspaces should only see foundation models served from their designated geo. Cross-geo FMs should be hidden from / rejected by the gateway-backed model picker so customers under data-residency contracts can't accidentally route inference out-of-region.

Repro

1. Provision (or use) a Databricks workspace with Geo Designated Services enabled.
2. Open the CODA app on that workspace.
3. Launch claude → run /model.
4. Observe: x-geo FMs still listed and selectable.

Ask

• Confirm whether the filter belongs in the AI Gateway Beta layer or in this app's model-list resolution.
• Add a test pass against a GDS-restricted workspace before next release.
• If the gateway is the gap, link out to the gateway-side issue so we can track the dependency.

Filed from: app version v0.18.1, Claude Code v2.1.128.