Academy → Using HermesOfficial documentation · clear explanation

Codex App-Server Runtime (optional)

Codex App-Server Runtime (optional)

Developer25 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Codex App-Server Runtime (optional) as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Why, What tools the model actually has, 1. Codex's built-in toolset (always on), then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

  • Understand Codex App-Server Runtime (optional) without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

MCP
A standard way to expose external tools, resources, and services to an agent.
Provider
The service that runs or provides access and authentication to a model.
Tool
A structured action the agent can call to read or change something.
Automation
Running work later or repeatedly with explicit success and failure conditions.
Topic map

What does the source say, and in what order?

  1. 01
    Why

    Start here to understand the core idea or structure.

  2. 02
    What tools the model actually has

    Read this after the foundation, then connect it to the previous step.

  3. 03
    1. Codex's built-in toolset (always on)

    Read this after the foundation, then connect it to the previous step.

  4. 04
    2. Native Codex plugins (auto-migrated from your codex plugin install)

    Read this after the foundation, then connect it to the previous step.

  5. 05
    3. Hermes tool callback (MCP server, registered in ~/.codex/config.toml)

    Read this after the foundation, then connect it to the previous step.

  6. 06
    What's NOT available on this runtime

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Workflow features (/goal, kanban, cron)

    Read this after the foundation, then connect it to the previous step.

  8. 08
    /goal (the Ralph loop)

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Kanban (multi-agent worktree dispatch)

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Cron jobs

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

npm i -g @openai/codex codex --version # 0.130.0 or newer
codex login # writes tokens to ~/.codex/auth.json
codex plugin marketplace add openai-curated # then via codex's TUI, install Linear / GitHub / Gmail / etc.
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Codex App-Server Runtime (optional)” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?