Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Codex App-Server Runtime

Codex App Server Runtime Hermes can optionally hand and turns to the Codex CLI app server instead of running its own tool loop. When enabled, terminal commands,

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/codex-app-server-runtime

Codex App Server Runtime Hermes can optionally hand and turns to the Codex CLI app server instead of running its own tool loop. When enabled, terminal commands,

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Why
  2. What tools the model actually has
  3. 1. Codex's built-in toolset (always on)
  4. 2. Native Codex plugins (auto-migrated from your codex plugin install)
  5. 3. Hermes tool callback (MCP server, registered in ~/.codex/config.toml)
  6. What's NOT available on this runtime
  7. Workflow features (/goal, kanban, cron)
  8. /goal (the Ralph loop)
  9. Kanban (multi-agent worktree dispatch)
  10. Cron jobs
  11. Trade-offs
  12. Prerequisites
  13. Enabling
  14. Self-improvement loop (memory + skill nudges)

Section map

Why

Maps why to the Core Features documentation path, with the source page reserved for exact commands and updates.

What tools the model actually has

Maps what tools the model actually has to the Core Features documentation path, with the source page reserved for exact commands and updates.

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

Maps 1. codex's built-in toolset (always on) to the Core Features documentation path, with the source page reserved for exact commands and updates.

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

Maps 2. native codex plugins (auto-migrated from your codex plugin install) to the Core Features documentation path, with the source page reserved for exact commands and updates.

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

Maps 3. hermes tool callback (mcp server, registered in ~/.codex/config.toml) to the Core Features documentation path, with the source page reserved for exact commands and updates.

What's NOT available on this runtime

Maps what's not available on this runtime to the Core Features documentation path, with the source page reserved for exact commands and updates.

Workflow features (/goal, kanban, cron)

Maps workflow features (/goal, kanban, cron) to the Core Features documentation path, with the source page reserved for exact commands and updates.

/goal (the Ralph loop)

Maps /goal (the ralph loop) to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Why, What tools the model actually has, 1. Codex's built-in toolset (always on), 2. Native Codex plugins (auto-migrated from your codex plugin install), 3. Hermes tool callback (MCP server, registered in ~/.codex/config.toml). Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: codex, app-server, runtime, server, optionally. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for codex app-server runtime before applying exact upstream commands.

Verify firstWhy

Open the source anchor for Why and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Why; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for What tools the model actually has if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page