- AI Business Insights
- Posts
- The AI that opens your files
The AI that opens your files
Stop chatting with AI, start delegating
In partnership with
I sat through a full walkthrough of ChatGPT Codex this week, and one line kept echoing. Most AI apps just chat back at you. You type, they type, and you're still the one doing the real work. Codex flips that. It runs on your own computer and produces the finished files for you.
The person doing the walkthrough set out to prove something simple. You don't need to know a single line of code to get huge value out of it. Yes, it has "code" in the name, and yes, it started life as a coding tool. But it now handles everyday knowledge work too. Spreadsheets, file cleanup, PDFs, inbox research, even building a website. That's the part most people are sleeping on.
The ones showing up in LLMs convert 3× better than Google
They optimized for LLMs, not just Google.
FAQs. Comparison pages. Transparent pricing. LinkedIn presence. These aren't vanity plays. They're what gets you cited in ChatGPT, Gemini, and Claude when your buyers are researching, your investors are looking, and your future hires are deciding where to work.
Download the free AEO Playbook for Startups from HubSpot and get the exact checklist. Five minutes to read.
*Ad
The old way vs the new way
Here's the contrast that stuck with me. The old way of using AI is copy-paste ping pong. You paste data into a chatbot, it spits text back, and then you manually rebuild the file yourself. Codex skips that middle step entirely. It works inside the folders on your computer and creates the real files for you.
A few things make it different from a normal chatbot:
It works locally, inside project folders you choose.
It connects to the apps you already use, like Gmail, Calendar, and Google Drive.
It can take over your screen and click around inside other apps.
It does knowledge work and coding in the same chat.
So instead of being a smart talker, it acts more like a smart assistant who actually opens the files and gets things done.
Set it up so it can't hurt you
The walkthrough spent real time on doing this the right way, and I appreciated how much control he stressed. You are handing an AI agent the keys to your files, so the setup matters more than the demo.
Download the Codex app separately. It isn't baked into the regular ChatGPT web app yet.
Use Projects. Each project is its own folder, so your work stays isolated and organized instead of cross-contaminating.
Pick your permission level. On the safer setting, Codex always asks before touching outside files or the internet. Beginners should stay far away from full unrestricted access.
Mind the credits. It's free to start but usage-based. Higher reasoning and faster speeds burn credits quicker, so high reasoning with standard speed is the sweet spot for most tasks.
That permission piece is the whole heart of it. Write clear, specific prompts, and only open up the access you're actually comfortable with.
Say user_id. Get user_id.
Wispr Flow recognizes variable names, file references, and framework syntax mid-dictation. Speak your prompt, get developer-ready text for GitHub, Jira, or your editor. No mangled syntax. Ever.
*Ad
The five tasks that sold me
This is where it got fun. Real tasks, not toy demos:
Receipts to dashboard. He dropped a pile of receipt images into a folder and asked Codex to pull vendor, date, total, and category, then build an Excel dashboard. It finished in about two minutes and even saved a PNG version nobody asked for.
PDF invoices to spreadsheet. Same trick, pulling invoice numbers and dates out of PDFs into one clean sheet.
Messy folder cleanup. He pointed it at a chaotic downloads folder and asked it to figure out which client each file belonged to, rename everything clearly, and sort it into a tidy structure. It kept every file and reorganized the whole thing.
Inbox research. With the Gmail plugin connected, he asked it to scan for sponsorship emails and drop them into a table, right inside the chat.
Image generation. He had it create product photos, save them straight to a folder, then build on them with follow-ups.
None of those need a developer. They're the exact chores most of us avoid on a Friday afternoon.
Plugins, skills, and memory
Three features take Codex from handy to genuinely powerful.
Plugins connect it to your real apps. Gmail, Drive, Chrome, Calendar, plus a "computer use" mode that controls your actual screen. You grant access one app at a time.
Skills are reusable recipes. Think saved instruction sets, like a detailed template for building a PowerPoint. The best tip here: don't write them by hand. Chat back and forth until you love the output, then just say "save that as a skill."
Memory means you stop repeating yourself. There's an agents.md file that works like an onboarding doc for a new assistant. You tell it who you are and how you like things done, and it reads that first on every new chat.
He was honest about the rough edges too. Computer use, where Codex drives your mouse through apps like Canva, is impressive but slow and credit-heavy. He called it the future, just not quite ready yet. There's also a daily morning brief that checks your calendar and unread email while you sleep, and one-prompt website building. He spun up a clean video production site from a single prompt.
One AI employee. Engineering, finance, growth, ops.
Last week Viktor opened 14 pull requests, closed two month-end books, drafted a board update, deployed three landing pages, and triaged 600 support tickets. From inside Slack and Microsoft Teams. 20,000+ teams now run this way.
*Ad
Start without torching your credits
If you want to try it the way he does, here's the simple path:
Install the Codex app and create your first project from scratch.
Keep permissions on the safer "ask me" setting.
Drop your files into the project folder.
Write a clear, specific prompt about exactly what you want and where to look.
Build an agents.md file so it remembers your preferences.
That's the whole on-ramp. The depth comes later, once you trust it with bigger jobs.
Where my head landed
The thing I can't shake is the shift in posture. For two years the deal with AI has been: it drafts, you assemble. You were always the one moving the output from the chat window into the actual file. Codex quietly deletes that step, and once you feel it, the old way starts to feel like typing with one hand tied behind your back.
It isn't perfect. The screen-control stuff is slow, the credits add up, and you have to be deliberate about permissions. But the direction is unmistakable. The assistant is starting to do the assisting.
Tonight, install it and hand it one real chore. Point it at a messy folder, or a stack of receipts, and watch what comes back. That first finished file lands differently when you didn't have to build it yourself.