A post in r/ClaudeCode this week put a name on something. The agent keeps "presenting me with decision cards", and it feels like "instead of me controlling the coding agent, it starts to control me". The fix they want: "agents digest MY context and implement it with sufficient authority to prevent these unnecessary escalation."
Two replies stuck with me. One: "Anything reversible inside the task, the agent decides and writes it down in a short log. Anything touching requirements, new deps, schema or deleting stuff, it stops and asks." The other: "A question that doesn't carry its own context isn't worth answering."
For people running Codex (or Claude Code, Cursor) on real projects:
- What does your agent decide on its own, and what has to come back to you?
- Where do the decisions it made alone get written down, and does the next session read them?
- How many of its questions could it have answered if it knew what you'd already decided?
- What are you building, and with which tools? (I'm collecting real workflows to test against.)
Background: I used to burn hours re-briefing AI tools, and I'm building a fix: project decisions kept in the cloud that any coding tool reads over MCP at the start of a session and saves to at the end. No name, no link. Would you pay for that, or does a decisions log in the repo do it?