SethGammon/Citadel: README-based editorial guide

SethGammon/Citadel describes itself in the README as "The operating layer for Claude Code + OpenAI Codex: persistent project memory, intent routing, safety hooks, cost telemetry, and parallel agent fleets.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: An open-source operating layer for Claude Code and OpenAI Codex.. That establishes the project's stated boundary, not a production test.

The README's "Trust and scope" section gives a useful starting point for deciding whether the project fits: Citadel runs with the permissions of Claude Code or Codex. It does not replace code review, branch protection, or repository-specific checks.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Representative repository-operation shakedown. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Quick install". The source evidence includes: Requires: Claude Code or OpenAI Codex, Node.js 18+, and a git repository.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: git clone https://github.com/SethGammon/Citadel.git ~/Citadel When the README contains no runnable command, this article does not invent one. Open its "Start using it" section and confirm system dependencies, default ports, and first-run initialization before using a public server.