What is up people!
You know where you want the picture to go. You can see the empty space for the headline. Then you open an AI chat and spend five minutes trying to describe a layout you could draw in ten seconds.
By the third correction, the prompt has become a small essay. “A little further left” now refers to something that moved two versions ago, and the part you liked has somehow changed too. You started with a simple idea and ended up explaining your explanations.
This week’s AI releases offer a reason to reconsider that habit. OpenAI updated image creation, voice, and access to source files. None of these updates invented the idea of showing or telling a computer what you want, but together they invite a useful question: which part of this request is getting lost when you turn it into typed instructions?
Sometimes a drawing preserves the relationship between things. Sometimes talking helps you discover a constraint you hadn’t thought to include. Sometimes the answer is already in a document, and your summary leaves out the detail that matters.
The opportunity is to spend less effort translating what you know, while staying precise about what AI should do with it.
⚡ TL;DR
A rough sketch can communicate a layout before you have the words for it. Use written instructions for the details the drawing cannot settle.
Voice can help you work through an unfinished thought. Confirm the resulting decisions in writing, especially names, numbers, and dates.
Give AI the actual source when you want an explanation grounded in records. A connected file still needs a clear question and the right interpretation.
Try a second input method on one small task this week. Keep it only if it reduces the total work, including corrections.
A rough sketch can carry what a paragraph loses
Imagine you’re making a poster for a neighborhood plant swap. You want a large plant on the right, the event name on the left, and a quiet strip along the bottom for the time and location. You have a clear arrangement in mind, even if you couldn’t name a single design principle behind it.
A drawing with three rough shapes can express that arrangement. It doesn’t have to resemble a finished poster. Its job is to show which element occupies which space, how large the main object should feel, and where nothing should compete for attention.
OpenAI’s September 8 ChatGPT Images 2.5 announcement claims improvements in following visual references, making focused edits, and maintaining consistency across revisions. Those are vendor claims, rather than results from a test for this issue. They matter here because a reference loses much of its value if the system keeps wandering away from it.
The practical starting point is more modest than asking for a perfect design. Give the system your arrangement and ask it to develop the visual treatment around that arrangement. A useful instruction for the imaginary poster might be: “Use this sketch for placement. Keep the plant on the right and leave the bottom strip clear. Make the illustration warm and simple.”
That separates two decisions you might otherwise blur together. You have chosen the layout, while the system has room to suggest the finish. If the result feels wrong, you can identify whether it ignored your arrangement or made a stylistic choice you dislike.
There’s now a built-in Sketch option in the ChatGPT mobile app. Type @ in the message box, choose Sketch, draw, confirm it, and add written instructions before sending. Image creation is available across tiers, although particular features and allowances differ.
Drawing also has limits. An empty rectangle could mean “put the headline here,” “leave this empty,” or “this is a separate panel.” Label the few parts whose meaning could be mistaken, then explain what the model may change. The drawing communicates relationships; the accompanying words remove ambiguity.
For our poster, the event name, date, and venue still deserve exact written instructions and a careful check in the finished image. A beautiful plant cannot rescue the wrong address. If you’re still deciding the date, leave that area empty instead of letting a plausible date become part of the design by accident.
The same principle applies when revising an image. Point to the part you mean and say what should change, but inspect the rest afterward. OpenAI’s image documentation warns that an edit can extend beyond the selected area, so a local request is no guarantee of a local result.
This is useful when you keep correcting position, proportion, or empty space. If all you need is a plain sentence on a plain background, typing may already be the simplest route. The reason to draw is that the task contains a relationship that your paragraph is struggling to carry.
A conversation can uncover the request you haven’t formed yet
Now imagine you’re organizing the plant swap itself. You ask for an event plan, but halfway through explaining it you remember that several attendees will be beginners. Then you realize that helping them choose a suitable plant matters more than fitting in as many activities as possible.
You could type all of that. But if the useful details tend to emerge while you talk, a conversation gives you somewhere to work them out. You can reconsider an idea, respond to a question, and hear whether the explanation makes sense before turning it into a brief.
The September 9 ChatGPT Voice update adds GPT-5.6 or GPT-6 Astra for searching and harder reasoning, with availability depending on your plan. Separately, OpenAI’s September 10 GPT-Live-1 API announcement describes a voice system that can listen and speak simultaneously. That second announcement is aimed at developers building products, so it shouldn’t be read as a promise that every feature is present in every ChatGPT voice conversation.
For an ordinary planning session, the useful move is to ask for questions before a plan. You might say: “I’m working out a beginner-friendly plant swap. Help me identify what I haven’t decided. Ask one question at a time, and don’t turn a possibility into a commitment.”
Suppose the conversation brings up a plant-care table. You mention that a friend might staff it, then spend several minutes exploring how it could work. By the end, it may feel settled simply because you’ve talked about it in detail, even though your friend hasn’t agreed.
That’s where a written closing step earns its place. Ask for a short account of what you decided, what remains tentative, and what needs a fact checked. Read it yourself and correct any upgrade from “could” to “will” before using it to organize the event.
There are also two different voice jobs worth separating. The Voice guide distinguishes conversation from Dictation, which produces text you can edit before sending. If you know what you want to say and just dislike typing on a phone, Dictation may be enough.
For important details, the editable text is valuable. You can inspect the spelling of a person’s name or replace “next Saturday” with the exact date. The same guide says Voice transcripts aren’t verbatim records, so don’t treat a fluent conversation as a perfect set of minutes.
One limitation matters if you plan to combine this with the next section: Live currently cannot find or add files from Library, and it does not initially support connected apps or plugins. Use voice to explore the problem, then move to a supported file-based chat to check the records. Those are separate capabilities, even when they appear inside the same product.
You haven’t gained anything if you spend twenty minutes talking around a question that takes one sentence to ask. Voice earns its time when the conversation helps you notice something that belongs in the request. Once the request is clear, you can stop exploring and use it.
Give AI the source before asking for the explanation
A week before the event, you want to know whether registrations are low. You tell AI, “Only twelve people have signed up. How can I improve attendance?” It can now suggest better promotion, more reminders, or a different message, all while knowing almost nothing about whether twelve is a problem.
Perhaps the room holds fifteen people. Perhaps last year’s event also had twelve registrations at this point and finished full. Or perhaps this year’s sheet counts households while last year’s counts individual attendees. Your short summary can be accurate and still leave out the comparison needed to answer your question.
Source files give the system a chance to inspect those details. In its September 10 release notes, OpenAI says Box, Dropbox, and SharePoint are joining Google Drive in ChatGPT Library. Eligible web accounts can browse connected material and add selected files or folders to a conversation, with source citations and existing permissions applying. Mobile support is due later.
For the hypothetical event, you could select this year’s registration sheet and last year’s record. Then ask the system to compare registrations at the same number of days before each event, identify what each row represents, and show the entries behind its answer. That is a more answerable question than asking why attendance is bad before establishing whether it is.
The distinction between a count and an explanation matters. A sheet might show fewer registrations without showing why they fell. If it contains no evidence about promotion, weather, or competing events, the system should present those as possibilities to investigate, rather than explanations discovered in the records.
You can make that boundary explicit: “Use these files to establish what changed. Tell me which comparisons are valid and which information is missing. Keep possible causes separate from findings supported by the files.” This gives the analysis a useful stopping point when the documents cannot answer the whole question.
For people working with larger organizational datasets, OpenAI also introduced the Data plugin for ChatGPT Work and Codex this week. It’s intended to connect business questions to data and relevant context. Its setup documentation makes clear that Data and the appropriate sources need to be installed or connected, with authorization where required.
That is a different starting point from attaching two sheets for a small event. A workplace may already have agreed definitions for customers, completed orders, or revenue. Those definitions belong in the analysis because a correct calculation of the wrong thing can produce a convincing but useless answer.
You don’t need to connect a whole folder to benefit from source-based work. Start with the smallest set of relevant files you’re allowed to use. Open the cited source for a consequential finding and check that it actually supports the claim, including its date and the conditions around it.
A source link makes that check possible; it doesn’t perform the check for you. The gain is that you can return to the evidence instead of arguing with a summary built from your own incomplete recollection.
🛠️ Suggested how-to: compare two ways of asking
Here’s a small experiment based on the documentation above. It hasn’t been run as a comparative test for this issue, and it doesn’t require you to change your whole workflow. Choose a low-stakes task where you already know enough to judge the answer.
Try your usual route first. Make a small poster concept, work through an event decision, or compare two simple records. Keep the request and note roughly how long you spend explaining and correcting it.
Change the input on a second attempt. Use a rough sketch for the layout, a short conversation for the undecided problem, or the actual files for the comparison. Keep the desired result the same so you can tell whether the input helped.
Check the details that matter. Did the layout survive? Did a tentative idea become a commitment? Did the comparison use the same dates and units? Count those corrections as part of the work.
Keep the route that costs you less effort overall. Include drawing, talking, finding files, reviewing, and fixing. A faster first answer can still leave you with more work at the end.
One attempt won’t establish which method is generally best. It can tell you whether a particular recurring frustration has an easier route. If the sketch takes longer than the explanation, or the conversation sends you into more indecision, you have a useful reason to keep typing for that task.
🧰 Tools to try
ChatGPT Sketch: Start here if you know how something should be arranged but keep struggling to describe its position. The mobile instructions are the quickest way into that experiment.
ChatGPT Dictation: Choose this when the request is already formed and you want to review the words before sending them. The Voice guide explains the distinction from live conversation.
Data in Work or Codex: Consider this if your workplace already has a supported, authorized data source and a real question for it. Read the setup requirements before assuming it’s ready to use.
For your next request, notice what takes the most effort to communicate. If it’s the arrangement, draw it. If it’s the thought you’re still forming, talk it through. If it’s what happened, bring the records. Then use exact words for the details you need AI to preserve.
P.S. An AI wrote these sentences from this week’s primary sources. Payton set the editorial standards and what good looks like. He wants to be transparent when AI wrote the issue.