Intelligence everywhere. It continues.

Xbox just built a team to disrupt itself. Fans have been using AI to rebuild old games for new hardware, including Xbox's own. Yesterday CEO Asha Sharma announced Xbox Labs, a small team that will "build in the open," and wrote that its experiments are good for players "even when (and sometimes because) they challenge our existing business models." It's bigger than it looks. What it means for product teams: 1. Your customers are already rebuilding your product with AI. A lab is how your own team gets there first. 2. Point it at what could replace you. Every time a new model ships, ask what you'd build if you were starting today. 3. Keep it off the main roadmap, with a direct line to the product team. It moves faster on its own, and what works still reaches customers. 4. Start with the technology. Ask what the new capability makes possible, then find the customer problem it solves. 5. Kill things on purpose. Set the bar for keep, kill or iterate before the first experiment starts. Here's how to understand it in four steps:

Every company should be operating an internal AI lab. If you're not building on new AI surfaces as they're released, someone else is, and you're falling behind. ChatGPT extensions were announced on a Tuesday. By Friday we had working prototypes for 10 leading brands. LCA concept. Not affiliated with Disney or OpenAI.

Having a website didn't make you a tech company. Having Claude write your docs won't make you AI-native. Last week Anthropic took Claude Docs, Slides and Design out of beta and put them on every plan, including Free. Claude drafts from your company's files and apps, and your team edits right alongside it. People made 45 million docs, decks and designs during the beta, and on October 15 it switches on by default for Claude Enterprise. It's still bigger than it looks. What it means for building an AI-native company: 1. Everyone is a manager now. A comment that tags @ Claude hands off the work, and the reasoning comes back in the thread. 2. Your company's context is the brief. Claude can only draft from what's written down somewhere it can reach. A company that never wrote down how it works gets generic drafts. 3. The ask is the new skill. "A launch brief" gets you a template. Say what it's for, who reads it and what it should cover, and you get a draft worth editing. 4. Your permissions are your agent policy. Claude can't do anything the person who asked can't, so your access settings now decide what each person's Claude can do. 5. Templates set the standard. Admins now pick the templates everyone starts from, so your best spec or brief becomes the starting point for every one after it. 6. Six hours back doesn't mean six times more docs. Making one takes a sentence now. Deciding which ones matter is still the job. Here's how to understand it in four steps:

Meta and Sierra just announced "Sign in with Google" for AI agents. It's called the Personal Agent Protocol. Your customer's agent signs in to your business and gets things done for them, and you decide what it's allowed to do. Shopify, Stripe and Walmart are already in, and Muse alone has millions of US users. It's bigger than it looks. What it means for brands: 1. The agent is a customer who already chose you. Turn it away and you turn away the customer behind it. 2. Build once, reach every agent. One standard instead of a new integration for each one. 3. You get a second front end. Agents follow the path you give them: this flow for bookings, that connector for orders. 4. Agent-first is a ladder: agents clicking through your site, then your APIs, then your own agent talking to theirs. 5. Permissions become product design. What an agent can see, do with a yes, and never touch. 6. Brand becomes behavior. When an agent does the job, speed and accuracy are the experience. Here's how to understand it in four steps:

If we were on Suno's design team, we'd be obsessing over the second song. Elon says Grok will use backends including Suno and Midjourney. Picture asking Grok for music for your launch video, getting a track you love, and coming back to Grok next week. You've learned that Grok can get you good music. You may not have learned anything about Suno. So the work is turning that first track into a project worth keeping: the versions you tried, the cut you approved, the style you want to use again. Plus a link your editor can open to listen and choose, with no downloading three files and explaining everything again. Next time, "make another like this" has a saved project to point to, whether you come back to Suno directly or through your agent. The numbers worth watching: does that creator start a second project, and does their editor stick around? Those two show whether the integration is turning requests into customers.

If you're building a ChatGPT plugin, today's Intelligent UI launch changes the job. ChatGPT can now add charts, forms and small interactive tools to its answers, built on the spot for each question. So generic help, like comparing options or running a quick calculation, now comes built in. A plugin earns its place when it uses what only your product has. Example: someone asks which running shoes to buy. ChatGPT on its own can show a comparison chart of popular models. A shoe store's plugin can show which ones are in stock in their size, what they bought last time, and let them order. So when you plan a plugin, start with one question: what can we show or do that ChatGPT can't build on its own?

The next breakout consumer products will be deeply integrated into your personal agent. Our team is laser focused on designing world class product experiences for this reality. ChatGPT has 1.2 billion weekly users. Extensions give you new places to build your product inside it. Take a travel app... Rich forms: Ask whether the budget includes flights. Conversation panels: Let people browse hotels while they keep chatting. Model-App Context: Let the conversation work with the hotel they selected. Deep links: Bring them straight back to their saved trip. I'd happily let an agent compare cancellation policies. I still want to look at the hotel photos. Figuring out which parts to hand over, which choices to keep, and where each interaction belongs is the new design brief. These are the surfaces we're designing for:

Plugin Extensions open up new surfaces for you to define the experience inside of ChatGPT Here are the 9 new 'extensions' you should be paying attending to: 1. Sidebar apps: Your app gets a home base in ChatGPT. People can come back to it any time without starting a new chat. 2. Conversation panels: Your app and the chat sit side by side. Design for both being on screen at once. 3. Plugin settings: Users tweak your product without ever leaving ChatGPT. Your settings page now lives inside someone else's app. 4. File viewers and editors: Your interface opens their files right in ChatGPT. Read, edit and save in one place. 5. Display modes: You choose how much space you take up. Match the size to the job. 6. Deep links: Send people straight to the exact page or item they need. No digging through menus. 7. Model-App Context: The model sees what's happening in your app, and your app knows what was said in chat. Both stay in sync. 8. Composer mentions: Users can @ your content right into a prompt on desktop. Your data becomes something people type. 9. Rich forms: Ask for structured input or let people pick from images. Less guessing, fewer back-and-forths. Apps in ChatGPT are starting to look like real software. Time to design them that way.

ChatGPT plugins are AI's "app store" moment for brands.

An evolution of Garrett's elements of UX to AX (for the AI Age)

If you're not building custom animation playgrounds, you're doing it wrong. Chat is good for many things, but for fine-tuning an animation exactly how you want it to appear in product, UI is better.

Vibe printing?

My team at latecheckout.agency wrote a book about AX and the rise of agentic experiences a few months ago It's totally free for digital download latecheckout.agency/ax-book

Prompt the same style 50 times and you’ll get 50 different looks. Train a LoRA once and use it to get consistent images. Here’s how one of our designers is doing it 👇 1. Collect your reference images that share the look you’re after into one folder. 2. Have a model write a text file for each image describing what’s in it. The LoRA model reads the description instead of guessing at each picture. 3. Pick a trigger phrase for the style and include it in every caption. That phrase becomes the name you call the style by. 4. Zip the folder, upload to a tool like fal.ai, run the LoRA trainer. Your custom LoRA is the layer that sits on top of a base model. It teaches the model your look, your quality bar, that you can reliably call on and repeat.

Odyssey-themed All Hands this morning at @meetLCA Props to the legendary designers bringing visions to life for 6 years.

We used Codex to help audit the UX of 3 products in the same amount of time it would take to audit 1. Here's the setup 👇 1. Turn on browser use, give Codex the URLs and a goal, and let it crawl every path in on desktop and mobile. 2. Have Codex write a text file for each screenshot as it goes. What's on screen, where the flow breaks, what it would fix. 3. Treat the audit like a first draft & read every output before using any of it. A chunk of ours was noise and some findings weren't relevant. 4. Hand what survives to Claude to compile it into a microsite. Easier to digest, with a prioritized plan with screenshots and fixes next to each We ran this without any specific agent skills, but loading in your own would take this setup to the next level. Codex unlocked speed. You still need to know the product to know what's worth fixing.

Love when people take initiative and do cool stuff...