My ChatGPT Workflow: When I Use Phone, Voice, Web, and Mac Apps

I use ChatGPT differently on my phone, in the browser, and on my Mac. Here’s the workflow I’ve settled on for voice, research, projects, files, and serious work.

Get the next practical AI marketing episode wherever you listen.

ChatGPT stopped feeling like a single app a while ago. I now think of it as a small suite of tools: a phone app for thinking on the move, a web app for everyday work, and a Mac app with Codex for heavier projects.

That distinction matters because I don’t want to use the most expensive or powerful mode for every small question. I want to get the most from my subscription without spending unnecessary credits—or making simple work harder than it needs to be.

My basic rule is simple: use ChatGPT for conversation, planning, and lightweight work; use Codex when I need the system to take on a substantial project.

My ChatGPT workflow at a glance

  • iPhone app: quick questions, curiosity, dictation, and voice conversations while walking or driving.
  • Web app: brainstorming, lightweight research, project context, file management, and everyday tasks.
  • Work or deeper research modes: larger research assignments when I’m away from my computer.
  • Mac app and Codex: repeatable processes, files, building, coding, and serious multi-step work.

The goal isn’t to find one “best” ChatGPT feature. It’s to match the tool to the kind of thinking or work I’m doing.

I use the iPhone app as a thinking partner

The iPhone app is probably the ChatGPT tool I use most often. Not because it’s the most powerful, but because it’s always available.

I’m increasingly scrolling less when I have a spare minute. If I’m curious about something, I’ll ask ChatGPT. I might want to understand an idea from a podcast, investigate how something works, or explore a question that would otherwise disappear before I get home.

That makes the phone app useful for more than productivity in the traditional sense. It gives me a place to follow curiosity while it’s still alive.

Voice is especially useful when my hands are occupied

The voice feature is where the phone app becomes much more useful than a regular text box. While driving, walking, or running, I can talk through an idea without trying to type on a tiny keyboard.

Sometimes I’ll ask Siri to open ChatGPT voice mode, then start with something simple: “I’ve been thinking about this idea. Help me work through it.” From there, ChatGPT can ask questions, reflect the idea back to me, point out gaps, or help me take it one step further.

I’m not naturally a verbal processor. I usually think best with pen and paper or by sitting down and working through an idea in text. But voice has helped me capture thoughts that would otherwise vanish because I didn’t have my hands free.

The useful part is that the conversation is saved. Later, I can return to it, ask for a summary, or pull out the strongest ideas. A commute or a walk can become a surprisingly productive thinking session without turning into a frantic note-taking exercise.

If you tend to process ideas out loud, this may be even more valuable. But even if you don’t, it’s worth testing. You may discover that speaking an unfinished thought is enough to give it shape.

The web app is where I do lightweight work

The web app is my general-purpose workspace. I use it for brainstorming, outlining, asking questions, and doing lighter research before deciding whether a task deserves more serious processing.

This is also where I try to conserve my higher-cost work. I don’t need an intensive agent to help me brainstorm five possible angles for an article. I don’t need it to spend a long time reasoning through a simple planning question. I can use regular chat to get the thinking started.

That’s especially useful because the different ChatGPT modes can draw from different usage allowances. More autonomous work can consume substantially more credits when it runs for a long time, uses tools, or delegates work to other agents.

So I use a two-stage process:

  1. Frame the problem in regular chat. Clarify the goal, explore options, and create a rough plan.
  2. Escalate only when necessary. Move the defined task into a deeper research or Codex workflow when it requires sustained effort or action.

This approach also improves the work itself. I’m not asking an agent to wander around trying to understand a vague request. I’ve already done enough thinking to give it a clear outcome.

For more on organizing ongoing work, I’ve written about using ChatGPT Projects to organize AI work. Projects are becoming a more useful replacement for keeping every task in an isolated conversation.

Projects are replacing my old custom GPT workflow

I used to rely much more heavily on custom GPTs. I still have some old ones, but I’ve moved most of my repeatable workflows into projects and Codex.

Projects make more sense for the way I work now because they keep related conversations, instructions, and files together. I have different projects for businesses, side projects, hobbies, and different areas of my life.

That separation matters. When I open a project, ChatGPT has more relevant context and less irrelevant context. I don’t want everything I’ve ever discussed mixed together. I want the system to know which body of information applies to the task in front of me.

Files make projects much more useful

Projects have also become more valuable because I can save sources and files inside them. Some files are documents I uploaded. Others are documents ChatGPT created during earlier work.

For example, I might ask ChatGPT to research a subject and save the result as a document. Later, that document can become a source for a different conversation or project. I can move files, organize them, and reuse them instead of starting from scratch every time.

This has gradually changed how I think about ChatGPT. It’s not just a place to generate a response and move on. It’s becoming a lightweight information system for my work.

The Library feature helps with this by giving me a central view of uploaded files, images, folders, and connected sources such as Google Drive. I can find documents that would otherwise be buried in old conversations and bring them into a new task.

That sounds like a small interface improvement, but it changes the workflow. The value of AI increases when it can work with the information I’ve already created instead of forcing me to explain everything again.

Chat is becoming more proactive—but I still choose when to escalate

As ChatGPT’s context window and memory improve, regular chat can handle more than it used to. It can remember relevant past conversations, access project files, and sometimes identify useful context without me spelling out every detail.

That makes ordinary chat more capable and more “agentic.” It can edit documents, create files, and help manage project materials without requiring me to switch into a specialized work mode for every action.

Still, there’s a difference between helpful context and full autonomy. Regular chat is usually enough for ideation, simple planning, and lightweight tasks. I move to a deeper work mode when I want the system to pursue a larger goal, inspect many sources, or work through a multi-step process with less supervision.

If I’m on my phone and need serious research, I may switch into the deeper work area and ask for a thorough investigation. But I’m using that selectively. For many research questions, I can now simply describe the depth I need: “Do a deep dive. Find the strongest sources, compare the options, and compile the findings into a document.”

That natural-language instruction often gets me closer to the result I want than choosing a feature because its name sounds impressive.

Of course, there are still times when the dedicated deep research workflow is the right choice. The point is not to avoid it. The point is to understand when the extra depth is justified.

Codex is where I do substantial work

On my Mac, I almost never use the regular ChatGPT side of the app. I go straight to Codex.

Despite the name, I don’t think of Codex as a tool only for writing code. I think of it as my work mode. It can work with files and folders on my computer, follow documented processes, create things, edit things, and complete a much larger sequence of tasks than a normal chat conversation.

That distinction helped me understand its value. I had initially associated Codex with programming. Now I use it for many kinds of work, including content production, research, image creation, and repeatable operations.

Give Codex a process, not just a prompt

The most powerful setup I’ve built is a folder for my personal brand with documents that explain my recurring processes. For example, I have a process for starting a new piece of content.

When I say, “Let’s start a new episode,” Codex already knows the sequence. It can help develop angles, generate title options, explore image concepts, and create the related assets. I don’t have to explain the entire process every time because the process exists in the project files.

That’s a major difference from asking ChatGPT to perform a one-off task. Instead of only giving it instructions in the moment, I’m building a reusable operating system around the work.

The workflow is still collaborative. Codex moves through the steps, and I decide when to continue, adjust the direction, or reject an option. I’m not handing over judgment. I’m reducing the amount of repetitive coordination I have to do.

For a related example, see how I built a custom GPT to handle repeatable work. The tools have changed, but the underlying principle remains: document the process so the AI can help execute it consistently.

Keep project folders contained

Codex projects typically correspond to folders on my computer. Those folders hold the files, instructions, and assets associated with the work.

I like keeping projects contained because it gives the system a clear boundary. It can work with the relevant files without automatically having access to my entire computer.

I don’t recommend giving an AI unrestricted access to everything unless you understand the risks and have a dedicated environment for it. A well-organized folder is safer and usually more useful than a giant pile of unrelated files.

Inside a project folder, Codex can create files, update documents, and build on previous work. I don’t need to understand every line of code it changes to benefit from it—but I do need to review the results and remain responsible for what gets shipped.

How I decide which tool to use

When I’m unsure where to begin, I use this simple decision tree:

  1. Do I need to capture or explore a thought? Use the iPhone app, especially voice mode.
  2. Is this a small question, brainstorm, outline, or simple task? Use regular ChatGPT in the web app.
  3. Do I need substantial research while I’m away from my computer? Use the deeper work mode selectively and specify the outcome clearly.
  4. Does this involve files, a repeatable process, building, or multiple steps? Move to Codex on the Mac or Windows app.

I also try to separate thinking from execution. ChatGPT is excellent for helping me understand what I want to do. Codex is better when I know the goal and want the system to help carry out the work.

The practical takeaway

Don’t treat ChatGPT as one giant text box. Use the phone app when you need a thinking partner in the real world. Use the web app for lightweight work and project-based context. Save deeper research for tasks that genuinely need it. Then use Codex for substantial, repeatable work with files and processes.

The biggest productivity gain hasn’t come from finding a magical prompt. It has come from giving each interface a job.

Start with the least expensive tool that can handle the task. Build context in projects. Document the processes you repeat. Escalate to Codex when the work becomes multi-step or operational. That workflow gives AI room to create leverage while keeping my judgment, taste, and responsibility in the loop.