`codex plugin add firebase@firebase` fails

Open 💬 0 comments Opened Jun 5, 2026 by charlotteliang

What version of Codex CLI is running?

codex-cli 0.137.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.5 medium

What platform is your computer?

macOS

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

terminal

Codex doctor report

Codex version: 0.137.0
  Overall status: fail
  OS: Mac OS 26.5.1, macos-aarch64
  Install method: npm
  Auth mode: ChatGPT
  Model: gpt-5.5
  Git repo detected: false
  MCP servers configured: 0

  Failure:
  network.provider_reachability: fail
  ChatGPT base URL: https://chatgpt.com/backend-api/ connect failed (required)

  Warning:
  network.websocket_reachability: DNS lookup failed for
  wss://chatgpt.com/backend-api/<redacted>
  updates.status: curl: (6) Could not resolve host: api.github.com

What issue are you seeing?

## Bug: Cannot install Firebase Codex plugin

I’m unable to install the Firebase plugin using Codex CLI.

### Command

```bash
codex plugin add firebase@firebase

### Expected behavior

The Firebase plugin should install successfully and become available in Codex. Here's the firebase plugin setup: https://github.com/firebase/agent-skills/tree/main

### Actual behavior

The plugin does not install. Codex reports a failure instead.

### Environment

Codex CLI version: 0.137.0
OS: macOS 26.5.1
Architecture: macos-aarch64
Install method: npm
Auth mode: ChatGPT
Model: gpt-5.5
MCP servers configured: 0

### Diagnostics

codex doctor --json reports overall status fail.

Relevant failures:

network.provider_reachability: fail
ChatGPT base URL: https://chatgpt.com/backend-api/ connect failed (required)

network.websocket_reachability: warning
DNS lookup failed for wss://chatgpt.com/backend-api/<redacted>

updates.status: warning
curl: (6) Could not resolve host: api.github.com

### Notes

This may be related to DNS/network reachability, but the user-facing failure is that codex
plugin add firebase@firebase does not work. It would be helpful if Codex surfaced a clearer
error or documented whether this plugin ID is valid/supported.

What steps can reproduce the bug?

Uploaded thread: 019e998d-ab22-7631-9612-1d579fa457e6

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗