Ellivien Codex helper

Codex Handover Builder

A gentle way to make the file Codex reads at the start of a new shell, so she knows the rules, the project, your preferences and whether you want a practical tool or a named coding companion.

What this makes

This builder creates a starter Markdown handover document. You can save it as something like CODEX-HANDOVER-ACTIVE.md inside your project folder, then ask Codex to read it before doing any work.

Privacy note: this runs in your browser. It does not send your answers to me, Blogger, OpenAI, Netlify or anyone else. Still, do not put API keys, passwords or private tokens into it.

Important: a handover is not magic permanent memory. It is a practical context file. Keep it short enough that Codex can read it easily, and update it when rules or project state change.

1. Project basics

Project name

Handover file name

Folder Codex is allowed to access

What are you building?

2. Permission rules

Tick the boundaries you want Codex to follow. These are deliberately cautious.

Only work inside the allowed folderCodex should not inspect or edit unrelated files. Read before actingCodex should inspect relevant files before suggesting changes. Do not edit unless explicitly askedUseful if you usually want to discuss first. Do not deploy unless explicitly askedPrevents accidental Netlify or production deploys. Do not install packages unless explicitly askedPrevents surprise dependency changes. Ask before destructive actionsNo deleting, resetting or overwriting important work without approval. Protect secretsNo API keys, passwords or tokens in public screenshots, posts or copy/paste text.

3. Command preferences

Keep commands pasteableGive complete commands I can paste into Terminal. I use macOS TerminalFormat examples for Mac unless I say otherwise. Environment variable commands on one lineHelpful for people copying into Terminal. Explain commands before I run themGood if Terminal still feels frightening. Summarise command outputTell me what mattered instead of dumping noise.

4. How you want Codex to be

Some people want a neutral coding tool. Some people want a named coding companion. Both are valid.

Working style Named coding companion Practical coding tool Gentle technical teacher Direct senior engineer

Codex name, if any

Tone and teaching preferences

Optional emerging persona notes

Use simple explanationsNo unnecessary jargon. Name risks clearlyTell me when something could break, expose data or cost money. Keep updates conciseWarm is fine. Waffle is not. Support me when I am tiredUse smaller steps and less technical density. Challenge me when neededPush back if my plan is risky, unclear or too much at once.

5. Current project state

What already works?

What is broken, confusing or active?

Anything Codex must not touch?

Useful commands or notes

Generate your handover

Press the button, then copy the whole Markdown file. Save it inside your project folder using the file name you chose above.

How to use it

Save the generated text as your handover file inside your project folder. Then start a new Codex shell from that folder and begin with:

Before we begin, read CODEX-HANDOVER-ACTIVE.md. Do not edit anything yet. Please tell me what you understand about the project and the rules.

If your handover file has a different name, use that name instead.

© 2026 Ellivien · ellivien.blogspot.com · This is an Ellivien helper, not official OpenAI documentation.