Key points
- Users can now configure Google Cloud Vertex AI via a new setup wizard using Application Default Credentials or credential files.
- Local image attachments can be previewed while composing messages in supported terminals, with clickable transcript paths to open viewed images.
- The update includes fixes for saved chat visibility after switching model providers and improved handling of network approval prompts.
According to the release notes, users can enable the gcp_setup_wizard to configure access using Application Default Credentials or a specific credential file.reported
How we got here
What is new
The update introduces several interface enhancements. Users can preview local image attachments while composing messages on supported terminals. Clickable paths in transcripts now allow users to open viewed local images directly. Additionally, the command center and session picker now mark unread results, helping users track activity across multiple sessions. Users can also switch between connected backends from the terminal session picker while retaining their drafts.
Reading between the lines
The release notes highlight improvements to context management and error handling. Automatic context compaction now accounts for retained output from failed responses and responses with missing token usage data. The app-server README updates cover managed network constraints and prompt-user command rules that require fresh human approval, indicating continued focus on security and control.
The open questions
The release notes do not specify which terminals support local image previews, leaving uncertainty about compatibility. It is unclear whether the Vertex AI setup wizard supports all Google Cloud authentication methods or only the two mentioned. The impact of the new context compaction rules on conversation length limits is not detailed. Users must verify if their specific terminal environment supports the new image preview feature.
Why it matters
- Model evaluators can now test Codex with Google Cloud Vertex AI, expanding the range of backend providers available for evaluation.
- Local image preview functionality allows for better assessment of multimodal capabilities within the terminal environment.
- Improved context compaction handling may affect how evaluators measure performance in long-running conversations with failed responses.
- The ability to switch backends while keeping drafts facilitates comparative testing across different model providers.
Topics: tools, models, vendors, openai, google cloud
Updated
The strongest doubt
Counterpoint from the sources
The release notes do not confirm if the Vertex AI setup wizard is available for all user tiers or regions.
Try it
codex agents --no-daemon
Good result: Opens the agent command center without running a background daemon.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
How do I set up Google Cloud Vertex AI in Codex 0.167.0?
Enable the gcp_setup_wizard and follow the prompts to configure access using Application Default Credentials or a credential file.
Can I preview images in all terminals?
The release notes state that local image previews work on supported terminals, but do not specify which ones.
What happens to my drafts when I switch backends?
The update allows users to switch between connected backends from the terminal session picker while keeping their drafts.
Connected stories
Reading receipt
- Users can now configure Google Cloud Vertex AI via a new setup wizard using Application Default Credentials or credential files.
- Local image attachments can be previewed while composing messages in supported terminals, with clickable transcript paths to open viewed images.
- The update includes fixes for saved chat visibility after switching model providers and improved handling of network approval prompts.
Still open: Which specific terminals support local image previews?
Still open: Does the Vertex AI setup wizard support all authentication methods?
