Skip to content

Surface resolved Databricks model metadata#9206

Open
jh-block wants to merge 1 commit into
mainfrom
surface-databricks-resolved-model
Open

Surface resolved Databricks model metadata#9206
jh-block wants to merge 1 commit into
mainfrom
surface-databricks-resolved-model

Conversation

@jh-block
Copy link
Copy Markdown
Collaborator

@jh-block jh-block commented May 14, 2026

Summary

  • add inference metadata to assistant messages so providers can report the resolved model used for a response
  • opt Databricks into resolved-model reporting using the model returned in provider usage
  • show the latest resolved model in the desktop model dropdown and inline model-change notifications between messages

Scope

Only Databricks for now, but the mechanism is intentionally general and support can be added to any other providers that report the resolved model (e.g. gpt-5.5 -> gpt-5.5-2026-04-23) in their responses.

Screenshots

When clicking on the model name in the bottom bar:
image

Disclosure shown inline in the chat when the resolved model changes (either because the user changed the model, or because an alias like 'goose' was updated server-side to point to a different model):
image

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5ec5d57108

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread ui/desktop/src/components/ProgressiveMessageList.tsx Outdated
@jh-block jh-block force-pushed the surface-databricks-resolved-model branch 3 times, most recently from b8aeb16 to 33aba82 Compare May 14, 2026 11:06
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 33aba82d5a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread crates/goose/src/agents/agent.rs Outdated
Comment thread ui/desktop/src/components/BaseChat.tsx
@jh-block jh-block force-pushed the surface-databricks-resolved-model branch from 33aba82 to 478eccd Compare May 14, 2026 11:29
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 478eccd5b6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread crates/goose/src/agents/agent.rs
Signed-off-by: jh-block <jhugo@block.xyz>
@jh-block jh-block force-pushed the surface-databricks-resolved-model branch from 478eccd to cd07081 Compare May 14, 2026 11:41
@jh-block jh-block requested a review from DOsinga May 14, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant