chrome-devtools in Codex only exposes press_key, so typing text sucks

What version of Codex CLI is running?

v0.124.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4

What platform is your computer?

Linux

What terminal emulator and version are you using (if applicable)?

bash

What issue are you seeing?

Using chrome-devtools through Codex, I don't get any normal text-entry tool.

I do get tools like:

• new_page
• list_pages
• take_snapshot
• take_screenshot
• press_key
• list_console_messages
• list_network_requests

But I don't get type_text, fill, or anything similar.

So if Codex needs to type into an input, it has to do it with press_key one character at a time.

Typing something like admin@test.com turns into:

a -> d -> m -> i -> n -> @ -> t -> e -> s -> t -> . -> c -> o -> m

That's a pretty bad experience and makes browser automation much more awkward and fragile than it should be.

What steps can reproduce the bug?

1. Configure Codex with the chrome-devtools MCP.
2. Start Chrome with remote debugging enabled.
3. Open a page with a text input.
4. Ask Codex to type into it.
5. Check the browser tools available in the session.
6. Notice there's no type_text/fill, only press_key.

What is the expected behavior?

Codex should expose a proper text-entry tool for chrome-devtools, like type_text, fill, or equivalent.

What do you see instead?

Only press_key, so text has to be entered one keypress at a time.

Additional information

Not sure whether this is:

• Codex filtering part of the MCP toolset
• the chrome-devtools integration only exposing a subset of tools
• or an MCP tool discovery/surfacing issue

Filing here because the problem seems to be in how chrome-devtools is exposed inside Codex.