What Changed When a Non-Programmer Started Using Codex: An AI That Can Touch Local Files

January 23, 2026Updated: July 25, 2026Articles

I started using Codex at the end of 2025. Precisely because I am not a programmer and was not comfortable in a terminal, the sense of reaching work I had written off as beyond me was strong.

This article reworks impressions written just after adoption and published on 22 January 2026, presented as a record dated 23 January 2026. Back then it was terminal-centered; today both where you can use Codex and how it is priced have changed.

The terminal became less frightening

A terminal looks like a place where the wrong command breaks something. Codex explains what it is about to run and asks permission where needed, which makes it much easier to follow what is happening.

That said, a command an AI proposes is not automatically safe. For anything involving deletion or overwriting, check which files are affected and how you would restore them before granting permission.

It can look at how several files relate to each other

Previously I copied code into ChatGPT and got suggested fixes back. That works for a single file, but on a site where files call each other, explaining the situation becomes hard.

Give Codex the working folder and it finds the related files, checks how far a change reaches, and then edits. Asking for an explanation of why it is touching a particular file, not just the finished code, makes it a learning exercise too.

Set up a way to undo things first

If an AI is going to touch files directly, keeping a change history with something like Git matters. Being able to see the difference before and after makes unexpected changes easy to spot and easy to roll back.

Small jobs are a good place to start.

Change some wording in one place
Find the files that contain the same passage
Make no changes; just investigate the cause
List the changes currently outstanding

I picked up the habit of keeping work logs

Early on I worried about forgetting how the work had gone once I closed the chat or the terminal. So at each stopping point I began asking for “what I did today, which files changed, and what comes next, in Markdown.”

As those logs accumulate they become the material for briefing the next AI. Rather than relying on the AI’s memory, keep the history in files you control.

Codex as of 20 July 2026

Codex today is available not only as a CLI but through a desktop app, IDE extensions, and the cloud. Using it with a ChatGPT account and using it with an API key differ in available features and in how the cost works.

Since April 2026, Codex usage on most ChatGPT plans has moved to a token-based credit system. The feeling described in the original article — that you can experiment freely within a Plus plan — largely remains, but actual consumption has to be checked against your current plan screen and the official rate card.

In summary

The biggest change from Codex was not that I became able to write code. It was that work which used to stop at “I do not understand it, so I will not touch it” became something I could try with an explanation alongside.

The less of a programmer you are, the more useful it is to start with small, reversible jobs rather than building a large application straight away.