$ the-wire · showcase
Codex adds Vim search motions and MCP tool result hooks
By RepoJournal · Filed · About OpenAI
openai/codex 0.151.0 lands with MCP upgrades and sandbox fixes, while the composer gains Vim-style search.
Codex 0.151.0 [1] adds a configurable grace period for discovering tools from optional MCP servers, lets extensions inspect or replace MCP tool results before they reach the model, and improves plugin catalogs to combine per-repository configuration without hiding valid plugins. It also preserves restored permission profiles across TUI turns and prevents `/cd` from weakening sandbox restrictions. The composer now supports Vim search motions: `/` and `?` do draft-local forward and backward literal search, with `n` and `N` for wrapped repeat, working after delete, change, and yank operators while skipping atomic elements and partial graphemes [2]. Diagnostic report uploads are hardened: the core event goes before attachments, each attachment uploads in a separate gzip-compressed envelope, with size bounds and format-aware truncation for JSONL, plus retries within a shared upload-time budget [3]. Resuming a thread without an explicit `cwd` now restores it from owned snapshots, so forked history and compaction no longer pull settings from another thread [4].
Action items
- → Review MCP tool result hooks in 0.151.0 for extension compatibility openai/codex [plan]
- → Test Vim search motions in the composer openai/codex [monitor]
- → Verify thread cwd restoration with forked history openai/codex [monitor]
References
- [1] 0.151.0 ↗ openai/codex
- [2] Add Vim search motions to the composer ↗ openai/codex
- [3] Harden diagnostic report uploads ↗ openai/codex
- [4] Restore thread cwd from owned settings snapshots ↗ openai/codex