Theo - t3.gg

wtf chrome has vertical tabs now. finally

meek mill got into YC and your ai wrapper just got demolished by a claude update

Fun fact: Automating iMessage use is against Apple's TOS. Particularly funny to see this from Anthropic

I don't understand vertical tabs. Why would I want less space for the website content I actually want to look at?

ChatWise idle memory usage Before (tauri) vs Now (electron)

→ Search the web for live sports scores and stock prices → Find files on my desktop and run shell commands → Write code and solve math problems → Everything Claude Code does — for free The breakthroughs that made this possible: Apple's "LLM in a Flash" paper showed models can page from SSD using unified memory. I proved it works in practice on consumer hardware — not just in a research lab. Google's TurboQuant research showed you can compress KV cache with zero quality loss. I applied this with two server flags and doubled my context window from 32K to 64K tokens. For free. No code changes. The biggest surprise: the 35B model at 2.6 bits per weight was supposed to have "broken" tool calling. Every agent framework I tried failed — infinite loops, no answers. I stopped asking the model to generate JSON function calls. Instead I ask it simple questions. "Is this a search, shell, or chat?" → one word answer. Works perfectly. The tool calling wasn't broken. The protocol was wrong. Both models. Full agent. Same $600 computer: → 35B MoE: 30 tok/s, 2x faster, smarter reasoning → 9B dense: 16 tok/s, 64K context, reads entire codebases I benchmarked everything: → 212 math problems: 86.3% accuracy (3 categories at 100%) → 10 web search categories: 10/10 accurate → Shell commands: finds videos, checks disk space, reads code → MLX vs llama.cpp: tested both, llama.cpp wins for 35B

OpenCode is about to get more powerful with remote sandboxes I showed a brief demo before, but here's a much more in-depth demo. it's not hard to add basic support for a remote env, but handling all the edge cases like when a remote env gets deleted is difficult. especially if care about good UX You never want to lose session data. so the choices are: run the session in your env, but run all tool calls remotely. that's too complex and painful. The other way is to just let the full session run remotely, but sync back all the session data in your env. We chose this path: we built a syncing system which logs all events in a way that we can always recreate your entire session. That means the remote env could get destroyed, but we can easily restore it. it also opens up other interesting ideas which we'll be exploring