Codex Daemon Profile Field Guide

Turn repeated web-dev chores into narrow, cheap, low-context Codex workers.

Original source pages and recordings require authorized access. The full article text here is public.

Turn repeated web-dev chores into narrow, cheap, low-context Codex workers.

Use this when a repeated CLI or browser-adjacent task deserves its own focused Codex profile instead of a full general agent.

Choose the right mechanism

Mechanism Use when Agent responsibility Artifact
Daemon profile Repeated narrow task Preview deploy checks, log triage, changelog drafting profiles/pro-<tool>.ts
Fake CODEX_HOME Hard isolation Disable memories/MCP/plugins unless needed .codex-daemon-home/
Command map Small tool vocabulary Literal tasks with predictable outputs README plus examples

Agent-ready prompt

Design a narrow Codex daemon profile for this repeated task.
Use one command map, one output shape, low reasoning by default, and no broad memory/MCP/plugin access unless required.
Keep it read-only first.
Write docs, examples, and a smoke test before using it on a real repo.

Applied stories

Preview deploy checker

Role: Frontend lead

Every PR needs preview status, changed-route browser proof, and a short verdict.

Agent brief: Create a read-only deploy-check profile that discovers preview URL, opens changed routes, and writes a browser receipt.

Done when:

  • profile file
  • command map
  • read-only proof
  • smoke test

Log triage worker

Role: On-call engineer

A local dev server spews logs and general Codex wastes context reading everything.

Agent brief: Create a profile that tails, filters, summarizes, and writes exact blocker text for the main Codex session.

Done when:

  • filtered log
  • blocker summary
  • no source edits
  • handoff path

Tips and gotchas

  • A daemon profile should be boring: one job, one command map, one output format.
  • Disable unrelated memories, MCPs, apps, and skills to keep context small.
  • Start read-only; add mutation only after a smoke test proves the profile is scoped.
  • Use low reasoning for literal CLI wrappers and reserve smarter models for ambiguous planning.

References

Source references