AD
Episode
463
Interview
Web News

Trying Codex For The First Time Was… Confusing

Recorded:
March 17, 2026
Released:
March 24, 2026
Episode Number:
463

AI coding tools are evolving incredibly fast - but the user experience may not be keeping up. In this episode, Matt shares his first experience trying Codex on Windows and how a simple attempt to generate a classic Snake game quickly turned into a confusing experience filled with permission prompts, unclear setup steps, and rapidly draining usage credits. This sparks a larger discussion about whether AI development tools are moving so quickly that UX is being left behind. In this episode Matt and Mike discuss the gap between tools like ChatGPT and more advanced coding environments like Codex, why developer tools can still feel intimidating even with AI doing the coding, and how today’s AI ecosystem feels a lot like the early days of crypto - powerful but sometimes chaotic.

Listen

Also available on...
...and many more, check your podcast app!

Who’s in This Episode?

Show Notes

Is AI Developer UX Getting Worse?

A growing sentiment on this show is that AI UX is being left behind in the name of constant innovation. This situation hit a critical point with us when we started seeing the UX of AI developer tools such as Codex (main focus of our discussion), Claude Code, and more.

The Codex Experience: Dropped Into The Deep End

Matt recently installed Codex for Windows to try it out.

Instead of a guided experience, the tool immediately opened a file dialog asking him to select a folder - without any explanation of what it was for.

After skipping that step, Codex presented a playground environment with example prompts like:

  • Create a classic Snake game
  • Build something using PDFs
  • Generate different small applications

Matt tried the Snake game example.

But instead of simply generating code, Codex immediately began:

  • running tasks
  • requesting permissions
  • attempting commands like npm test
  • consuming account usage credits

All while the user has very little context for what's happening.

The Credit Anxiety Problem

One thing that stood out immediately was usage metering.

While experimenting with Codex, the system was already consuming 5% of available usage during a simple test.

For users experimenting with the tool for the first time, this creates anxiety:

  • What is the AI actually doing?
  • Is this normal usage?
  • Am I wasting my credits just testing things?

This is very different from tools like ChatGPT, where experimentation feels relatively safe.

ChatGPT vs Codex: Two Very Different UX Models

ChatGPT succeeds because the interface is extremely simple.

You open the app and see one thing:

A prompt box.

From there, users naturally learn through conversation.

They can ask:

  • What can you do?
  • Can you write code?
  • Can you explain this?
  • How do I do this?

The UX encourages exploration.

Codex, on the other hand, feels like it drops users directly into a developer workstation environment.

Without onboarding, that environment can feel intimidating - even for experienced developers.

The Gap Between “AI Can Code” and Real Developer Tools

A common narrative in AI right now is that AI is democratizing coding.

We often hear that anyone can now build apps without developers.

But tools like Codex highlight an interesting reality:

Even with AI doing the coding, the surrounding tooling still assumes familiarity with:

  • repositories
  • project folders
  • package managers
  • command execution
  • development environments

For someone coming from a ChatGPT-only experience, that leap can be massive.

When Powerful Tools Skip Onboarding

In contrast to Codex, many modern apps are obsessed with onboarding.

Some apps go so far as to guide users step-by-step through every feature.

Matt compares this with software like QuickBooks Online, which frequently displays tutorials, feature announcements, and walkthroughs.

While this can sometimes feel excessive, it does highlight the opposite problem:

Codex offers almost no onboarding at all.

The result is a tool that feels powerful but also somewhat opaque.

AI Tools Right Now Feel Like Early Crypto

This situation is reminiscent of the early Web3 and cryptocurrency boom.

At that time, there was enormous hype around blockchain technology, but the user experience outside of centralized exchanges was often confusing and risky.

For example:

  • Sending crypto to the wrong address could permanently lose funds
  • Wallet setups were confusing for newcomers
  • Many tools assumed a high level of technical knowledge

In many ways, today's AI tooling ecosystem feels similar.

The capabilities are impressive, but the UX maturity isn't always there yet.

Is This Just a Gen 1 Problem?

One possibility is that this is simply a first-generation problem.

AI capabilities are evolving so quickly that developers are prioritizing:

  • new features
  • new models
  • new capabilities

UX refinement may simply be lagging behind the technology.

But if AI is truly meant to democratize development, eventually these tools will need:

  • clearer onboarding
  • safer experimentation environments
  • better explanations of what's happening under the hood


How to support the show

Patreon

Prices subject to change and are listed in USD

  • Support the show from as little as ~$1/month
  • Get a shoutout at the end of the episode (while supplies last) for just ~$3/month
  • Help support the HTML All The Things Podcast: Click Here

Scrimba Discount - Coding Courses!

Learn to code using Scrimba with their interactive follow-along code editor.

Join their exclusive discord communities and network to find your first job!

Use our affiliate link for a 20% discount!!

  • Click the link to take you to the Scrimba site
  • A pop-up should appear on your screen with the discount amount and instructions on how to claim it
  • Discount is for new accounts only

We receive a monetary kickback if you use our affiliate link and make a purchase.