The July inventory

You came here from the email, so you know the shape of the month: July moved products under people. This page is the full inventory, the creator cost numbers, the open-model verdict, and all 21 moves written out.

Same deal as the email: I didn't run a new product test for this issue. Every date below is checked against the companies' own pages, and the user side comes from roughly 3,000 tagged Reddit, X and YouTube comments plus the Facebook and Instagram threads I read alongside them.

Where something is my read rather than a fact, I say so in the sentence.

July 9. OpenAI launched the GPT-5.6 family and ChatGPT Work, and replaced the desktop app with a new client that has 3 modes: Chat, Work and Codex. The old desktop app stayed installed on many machines under a new name, ChatGPT Classic.

That last part is what July felt like for a lot of people. The loudest thread I found was r/ChatGPT's "DO NOT UPDATE" post, 274 upvotes and 292 comments, most of them people hunting for chats and Projects that were still on their machine the whole time.

The rescue path spread reader to reader, not from OpenAI:

If you're on the new app and can't find something: your history is still on chatgpt.com, and Classic may still be installed. Search your machine before you rebuild anything.

ChatGPT Work itself. OpenAI's pitch is an agent that can "take action across your apps and files" and "turn a goal into finished work." That's the company's claim, from its own launch post. One thing OpenAI also says: Work has its own usage accounting, and long tasks consume more of your plan's allowance. If you're on Plus, that's the line to remember before you hand it a big job.

The most repeated user question wasn't about capability. From the X replies I audited, it was about recovery:

She asked it in one line: if it deletes my project folder, "is there an undo or do i just cry." The products still don't have a clean answer. Section 2 of the checklist is my answer in the meantime.

One date ahead: the standalone Atlas browser shuts down August 9. Move your bookmarks and saved logins before then.

Claude's July was a stack of changes, so here they are in order.

June 30. Sonnet 5 launched and became the default on Free and Pro. Your everyday chats upgraded on their own.

July 1. Fable 5 access came back after the June export-control pause, with a promo window letting Pro and Max spend up to 50% of weekly limits on it.

July 7. Cowork went to web and mobile, with cloud sessions that keep running when your laptop is closed.

July 8. The Cowork tab got folded into Projects. The highest-intensity Claude thread of my whole sample was a r/ClaudeAI business user discovering this by opening the app: 281 upvotes, 171 comments, and a line I'd frame: "If you're going to let people build real workflows on your product, tell them before you move the furniture."

His folders weren't deleted. They'd moved into the regular Projects screen, mixed in with everything else. If yours look gone, that's where they are.

July 20. The money change. Fable 5 stopped counting against Pro plan usage and moved to pay-per-use credits. Anthropic's own announcement: Max and Team Premium keep Fable inside 50% of limits, Pro continues via usage credits with a one-time $100 credit.

My read on what to do, and it's a read: don't upgrade to Max just to keep Fable. Price the work you'd actually give it against the credits, and remember Sonnet 5 covers most days. The full routing logic is in The model map, published July 21, and I'm not reprinting it here.

July 24. Opus 5 launched as the strongest model on Pro and the new default on Max. It uses more of your allowance per message, so treat it as a deliberate pick for the jobs that earn it.

July 9 and 10. Smaller but nice: memory got itemized entries and a monthly recap under Settings, with break reminders and quiet hours.

July 20 and 21. Google released Gemini 3.6 Flash plus 3.5 Flash-Lite and Flash Cyber, all developer-side API models. The delayed 3.5 Pro flagship stayed in partner testing, with Google saying "coming soon" and giving no date.

So the app in your pocket barely changed in July. If you're a Gemini user, the practical note is that there's nothing to switch, learn or fix this month. If you build with the API, 3.6 Flash is the cheaper workhorse to test.

Copilot had a quiet July in every dataset I read, and I'd rather tell you that than invent a section. The change that matters is control: Teams meeting organizers can now turn off Copilot, Facilitator and Intelligent Recap per meeting, and the July Windows 11 update lets you remap the Copilot key.

Also a quiet month in the user research. The one real change: Grok 4.5 became xAI's frontier model mid-July, priced at $2 per million input tokens and $6 per million output on the API, flowing into Grok-powered tools without a new subscription tier. If your quotas moved earlier in the summer, that story and the routing fix are in The model map.

July's changes were under the hood: the July changelog upgraded Computer and added the new frontier models to the Agent API on July 27. If you pay for Perplexity, nothing about your plan or interface changed this month.

This is the part I most want to get right, because the internet merges 2 different stories into 1.

Story 1, stated fear. Across the 1,135 X replies audited under ChatGPT Work and Claude Cowork posts, the recovery question came up over and over: rollback, undo, permissions, version control. Sophia's undo question above is one version. Sebastian Buzdugan's is another: Work "will hit permissions before model quality, who owns rollback after actions." Both are single voices with tiny engagement, and I'm quoting them as exactly that, 2 people asking the right question early.

In that whole X audit, the count of confirmed cases of these agents destroying someone's files was zero. Fear, yes. Verified damage, no.

Story 2, observed damage. The Facebook and Instagram sets were different. An Instagram caption in my sample described a Cowork run that erased a folder holding 15 years of family photos, bypassing the Trash, on a machine with no backups. A Facebook commenter described a confirm-before-deleting setting that saved a client file after a badly written prompt the week before.

I can't independently verify either story, and I'm not treating captions as proof. But the pattern across Meta platforms was consistent: the damage reports live where the least technical users live, and every workaround people shared was some version of a human undo button. One fenced folder. A copy before big jobs. A review-before-delete folder. Confirm before overwriting.

Which is exactly what section 2 of the checklist builds.

And the wins are real too. The same X audit that found zero confirmed damage found real finished work: one user had Work migrate his entire newsletter between platforms in one shot. The tool is capable. The recovery story is what's missing. Hold both.

Most comment volume of any lane this month, and the most real money.

The headline. Neill Blomkamp released Nightborne, a 13-minute sci-fi short with every shot generated in Seedance 2.0. His own post drew 3,580 likes and 2,307 replies, and the replies split hard: craft admiration on one side, "stilted uncanny performances" and "this is not art" on the other. Whatever side you're on, a director shipping 13 minutes this way is why your feed was full of Seedance in July.

The unit economics. Creator JSFILMZ priced it plainly: Seedance 2.5 charged 660 credits for 30 seconds at 720p, which he put at roughly $5. The complaints in my comment sets were about what iteration does to that number: reroll a shot 10 times chasing a hand or a face, and your $5 shot is a $50 shot.

What the working creators do differently. The patterns repeated across the X workflow threads:

One reference image, locked. "one reference locks the character so the face stays consistent across every shot", from Nexlow's music-video workflow.

Storyboard before generating. Nexlow's 12-panel colour-coded board and Higgsfield's story-to-sheets-to-storyboard pipeline both build the board first and generate second. The creators who described burning credits were generating and reacting.

Count your generations. This LinkedIn post is 2 months old and it's a partnership announcement, so weigh it accordingly, but it's the cleanest public number I found for the reference-sheet workflow: about 50 generations and about $10 for a full project's shots.

The named limits. Seedance struggles with fights in confined spaces, storyboard instructions get dropped or altered, and camera moves sometimes fail as generated. The creators shipping real work say so out loud. That's how you know they're shipping real work.

Moves 18 to 21 in the checklist are this section compressed: spend ceiling, locked reference, storyboard first, human check on anything with product truth in it.

The dates first. Zhipu's GLM-5.2 went open weight under MIT on June 15. Moonshot unveiled Kimi K3 on July 17, paused new paid signups July 20 after demand spiked, then published the full weights July 27, the largest open-weight model ever released.

Now the part the headlines skip. "Open weights" reads like "free model on your laptop." Here's what serving K3 actually took one infrastructure team:

80 RTX 5090s, and the replies under Kimi's own weights announcement were people asking whether an RTX 4050 could run it. It can't. Almost no one outside infrastructure teams runs these locally, and across my Reddit and YouTube sets the people who tried described hardware costs most of us would never spend.

So here's the verdict, and this part is my read built on those comment sets: if you're curious, use the web apps. Kimi, Z.ai, DeepSeek are free to try with a sign-in, and they're a real overflow lane for the Thursday your paid plan runs out. Two limits come with that. The privacy concern in the threads is real and constant, so keep client data and anything sensitive on the tools you already trust. And quality wobbles more than the benchmarks suggest, so treat them as a second opinion while your trusted tools stay the system of record.

If you're already routing models by task, the interesting July development is K3 and GLM appearing on hosted providers, which is how the price pressure reaches you: through cheaper hosts.

One more thing from the agent research, because the internet is loud about it. The X threads I went through turned up zero confirmed cases of ChatGPT Work or Claude Cowork wiping someone's files.

On Facebook and Instagram, people did. A post described 15 years of family photos erased, and a commenter described a client file saved only by a confirm-first setting. Stated fear and real damage are different sizes, and I'm keeping them separate.

So I turned July into 21 moves: portable instructions, a fenced folder for any agent, an overflow tool, a spend ceiling for creators. The moves are mine. I ran all 21 before this went out.

If you do nothing else on this page, do these 3:

Tell me in the comments which July change cost you the most, and whether you'd already made any of the 21 moves before it hit. I read all of them.

Dan Rice · AI Signal Read once. Use AI better all week.

Company pages and documentation

Tech media

Reddit

X

AI Signal