Coding jobs through Codex

Use case

Small coding tasks still land on you. You send Hermes the task, the folder, and the file name. It runs Codex CLI on the machine where Hermes already lives, checks the result, commits, and reports back on Telegram. You stay in chat.

Edit before you send: The repo path, how you want the Telegram report shaped, and which folders Codex must not touch.

Prompt to paste into Hermes Agent

When I send a coding job, run it through Codex CLI in [REPO PATH]. Do not start until the message has all three: the task, the folder inside the repo, and the output filename. Before the first job, confirm `codex exec` works. If auth fails, tell me to run `codex login --device-auth` and stop. Do not guess. For a one-file job: 1. Repeat the task in one line and the file you will write. 2. Run Codex only in that folder. Refuse if the path contains .env, a secret, or [FOLDERS TO AVOID]. 3. Read the file Codex wrote. If it does not run or does not match the task, try once more, then stop and show me the error. 4. Commit that file with a one-line message. Do not push. 5. Telegram me: what changed, the commit, and how to run it. For a job that needs more than one file, send the subtask list first and wait for my yes. Do not launch Codex until I confirm the plan. If the Codex login expires later, ping me with the exact command to renew it. Do not keep producing empty files.

More Hermes Agent prompts

Chief of Staff that routes the team
You have several Hermes roles and you are still deciding who should do what. This is the standing entry point: one message can mix research, a draft, an outbound note, and a scheduling task, and Hermes splits them before anyone acts.
Inbox sorted before you wake up
The first half hour of the morning disappears into overnight email. Hermes reads what arrived, separates what needs you from what can wait, and leaves reply drafts in Gmail. You open Telegram, work the urgent items, and send only the drafts you still agree with.
Scored leads with a real first line
A blast of the same cold note does not get replies. You give Hermes a tight market, and it returns a sheet of prospects with a score and an opening line taken from something it actually found about that company.
Overnight demo page for each new lead
Building a custom page for every prospect by hand does not scale. Overnight, Hermes reads the lead sheet, looks at each company site, writes a one-page demo aimed at their problem, and puts a public URL back on the row. In the morning the first email can point at something already live.