⚡ Hermes Home ← All comparisons 🧠 ELI5 🤖 Best Models 🌎 Community Get started →
Comparison

Hermes vs. Codex CLI

Codex was rewritten in Rust, now spans CLI, IDE extension, desktop app with Automations, and Codex Cloud. Here's how it compares to Hermes.

🖥️
Different scope.

Codex CLI is a capable multi-provider coding agent. Hermes is a persistent server agent with self-hosted scheduling, messaging, and automatic memory. Complementary tools.

You're here
Hermes
Persistent memoryYes, layered
Self-improving skillsYes, automatic
Self-hosted CLI schedulingYes
Desktop app schedulingN/A
Cloud executionN/A
Messaging integrationYes, 15+ first-party
Web UIYes, self-hosted
Provider supportYes, many
Open sourceYes, MIT
Language/runtimePython
AGENTS.md supportYes
Memory inspectabilityYes, markdown
Comparing
Codex CLI
Persistent memoryPartial (session history + AGENTS.md)
Self-improving skillsNo
Self-hosted CLI schedulingNo (CLI has none)
Desktop app schedulingYes (Automations feature)
Cloud executionYes (Codex Cloud)
Messaging integrationNone first-party
Web UINo (CLI + desktop app)
Provider supportYes, 12+ providers
Open sourceYes, Apache 2.0
Language/runtimeRust (rewritten 2025)
AGENTS.md supportYes
Memory inspectabilityPartial (session history)

The details

Both tools are open source and coding-focused. But they serve different runtime contexts.

What Codex is now

Codex CLI was rewritten in Rust in 2025, giving it a zero-dependency install and a noticeably faster startup. It now spans multiple surfaces: the command-line tool, an IDE extension, a desktop application, and Codex Cloud for managed execution. Provider support is genuinely broad — 12+ providers including Groq, Ollama, LM Studio, DeepSeek, xAI, and Azure OpenAI. If you want a coding agent that runs everywhere and touches every provider, Codex has made serious progress.

Scheduling: Automations vs. cron

The Codex desktop app includes an Automations feature that can run recurring tasks — but this is not the same as a headless server cron. The CLI itself has no scheduling capability. Hermes runs as a persistent server process and integrates directly with system-level scheduling, meaning jobs keep firing whether or not any GUI is open. For unattended background automation on a server, Hermes is designed for that; Codex's desktop Automations are designed for interactive desktop use.

Memory model

Codex supports session resumption and AGENTS.md — both genuinely useful for continuity within a project. But memory resets between separate sessions unless you explicitly resume. Hermes builds a living cross-project knowledge graph: facts, preferences, and learned context accumulate automatically across every project and conversation, and the agent can write new skill modules to extend its own capabilities. The difference is between remembering a conversation and permanently learning from it.

Provider support: a genuine Codex advantage

Codex's 12+ provider list — including Groq for speed, Ollama for local inference, LM Studio, DeepSeek, xAI, and Azure — is one of the widest in the CLI agent space. Hermes also supports multiple providers but the breadth here genuinely favors Codex for teams with complex provider requirements or budget constraints that push toward faster/cheaper models.

Using Hermes and Codex together

Because Hermes can spawn arbitrary subprocesses, it can orchestrate Codex as a sub-agent. A Hermes scheduled job can invoke codex for a specific coding subtask, collect the output, and incorporate results into Hermes's memory. This makes the two tools genuinely complementary rather than mutually exclusive: Hermes handles persistence, scheduling, and messaging; Codex handles the coding task with its provider of choice.

Full feature comparison

Feature Codex CLI Hermes
Persistent memoryPartial (session history + AGENTS.md)Yes, layered
Self-improving skillsNoYes, automatic
CLI schedulingNoYes, self-hosted cron
Desktop app AutomationsYes (desktop app)N/A
Cloud execution (Codex Cloud)YesN/A
MessagingNone first-partyYes, 15+ platforms
Web UINo (CLI + desktop)Yes, self-hosted
Provider support12+ providersYes, many
Open sourceYes, Apache 2.0Yes, MIT
AGENTS.mdYesYes
Memory inspectabilityPartial (session history)Yes, markdown
RuntimeRust (rewritten 2025)Python
Orchestratable from HermesYesN/A

Which should you choose?

Choose Hermes if you need
  • Persistent cross-session memory that accumulates automatically
  • Self-hosted scheduling with headless cron jobs
  • Messaging integrations — Slack, Telegram, Discord, and 12+ more
  • Python and ML-ecosystem compatibility
  • An agent that improves its own skills over time
Choose Codex if you need
  • The widest provider coverage (12+ including Groq, Ollama, xAI)
  • A zero-dependency Rust CLI with no Node.js or Python required
  • Codex Cloud for managed remote execution
  • Desktop Automations for recurring tasks in a GUI workflow
  • OpenAI-primary workflows with broad fallback options

Try Hermes for free

Self-hosted, open source, and running in minutes. No cloud account required.