The hype is true. Anthropic did magic with Opus 5.5. Damn it's good.

We’ve fixed a bug that was degrading image understanding in GPT-6 Sol and GPT-6 Luna. You should now see better results on visual tasks in the API and Codex, including computer use.

i suspect those influencers telling people to “rent a VPS and move your agents to cloud” are getting a commission helping sell VPS i’m using a mac mini which i bought at $2500 and i’m often running it near full capacity building various ios and mac apps if i rent a VPS instead, it cost about $300/month for a similar spec. with just 9 months, the rent would have exceeded the full price let’s say i decide to keep going for 5 years, total VPS cost would be $18k and that’s for just running 1 machine for 5 years. at the end i own nothing if i invest that $18k to buy my own hardware instead, i could have got 7 mac minis so 7x more compute capacity, and they would be mine forever if you are considering a long term setup, i can’t think of any good reason to be renting VPS. own your hardware - my desk is my cloud

Grok Bot now connects to your finances. Link your bank, card, and investment accounts with the new Finance integration, then ask Bot to help manage your spending, investments, and more.

Factory Router now cuts inference costs by 63% in production, up from 42% in late June, while routed session volume grew roughly 4x.

I feel retarded for not knowing about OMO going full PI. OmO 5.0 now runs on a fork of badlogic's pi, and the onboarding alone sold me. First it gives you a feature tour and handles migration if you're coming from OpenCode. Then it asks before digging through your past sessions, mines them for how you actually work, and works out how much you've saved on cache from its own logs. It saves what it learns to memory and ends with a send-off. After that, ulw reads the repo, plans, and proves every step. mass ulw turns one job into a graph of agents, each on the right model. 69k stars and I'm this late. @q_yeon_gyu_kim github.com/code-yeongyu/oh-m…

If @OpenAI launches the rumored $500 plan, what will get you to pull the trigger — Do you exceed your plan today regularly?

Thariq from Anthropic's Claude Code team just published his tests on effort: turning effort up mostly buys 𝗺𝗼𝗿𝗲 𝘃𝗲𝗿𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗲𝗱𝗴𝗲-𝗰𝗮𝘀𝗲 𝘁𝗲𝘀𝘁𝗶𝗻𝗴. You can turn his approach into 𝘁𝘄𝗼 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 and have Claude Code follow it. For new features, he works in four steps: → Have Claude ask you questions first and fill in what the spec is missing → Build it on low. It's fast, and you can step in anytime → Look it over, and if it needs changes, stay on low → Switch to high at the end to verify and test If you want to try it, send this image and the prompt below to Claude Code 👇 "Set up the workflow in this image in my Claude Code: 1. Create two subagents in ~/.claude/agents: - builder: writes the code. model: opus, effort: low. It implements the spec I've approved and stops when it's done. - verifier: checks the work. model: opus, effort: high. It runs the feature first to see what it actually does, then adds tests, focusing on edge cases. It reports problems to me and doesn't change the code itself. 2. Add a rule to ~/.claude/CLAUDE.md: when I ask for a new feature, first ask me what the spec is missing; after I confirm, hand it to builder; after I've reviewed the result, hand it to verifier. 3. Check whether the environment variable CLAUDE_CODE_EFFORT_LEVEL is set. If it is, the effort settings on both subagents won't take effect. Just tell me; don't change it. Show me the contents of the files you'll create or change, then explain the whole workflow in words a 10-year-old could follow. Don't write anything until I confirm."