@@ -0,0 +1,173 @@
+---
+layout: post
+title: AI Twitter Highlights · 2026-10-12
+categories: AI
+description: High-signal AI coding / model / product discussions from X in the past day
+keywords: AI, Twitter, Codex, GPT-6.1 Sol, Grok Bot, poteto, Yobiru, Claude Mods, Cursor Projects, Open Agent Connect, Sofatap
+lang: en
+translation_key: ai-twitter-hots-2026-10-12
+permalink: /2026/10/12/ai-twitter-hots-en
+issue: 31
+item_count: 10
+headline: "Codex default context hits 500k, Grok Bot lands an iPhone, agents start waking each other"
+highlights:
+  - label: "Codex Day 7: longer context, no surcharge"
+    text: "Tibo raised GPT-6.1 Sol’s default context in Codex and Work from 272k to 500k (~80%), and subscription usage no longer pays long-context fees — fewer forced compactions on long tasks."
+  - label: "Grok Bot moves from demo to “it actually helped”"
+    text: "Someone had the Bot buy a sold-out iPhone 18 Pro Max with a virtual card; Elon quote-tweeted “this actually works” and called it a 24/7 super-employee; poteto’s “what do I use Bot for?” post neared 3K bookmarks."
+  - label: "Agent mesh + a rewrite of “Good Code”"
+    text: "Yobiru open-sources cross-machine agent messaging and wake-ups over Tailscale; Open Agent Connect adds Grok Bot; poteto sparks a debate on clean code in the agent era, with DHH and Addy Osmani weighing in."
+products: [Codex, Grok Bot, Claude Code, Cursor, Yobiru]
+stats:
+  - value: "500k"
+    caption: "New default context length for GPT-6.1 Sol in Codex / Work (was 272k)"
+  - value: "80%"
+    caption: "Lift versus the previous default context window"
+  - value: "870"
+    caption: "Replies poteto got asking what people did with Grok Bot this week"
+stat:
+  value: "500k"
+  caption: "New default context length for GPT-6.1 Sol in Codex / Work (was 272k)"
+---
+
+# AI Twitter/X Highlights Digest · 2026-10-12 (Mon)
+
+
+## Today's Highlights
+
+1. **Codex “28 days” Day 7 is a real context upgrade**: @thsottiaux said **GPT-6.1 Sol**’s default context in Codex and ChatGPT Work moved from **272k → 500k** (~**+80%**), and subscription usage **no longer pays long-context fees** — fewer forced compactions on long tasks.  
+2. **Grok Bot keeps proving it can get things done**: @liam_fallen had the Bot email shops, find stock, and order a sold-out **iPhone 18 Pro Max** with a virtual card; @elonmusk quote-tweeted “**Seriously, this actually works!**” and framed Grok @Bot as a **24/7 super-smart employee**; @poteto’s “not sure what to use Bot for?” post neared **3K bookmarks**.  
+3. **Agents start waking each other; “Good Code” gets rewritten**: @turingou open-sourced **Yobiru** (cross-machine messages / wake-ups over Tailscale); @newfish’s Open Agent Connect added Grok Bot; @poteto argued that clean-code priors need updating when agents write almost all the code — @dhh and @addyosmani both jumped in.
+
+---
+
+## 1. Codex Day 7: GPT-6.1 Sol default context → 500k
+
+**Key points**: Day 7 of Tibo’s 28-day run skipped another quota Reset and shipped product: **when GPT-6.1 Sol is used through Codex and Work, default context rises from 272k to 500k** (~80%), with more still to come. A follow-up clarified that **subscription usage no longer incurs long-context fees**. Community read: fewer forced compactions on long sessions, better stamina for big-repo / multi-file work.
+
+**Why it matters**: Yesterday was a “water day”; today is “longer window without a surcharge.” For anyone mid-Codex marathon, this is more immediately useful than another small feature drop.
+
+- Tibo Day 7 / 500k: https://x.com/thsottiaux/status/2109430343346581527  
+- No long-context fee on subscription: https://x.com/thsottiaux/status/2109430894604026039
+
+![Codex Day 7 500k context](/images/twitter-hots/2026-10-12/01-codex-day7.jpg)
+
+---
+
+## 2. Grok Bot: buys a sold-out iPhone; Elon: “hire a super employee”
+
+**Key points**: @liam_fallen couldn’t find an **iPhone 18 Pro Max** anywhere (Apple itself said end of October). He gave Grok Bot a virtual card; the Bot **emailed stores → found stock → verified and ordered → delivered**. He’s writing from that phone. @elonmusk quote-tweeted “**Seriously, this actually works!**” and said to treat Grok @Bot like hiring a **24/7, extremely resourceful employee** you can start using from your phone in minutes.
+
+**Why it matters**: Yesterday’s “photo a card and buy” demo becomes today’s “sold-out hunt that worked” user story plus official endorsement — the consumer-agent narrative keeps climbing.
+
+- Liam: Bot bought an iPhone 18 Pro Max: https://x.com/liam_fallen/status/2109332219126784098  
+- Elon: it works — hire it: https://x.com/elonmusk/status/2109387553010851887
+
+![Grok Bot bought an iPhone](/images/twitter-hots/2026-10-12/02-grok-iphone.jpg)
+
+---
+
+## 3. poteto: does clean code still matter in the agent era?
+
+**Key points**: @poteto first argued that **codebases have always contained slop** — most software never needed formal perfection, and we traded bugs for velocity via tests and observability; agents can raise average quality at scale, and the new craft is unlocking a real productivity gap. When replies clung to maintainability / clean code, she followed up: **those principles come from an era when humans maintained code** — optimizing for human readability often costs performance, and priors need updating when agents already write nearly all the code. @dhh agreed architecture needs a **grounds-up rethink** once lines are cheap and fast; @addyosmani added that “better at scale” comes from **cheap verification** — humans review evidence and loops, not only diffs.
+
+**Why it matters**: Not another vibe-coding flame war — heavy agent users rewriting what “Good Code” means, which decides whether you still pay a performance tax for human elegance tomorrow.
+
+- poteto: codebases always had slop: https://x.com/poteto/status/2109110547824378140  
+- poteto: update Good Code priors: https://x.com/poteto/status/2109356992032817621  
+- DHH: rethink architecture from the ground up: https://x.com/dhh/status/2109414545181831476  
+- Addy: quality from agent-run verification loops: https://x.com/addyosmani/status/2109384286763958742
+
+![poteto Good Code debate](/images/twitter-hots/2026-10-12/03-poteto-good-code.jpg)
+
+---
+
+## 4. Yobiru: cross-machine agents message and wake each other
+
+**Key points**: @turingou turned a recent “agents chat with each other” script into open-source **Yobiru** (ヨビル — Japanese for “to wake”): if machines share a **Tailscale** network, Grokbot, home-Mac Codex, and Tokyo-workstation Claude Code can exchange messages and files; **no central server**, payloads carry download URLs + sha256, and wake permissions stay with the recipient. Real usage: Grokbot asking home Codex to drive a 3D printer, routing bookmark digests to the Tokyo box for product work, booking a restaurant then having home Codex send WeChat (after human confirm), checking cat-food levels and reordering. Repo [chekusu/yobiru](https://github.com/chekusu/yobiru) was **created 2026-10-10**; today’s post is the formal intro spike.
+
+**Why it matters**: Personal agents’ blind spot has been “the cloud box can’t reach the LAN.” Yobiru’s thin protocol stitches multi-machine, multi-vendor agents into a wakeable mesh — yesterday’s sofa workflow, engineered.
+
+- turingou: open-sourcing Yobiru: https://x.com/turingou/status/2109153922267107458
+
+![Yobiru agent wake messaging](/images/twitter-hots/2026-10-12/04-yobiru.jpg)
+
+---
+
+## 5. Open Agent Connect: Grok Bot can DM Claude Code / Codex on another machine
+
+**Key points**: @newfish said **Open Agent Connect now supports Grok Bot**: cloud Grok Bot and laptop Claude Code / Codex each get a network identity and can send encrypted DMs. Others called it a “neutral layer” for agents — the network belongs to no single vendor. Complements Yobiru’s LAN wake path: one is public-key identity mesh, the other Tailscale private wake.
+
+**Why it matters**: Cross-harness, cross-machine collaboration is moving from “roll your own script” to something people productize; Grok Bot as cloud front door, local coding agents as hands, is a pattern you’ll keep seeing.
+
+- newfish: OAC + Grok Bot: https://x.com/newfish/status/2109312460943749407  
+- Lufe: a neutral layer for agents: https://x.com/Lufe77Liya77/status/2109319576517284104
+
+![Open Agent Connect Grok Bot](/images/twitter-hots/2026-10-12/05-oac-grok.jpg)
+
+---
+
+## 6. Claude Mods: reshape Claude Code’s own UI in the terminal
+
+**Key points**: Anthropic shipped **Mods** for Claude Code (CLI and desktop) — extensions that change behavior and UI. The community is already deep in: @nkgoutham built two mods (Grok Build–style UI, in-terminal file pane) and published a marketplace; Polish Twitter got a long explainer; others warned that **third-party mods are supply-chain deps** — read them before install. CN users are wiring desktop sessions with 5h/7d quota, context window, cache hit rate, and subagent progress via mods.
+
+**Why it matters**: After Hooks / Skills, Mods make “rewrite the harness itself” first-class — deep customization with the risk that every plugin can rewrite prompts or block tools.
+
+- nkgoutham: folio / tint mods: https://x.com/nkgoutham/status/2109200494224924788  
+- Kacper: Mods intro: https://x.com/KacperTrzepiec1/status/2109206634299883612  
+- Mohak: treat hooks like dependencies: https://x.com/MohakBajaj5/status/2109160614979596624
+
+![Claude Mods customization](/images/twitter-hots/2026-10-12/06-claude-mods.jpg)
+
+---
+
+## 7. Claude Code × GitHub: seven repos that thicken the harness
+
+**Key points**: @Marlenuii posted two high-bookmark lists stacking **Claude Code** with **Agent Skills** and parallel worker / reviewer repos — Sonnet routes, Haiku workers run in parallel, Opus reviews. It’s listicle distribution, but the signal is clear: **the stock CLI isn’t enough; people are welding public repos into multi-model pipelines**.
+
+**Why it matters**: Same engineering line as yesterday’s “lead agent splits work; subagents commit early” — tools made parallelism cheap; the community is standardizing how to weld it.
+
+- Marlenuii: 7 repos that strengthen Claude Code: https://x.com/Marlenuii/status/2109323814672724093  
+- Marlenuii: even wilder 10-repo orchestration list: https://x.com/Marlenuii/status/2109249955722338690
+
+![Claude Code GitHub repos](/images/twitter-hots/2026-10-12/07-claude-github.jpg)
+
+---
+
+## 8. Cursor Projects: still called “top tier” for orchestration and long jobs
+
+**Key points**: After Projects opened up, user-side echoes continue: @kiaraplds called **Cursor Projects top tier** for agent orchestration and long-running builds; @naoufal_elh said anyone not using Projects to build is “probably slower.” Others contrasting Claude Projects’ weak coordinator only sharpen Cursor’s feel advantage.
+
+**Why it matters**: Post-waitlist, the fight isn’t “can I open one?” — it’s “can I stop babysitting?” Projects are becoming the default workspace unit for heavy users.
+
+- kiaraplds: Projects are top tier: https://x.com/kiaraplds/status/2109257732700172345  
+- naoufal_elh: slower without Projects: https://x.com/naoufal_elh/status/2109253381248463349
+
+![Cursor Projects orchestration](/images/twitter-hots/2026-10-12/08-cursor-projects.jpg)
+
+---
+
+## 9. Sofatap: unlock Windows from your phone; voice / touch feed Codex
+
+**Key points**: @turingou built **Sofatap** for “living-room TV + RTX 5090 rendering, don’t want to dig for a keyboard”: the phone unlocks a home Windows PC, drives on-box **Codex** with natural language to open/close apps, or moves the mouse via touch gestures. He plans to polish, ship to app stores, and open-source. Same personal Agent OS mosaic as Yobiru and Grokbot sofa flow.
+
+**Why it matters**: A strong cloud bot still can’t replace wanting the screen in your hand to command local GPU / LAN software — Sofatap turns the phone into a remote keyboard/mouse plus Codex remote.
+
+- turingou: Sofatap: https://x.com/turingou/status/2109295035732926572
+
+![Sofatap phone to Windows Codex](/images/twitter-hots/2026-10-12/09-sofatap.jpg)
+
+---
+
+## 10. Grok Bot use-case catalog: 870 replies → 263 copyable jobs
+
+**Key points**: @poteto asked what people got done with Grok Bot this week and got ~**870 replies**; a follow-up said if you’re unsure what to use Bot for, send @bot that thread — the post neared **3K bookmarks**. @thisiskp_ distilled the replies into a **Bot Usecases** site with **263** real cases (streetlights fixed, proposal planning, pixel games…). Elon’s “hire an employee” framing and the community’s catalog landed the same day.
+
+**Why it matters**: In a tool boom you don’t need another feature list — you need “what have people already finished with it?” 870 → 263 is a searchable answer.
+
+- poteto: send Bot the idea thread: https://x.com/poteto/status/2109326308950032501  
+- thisiskp_: 263 Bot Usecases: https://x.com/thisiskp_/status/2109352523677233261
+
+![Grok Bot use cases catalog](/images/twitter-hots/2026-10-12/10-grok-usecases.jpg)
+
+---