Agents · Codex

Codex + Hydrant.

Wire Codex to Hydrant so a run can fetch issue context, inspect decisions, generate execution bundles, and update the project graph without leaving the Codex session.

Install

Point the harness at Hydrant

Hydrant is a hosted MCP server. Use the harness-native configuration path and replace the example token with a personal access token from your workspace settings.

Endpoint
https://hydrant.dev/mcp
Config
~/.codex/config.toml
Scope
Codex shares this config between the CLI and IDE extension on the same machine.
Codex install command
shell
export HYDRANT_PAT="hyd_sk_your-token-here"
codex mcp add hydrant --url https://hydrant.dev/mcp --bearer-token-env-var HYDRANT_PAT
~/.codex/config.toml
toml
[mcp_servers.hydrant]
url = "https://hydrant.dev/mcp"
bearer_token_env_var = "HYDRANT_PAT"
  1. 1

    Create a Hydrant personal access token

    Mint a token in Hydrant settings for the workspace Codex should read and update.

  2. 2

    Register the MCP server

    Use the Codex MCP command for remote HTTP servers. Store the token in an environment variable so ~/.codex/config.toml does not contain the secret itself.

    export HYDRANT_PAT="hyd_sk_your-token-here"
codex mcp add hydrant --url https://hydrant.dev/mcp --bearer-token-env-var HYDRANT_PAT
  3. 3

    Confirm the config file

    Codex reads MCP servers from ~/.codex/config.toml. Keep token-bearing config local to your machine unless your team has a separate secret-management convention.

Verify

Check the connection

Reload the harness, confirm the MCP server is present, then ask the agent to call a small read-only Hydrant tool.

Reload

Restart Codex or start a new Codex session, then check codex mcp list.

One-line tool call

Ask Codex: Use Hydrant to list_spaces.

Codex should discover the hydrant MCP server from ~/.codex/config.toml and call list_spaces through the tool list.

Skill catalog

Use your team's loop

These skills ship in .agents/skills/ and are harness-agnostic. Use them as a repeatable lifecycle, not as commands tied to one agent vendor.

shape

Shape the work

Plan the UX and UI before implementation starts.

refine

Clarify the brief

Turn rough requests into implementable Hydrant issues.

nail

Remove ambiguity

Tighten issue wording until the scope is unambiguous.

prep

Check readiness

Check readiness, dependencies, likely files, and branch state.

go

Do the work

Implement a ready issue end to end from Hydrant context.

preflight

Verify

Run the final quality gate before shipping.

yeet

Ship

Ship, merge, and clean up the branch once the work is ready.

Troubleshooting

Fix the common misses

Most connection failures are token, reload, or config-precedence issues. Check these before changing the Hydrant endpoint.

Hydrant is missing from Codex

Run codex mcp list and restart the current Codex session. If you edited TOML by hand, check the section name is [mcp_servers.hydrant].

Headers are not sent

Prefer the Codex CLI registration command. If you edit by hand, keep bearer_token_env_var inside the hydrant server block and export that variable before starting Codex.

Tools appear but calls fail

Rotate the Hydrant personal access token and replace the old value in ~/.codex/config.toml, then restart Codex.

Where to next

Finish the setup path

After the MCP server is connected, walk the quickstart once and keep the MCP surface reference nearby for tool names and common workflows.

Read quickstartMCP surface