The Codex ingest stack: GitIngest and Repomix

Use this stack as a page: the Codex ingest stack.

Codex is OpenAI’s terminal coding agent: a host that edits a checkout and runs commands. It is not in our CanIUse matrix. It still needs context of a repo that may or may not be on disk yet.

Two packers keep getting collapsed into one product. They are not:

1. Codex — the host.
2. GitIngest — prompt-ready extract from a public GitHub URL.
3. Repomix — one file of a local tree, with ignore rules.

Clone versus extract

If the repo is public and you have not cloned it, swapping hub for ingest in the GitHub URL (or running GitIngest) is the fast path: a prompt-sized dump without a working tree. That is a read. It does not edit GitHub for you.

If you already have a clone — because Codex is about to change files — pack with Repomix. Do not round-trip the same tree through GitIngest “for freshness.” You will lose the branch you are on.

Head to head: Repomix vs GitIngest. Same job (feed a repo to an agent), different input (disk versus GitHub URL).

The three roles

Codex owns the checkout

Stay on one branch. Let it run tests. Do not ask GitIngest to apply the patch. Do not ask Repomix to commit.

GitIngest owns the public URL

Use it when there is no clone yet, or when you want a read-only snapshot of main to brief the agent. pipx install gitingest. Do not use it as a substitute for git clone if you intend to merge.

Repomix owns the local pack

npx -y repomix on the directory Codex is about to edit. Ignore junk. Paste the file. Then let Codex work in the actual tree, not in the dump.

One job, four steps

1. Point GitIngest at the public GitHub URL if you do not have a clone yet.
2. If the repo is already local, pack with Repomix instead of re-fetching.
3. Hand that file to Codex with the change you want. Stay on one branch.
4. Let Codex run the tests. Do not ask GitIngest to edit the tree.

More add-ons that bolt onto this host: Codex add-ons.