take two.

Free course · Registered members · Lesson 1 / 10

Codex, vibe coding and ownership of the result

Use natural-language requests to develop while keeping requirements, change review and tests.

20 minutes including practiceAll courses

Editorial team: Take Two · Published

Lesson preview

The result we want

Our project is Roma Blog: public articles and search, reader accounts and an editorial area for drafts and publication. A separate pipeline collects weekly events from Turismo Roma. A reader cannot become an editor by submitting a form field. Before coding, express these behaviours as observable checks: a draft must remain private even when someone knows its URL.

What Codex does

Codex CLI can inspect, edit and run code in a local repository. Start it in your project folder after installation and authentication, following the official setup guide in the sources. This course is free; it does not include a Codex subscription or promise plan availability or limits. Begin by asking for a file inventory without changes, then compare its response with the repository.

What to check as you practise

  • Observable acceptance criteria.
  • No changes or deployment in the first task.
  • Credentials kept outside the agent context.

Continue with the full lesson

Register free to access the complete explanation, examples, exercise and commented answer. This preview stays open to everyone.

Register / sign in free →

Workshop files · Version 1

The reference project

Download the complete blog, English and Italian instructions, SQL schema, agent contracts, fictional fixtures and tests. The sample blog interface is in English. This is a local learning project: password recovery, email verification and MFA remain extensions before opening it to a public community.

Download the blog project (ZIP) →

Free download. Full lessons require a free Take Two account. Codex access depends on your own plan.

Sources and further reading