After a week of working with Codex, it's easy to get tangled up: lots of threads, a few half-finished projects, and notes scattered around your personal-os folder. Each thread only remembers what happened inside it. And Codex's answers and plans can be long, overwhelming, or more complicated than your problem really is.
If something feels like too much, trust that feeling. You don't have to untangle it yourself. Codex can find your past threads, gather everything about a project in one place, and re-explain its thoughts to you in whatever way helps you understand them better.
That's what you'll do in the next 30 minutes: look back over your week, pull one big project together, ask Codex to simplify it, and give it a clean home in your personal-os folder.
Keep several threads going at once. Send a prompt, and while Codex works, start the next one. Come back when it's done. Never sit and watch a thread.
Open your personal-os project in Codex. Start a new thread for each prompt below, send it, and move on to the next one while Codex works. Codex knows how to find your past threads, so you don't need to tell it where they are.
Find my Codex threads from this past week, and look through my personal-os folder. List every project or idea I worked on, with one line on where each one stands. Keep it short.
Find my Codex threads from this past week. Pick the three moments where I seemed most stuck, confused, or frustrated. For each one, tell me in two sentences what was going on and what was really blocking me.
Find my Codex threads from this past week. Find the ideas, answers, or plans I seemed excited about but never followed up on. List up to five, with one line on why each might be worth coming back to.
Find my Codex threads from this past week. Find the moments where things clicked: something worked, or I was clearly happy with the result. What was I doing differently in those moments?
Before sending: describe the thread in your own words: what you were working on, or how it felt.
I'm thinking of a thread from this week where I [describe the thread]. Find it, and tell me in a few sentences where I left off and what the next step was.
Read each answer as it comes back. If anything surprises you, ask Codex to show you the thread it came from.
Pick the project that's most ambitious or most tangled right now. If you're not sure, pick one from "Where I got stuck."
Start a new thread and send this prompt:
Before sending: name your project.
Find every Codex thread from this past week, and every note in my personal-os folder, about [my project]. Tell me everything you find: what I'm trying to do, what I've tried, what went wrong, what I decided, and what's still open.
While Codex works, start a voice note in the same thread, and talk. Share as much about the project as you can. Codex has your threads, but only you know what's in your head. Don't organize it, just talk. If you run out of things to say, try these:
1. What are you trying to make, and why does it matter to you?
2. What would it look like if this went really well?
3. What have you tried so far?
4. Where did you get stuck, or confused, this week?
5. What decisions are you putting off?
When you're done talking, send the voice note. This thread now holds everything about your project, and that's what the next section works from.
A big project with a week of history is a lot to hold in your head, and Codex's first answer about it is often long and tangled. Ask Codex to look at it from a few different angles at once.
Wait for Codex to finish. Before you send this, make sure Codex has finished gathering your project context, and that you've sent your voice note from section 2.
Send this in the project thread from section 2:
Answer each of these questions about my project, all in one reply. Keep each answer to a few sentences. 1. What would this look like if it were easy? 2. Give me the simplest first step I could take here. 3. What context do you think I'm missing to move forward on this? 4. How have I overcomplicated this, and what is my actual goal, as far as you can tell? 5. If I could only do one thing on this today, what should it be? 6. Explain where I am with this in three sentences, as if you were telling a friend. 7. What am I avoiding here? 8. What would you cut from this if I had half the time?
The reply will be long. You can reshape any reply Codex gives you, as many times as you like. Try a few of these short follow-ups:
Then check the answers against your gut. When one feels wrong, tell Codex why in a sentence, and ask it to try again. Keep going until you can say two things out loud, in one sentence each: what you're really trying to do, and what you'll do next.
Everything you just worked out lives in one thread, and the next thread you open won't remember any of it. Save the simple version to your personal-os folder, so every future agent starts from it. While you're there, tidy up the rest of the folder.
Send this in your project thread from sections 2 and 3:
Propose a home for this project in my personal-os folder. It should hold the simplified version of everything we worked out in this thread: what I'm really trying to do, where it stands, what I've decided to skip, and my next step. Keep it short, and easy for me and future agents to read. Tell me what you'd create and where, but don't create anything until I say yes.
While Codex works, start a new thread and send this:
Look through my personal-os folder and suggest how to organize it better around what's actually in it: what to group together, rename, merge, or archive, and what would help an agent find its way around. Give me a short list, most useful first. Don't change anything until I say yes.
Both threads come back with a proposal, not changes. Read each one and say yes to what you like. Approve your project's home first, then the reorganizing, so the two threads don't move the same files at once.