Your local project, chosen agent, and its required account or provider configuration.
An improved empty state whose link works, and a clear view of which files Codex changed.
Make one small change, inspect the diff, and check the intended behavior. A PATH check alone does not establish readiness.
Handing a coding agent a big task on day one makes it hard to tell what it did or whether it worked. This guides your coding agent through one bounded change in your own project, from prerequisites to a checked result, so you see the whole loop once.
It covers choosing the workspace in the CLI or editor integration, having Codex find the repository instructions, scripts and current changes, and giving it one visible outcome with constraints and a way to verify it. The worked task improves the empty state on a main list: it explains what belongs there and adds a link to create the first item.
You then review the evidence: the diff, the running result, and which checks actually ran or were blocked. A check that could not run is resolved, not treated as a pass. You keep a small checkpoint to return to before moving to a larger task.
You need a local project and access to Codex through your chosen interface. Provider accounts, model weights, GPU compute and hosting are not included.
No reviews yet.
Sign in to rate this Vibe.
Learn the loop of brief, edit and review on one small change, with Claude Code launched in the right folder and the result checked.
Give Codex a clear task, inspect its changes, and verify your first result.