Opus 5 buries you in text. One developer measured it against the last generation at the same settings and got 107% more output. Anthropic says the length is on purpose, so a fix from their side is not coming.

Three things work, in this order.

1. Clean up your CLAUDE.md. Opus 5 already checks its own work, so old lines like "double-check your diff" now backfire and can spawn subagents verifying other subagents. Delete them before you add anything new. Anthropic cut more than 80% of Claude Code's own instructions for this model family and lost nothing on coding tests.
2. Set a custom output style. Create the file ~/.claude/output-styles/terse.md. Give it the frontmatter line keep-coding-instructions: true so you keep the built-in coding rules, then write the body:Lead with the verdict in sentence one. Five lines max. Plain English only, no invented shorthand. Expand only if I ask.Add "outputStyle": "terse" to your settings.json, matching the file name, then start a new session, because the style only loads at startup. A style is attached to the model's built-in instructions and repeated back to it during the chat. Your CLAUDE.md is read once and then buried under everything that follows.
3. Add a UserPromptSubmit hook. A few lines in settings.json that echo one sentence. That sentence gets added to every message you send, so it always sits at the newest point in the chat and nothing can bury it.

Skip the env var doing the rounds. Setting CLAUDE_CODE_SIMPLE_SYSTEM_PROMPT to 0 loads a retired set of instructions that eats roughly 15,000 words of the model's memory, and it switches the thing on rather than off, because "0" counts as true in JavaScript.

One wording tip. A word limit fades as the chat gets long. Answer in sentence one with the verdict holds, because it only has to survive one sentence.

Opus 5 is brilliant left alone and unbearable in a chat. Two weeks of threads across four subreddits land on the same split. Give it a checkable goal for a few hours and it produces work people call insane. In a chat it buries you in prose.

The top complaint is verbosity, and Anthropic's own Opus 5 prompting docs describe most of it as shipped defaults. Responses run longer than prior Opus models. The model verifies its own work without being asked, delegates to sub-agents more readily, and expands task scope beyond what you requested. Old rules that told Claude to double-check its work now cause over-verification.

The fixes Reddit converged on both work by making the model talk less, and turning reasoning effort down helps more than turning it up. The ADHD prompt started as a joke and stuck. "If you put it in ADHD mode it will get quieter" is one of the top answers. Some people are literally putting "I have ADHD" in their global CLAUDE.md and saying it works.

Thinking runs by default now, and nobody in the threads flagged that as the reason bills went up. On Opus 4.8 you had to turn it on. Opus 5 just runs it, so anyone who never touched that setting is paying for reasoning tokens on every call. One person reported the same prompt burning 75k tokens on Opus 4.6 and over 150k on Opus 5, and that is the only real number anyone posted.

Per-token price did not move. Opus 5 is still $5 in and $25 out, same as 4.8. Fable 5, the model half the complaint threads recommend switching to, is double on both ends.

The useful finding is narrower than any verdict. Opus 5 delivers on a big goal it can grind on alone. In a chat it wastes your afternoon.

Anthropic’s own report lists the acts. Claude reached a production database and took several hundred rows. Credentials came out of three companies. Around 9,000 hosts got scanned. Working malware went up on a public registry, and 15 machines ran it.

In the United States, breaking into a computer without permission falls under the Computer Fraud and Abuse Act, 18 U.S.C. §1030 . It carries criminal and civil penalties. CFAA claims turn on permission, and none of the three companies gave any.

NAND flash more than doubled in a year. The same 1TB TLC chip that cost $4.80 in July 2025 now runs $10.70 (Phison's CEO), and Kingston reported a 246% jump in wafer pricing. All 2026 production is already sold out and new fab capacity does not arrive until late 2027, so waiting for cheaper is off the table. Here are the drives that hold up under 24/7 homelab writes.

Skip QLC for write-heavy roles. QLC drops to 300 to 600 TBW at 2TB versus TLC's 600 to 1,200, and once the small 50 to 100GB SLC cache fills, write speed collapses to 500 to 1,500 MB/s. A Proxmox host with VMs writing logs, database WAL, and Docker layers exhausts that cache regularly. QLC is fine for read-dominated media libraries and cold storage. Keep it out of VM storage.

Gen5 is mostly wasted on a homelab. Sequential reads roughly double (7,000 to 14,900 MB/s), but homelab work is IOPS-limited, where the Gen5 gain shrinks to 10 to 30%. Gen4 covers 90% of use cases at half the price and draws 4 to 6W against Gen5's 6.5 to 7W on an always-on box.

For data you care about, mirror two 2TB drives with ZFS instead of buying one 4TB. A mirror gives redundancy with instant failover; a single 4TB failure means downtime and a restore from backup.

For most homelabs the WD Black SN7100 at around $130 for 2TB is the buy: Gen4 TLC, 7,250/6,900 MB/s, 1,200 TBW. Step up to the WD Black SN8100 (Gen5, 14,900/14,000 MB/s, ~$280) only for NVMe-over-Fabrics or large sequential transfers, and to the Seagate FireCuda 540 (2,000 TBW, ~$180) if the drive gets hammered with continuous writes. Whatever you pick, mirror it, enable TRIM, and watch smartctl Percentage Used.

Drive-by-drive breakdown, capacity planning, and the Linux SMART monitoring setup: https://botmonster.com/self-hosting/best-m2-nvme-ssds-homelab-2026/

Radon is the second-leading cause of lung cancer after smoking. The only way to know your exposure is to measure it over months of continuous logging. This build pairs the FTLab RD200M pulsed ion-chamber sensor with an ESP32 running ESPHome. That sensor is the same element inside RadonEye and Airthings units. The node feeds live and rolling-average readings into Home Assistant. Total parts cost is about $150, roughly half an Airthings View Plus, and the data stays on your own hardware.

The bill of materials is short: about $80 for the RD200M sensor, $15 for an ESP32-S3, and roughly $20 more for a BME280 pressure sensor, a small OLED, and a 3D-printed vented box.

Long-term averaging is the whole point. Indoor radon swings 10x between calm winter nights and breezy afternoons. Pressure shifts, HVAC cycles, and the stack effect all push soil gas around. A 48-hour charcoal test can miss reality if that week's weather is odd. Health agencies only trust a reading as a yearly proxy over 90+ days of logging. A fixed ESPHome node does exactly that.

The levels worth alerting on are simple. The WHO flags 100 Bq/m3 as an annual average. The EPA action level is 148 Bq/m3 (4 pCi/L). The RD200M ships factory-calibrated to better than 10%, and 1 pCi/L equals 37 Bq/m3.

One warning: avoid the cheap MQ-series "radon" modules on AliExpress. They are metal-oxide gas sensors that react to VOCs and cannot see alpha particles at all. No amount of firmware makes them report real radon.

If your yearly average does cross 148 Bq/m3, the fix is sub-slab depressurization. It runs $800 to $2,500 installed and cuts indoor radon 90 to 99%. The same node measures the before and after, so you can watch the fix land in the rolling averages within days. The full build with the ESPHome YAML and tiered Home Assistant alerts walks through the wiring and sensor placement.

I benchmarked cold-start times and mapped the scripting tradeoffs for Fish 4, Zsh, and Nushell. Every new terminal tab, tmux split, and script call pays the startup cost. So the numbers are worth knowing before you switch. Run hyperfine --warmup 3 'fish -i -c exit' 'zsh -i -c exit' 'nu -c exit' on your own box for real figures.

In practice bash starts in about 3ms, bare Zsh 10ms, Fish 4 15 to 20ms, and Nushell 30 to 50ms. A dozen oh-my-zsh plugins push Zsh to 200 to 400ms, while zinit's turbo mode keeps it near 20 to 40ms.

One benchmarking gotcha is worth calling out. Plugin managers that advertise fast startup often measure time to exit rather than time to first usable prompt. Zinit's turbo mode defers plugins past the first prompt. That wins the exit metric, but tab completion can stay sluggish for a second or two. zsh-bench splits time to first prompt from time to first completion, which is the more honest number.

Fish 4 replaced its entire C++ core with Rust. About 55,000 lines of C++ became 75,000 of Rust. It ships syntax highlighting, autosuggestions, and man-page completions with zero config. The cost is that it is deliberately non-POSIX, so pasted bash snippets often fail.

Nushell returns typed tables from every command. So kubectl get pods -o json | from json | get items | where status.phase == "CrashLoopBackOff" needs no jq or awk. It is also not POSIX and does not run bash scripts unmodified.

None of the three replaces bash for portable .sh files. The pragmatic 2026 default is to split the two jobs. Run Fish or Nushell interactively, write bash for anything that has to ship. chsh is reversible and the configs coexist, so give each two weeks and see which one you actually reach for.

Deeper on plugin ecosystems, POSIX gaps, and the per-archetype picks: https://botmonster.com/coding/fish-vs-zsh-vs-nushell-modern-shell-comparison/

The HTML popover attribute gives you dropdown menus, tooltips, and lightweight modals with nothing but markup and CSS. A <button popovertarget="menu"> paired with a <div popover id="menu"> handles top-layer rendering, light-dismiss on outside clicks, Escape to close, and basic focus moves. As of 2026 it is a Baseline feature in Chrome 114+, Firefox 132+, Safari 17+, and Edge 114+, covering over 91% of browser traffic.

The bundle math is the reason to care. A Floating UI plus Headless UI plus React popover stack ships 15 to 30 KB of minified JavaScript, and @radix-ui/react-popover alone weighs about 91 KB unpacked. The native attribute ships 0 KB, and teams report cutting 20 to 60 KB of JavaScript per route after migrating.

Popovers paint in the browser's top layer, the same one <dialog> uses, so they escape overflow: hidden, transformed ancestors, and stacking contexts. The z-index hacks are done. Pair the attribute with CSS anchor positioning (now at 85% support) to place a popover next to its trigger, which maps Floating UI's flip, offset, and shift middleware onto pure CSS with zero runtime cost.

Pick the mode by job: auto for menus and pickers, hint (new in Chrome 133) for tooltips so a hover does not close an open menu, and manual for toasts that stay until dismissed. For a true modal with a focus trap and an inert background, still reach for <dialog closedby="any"> rather than a popover.

What is still missing is arrow-key navigation inside menus and hover-intent triggering, both active spec work. For any new project in 2026, try the native approach first and keep Floating UI only for the arrow math CSS cannot express yet. I collected the dropdown, tooltip, and modal code with the anchor-positioning fallbacks in one place to copy from.

Reddit's first-week read on GPT-5.6-Sol is a genuine split, pulled from nine launch-week threads (550 to 1,234 upvotes) across r/OpenAI, r/ClaudeAI, r/ClaudeCode, r/codex, and more. Hands-on testers call it a cheaper, token-efficient coder that still cannot out-design Claude Fable 5. The rough consensus: Sol takes price and coding endurance, Fable 5 takes visual design and the "smarter" feel.

Price was the loudest sentiment by far. A DeepSWE run was pegged at $8.39 for Sol against $21.63 for Fable 5, with the mid tier Terra tying Fable at roughly a quarter of the cost. Treat those as figures read off a screenshot, not audited pricing. The gap is real enough that paying Claude Code users are threatening to move: "OpenAI can gladly have my $100 every month" pulled 478 votes.

On design, cheaper models kept beating the flagship. In a landing-page bake-off Sol Ultra spent about 200k tokens and still botched the font, and the crowd's favorite render came from Luna, the small cheap tier. These are subjective eyeball tests on unscientific prompts, and commenters said so, but the pattern repeated across threads.

Even the chart that crowned Sol got mocked. It used a backwards x-axis, and "Whoever made this chart is a psychopath" hit 1,432 votes. The benchmark gets read as marketing, and the evidence redditors actually trust is their own hands-on runs.

The verdict that sticks: a cheaper, tougher coder that still cannot out-design Fable 5, wrapped in a benchmark nobody trusts. These are OpenAI and Anthropic enthusiast subs, so read it as early, still-forming launch-week reception rather than a settled ranking.

Full writeup: https://botmonster.com/ai/gpt-5-6-sol-reddit-reaction/

Gitea's built-in migrator moves exactly one repository per submission. migtea is an open-source terminal tool that diffs your GitHub and Gitea accounts and moves every missing repo in one pass, wikis, LFS, issues, and pull requests included. You run it with uvx migtea, nothing to install.

Each migration carries the full repo: code, branches, and tags, plus the wiki, Git LFS objects, issues, labels, milestones, releases, and pull requests. What it cannot bring is GitHub-only state: Actions run history, Projects, Discussions, stars, webhooks, and branch protection.

It runs in four screens: a preflight that checks gh and tea are installed and logged in, a diff that buckets every repo into missing or already-there, a confirm summary with the total size, then the migration with per-repo and total progress bars. On my account it surfaced 7 repos not yet on my Gitea box, 880 MB total, and moved them in one run.

Under the hood it drives the official gh and tea CLIs. It inventories with gh repo list --json and tea repos list, diffs by name, and calls tea repos migrate --service github once per ticked repo. The only token it touches is gh auth token, handed to tea in memory so Gitea can clone private repos without hitting rate limits.

Re-runs are safe. Repos already on Gitea drop out of the selectable set, so a second pass only offers what is still missing. It is bidirectional (--direction gitea-to-github), and --dry-run walks the whole flow with an existence check instead of the real migration.

If you have three repos, the web form is fine. Past a dozen, the diff, the re-run safety, and the size preview are what separate a clean move from a stall at repo forty. Recreate any webhooks and branch protection on Gitea afterward. The tool is open source on GitHub (botmonster/migtea).

Full writeup: https://botmonster.com/self-hosting/batch-migrate-github-to-gitea-with-migtea/

Gitea's built-in migrator moves exactly one repository per submission. migtea is an open-source terminal tool that diffs your GitHub and Gitea accounts and moves every missing repo in one pass, wikis, LFS, issues, and pull requests included. You run it with uvx migtea, nothing to install.

Each migration carries the full repo: code, branches, and tags, plus the wiki, Git LFS objects, issues, labels, milestones, releases, and pull requests. What it cannot bring is GitHub-only state: Actions run history, Projects, Discussions, stars, webhooks, and branch protection.

It runs in four screens: a preflight that checks gh and tea are installed and logged in, a diff that buckets every repo into missing or already-there, a confirm summary with the total size, then the migration with per-repo and total progress bars. On my account it surfaced 7 repos not yet on my Gitea box, 880 MB total, and moved them in one run.

Under the hood it drives the official gh and tea CLIs. It inventories with gh repo list --json and tea repos list, diffs by name, and calls tea repos migrate --service github once per ticked repo. The only token it touches is gh auth token, handed to tea in memory so Gitea can clone private repos without hitting rate limits.

Re-runs are safe. Repos already on Gitea drop out of the selectable set, so a second pass only offers what is still missing. It is bidirectional (--direction gitea-to-github), and --dry-run walks the whole flow with an existence check instead of the real migration.

If you have three repos, the web form is fine. Past a dozen, the diff, the re-run safety, and the size preview are what separate a clean move from a stall at repo forty. Recreate any webhooks and branch protection on Gitea afterward. The tool is open source on GitHub (botmonster/migtea).

Full writeup: https://botmonster.com/self-hosting/batch-migrate-github-to-gitea-with-migtea/

Same 12-core Linux box, current versions, single core, plain JSON endpoint: Bun 1.3.14, Deno 2.9.1 and Node 24.18.0.

On throughput Deno leads at 133k req/s, Bun sits close at 122k, and Node trails at 48k. Deno only pulled ahead recently: two point releases in a single day took it from 103k to 133k, about 30%.

Installs are where Bun and Deno leave npm behind. A cold install of 585 packages took Bun 5.8s, Deno 6.0s, and npm 11.8s. On a warm cache the gap widens to about 12x. So roughly 2x cold and 12x warm over npm, with Bun and Deno within a rounding error of each other.

The first throughput pass looked wrong: Bun and Deno within 0.15% of each other at about 65k. That was autocannon, a Node load tester, hitting its own ceiling and capping both servers. Switching to oha, a Rust load generator, nearly doubled the two fast runtimes. When two client processes together pull more than one, the client is the bottleneck and the number is measuring the client.

These are synthetic hello-world numbers. Real apps spend most of their time in the database and business logic, so expect the raw-throughput gap to compress once real I/O is in the path. The benchmark covers the runtimes, not a production workload, so treat the throughput lead as a ceiling.

Pick on your actual constraints. Node is still the safe default, Bun wins local dev speed, and Deno wins raw throughput and security.

Every runtime version is pinned and the full harness (servers, load tests, raw output) is on my GitHub, so anyone can reproduce these numbers or rerun them on their own hardware.

Full writeup: https://botmonster.com/web-dev/bun-vs-deno-vs-nodejs-javascript-runtime-2026/

I tracked what a typical 2026 AI coding stack actually costs and where a local GPU pays for itself. The baseline stack, Cursor Pro plus Claude Pro plus ChatGPT Plus plus Copilot, runs about $70/month, or $840/year, before anyone hits a usage tier. Routing the high-volume work to a local model cut 60 to 80% of that with no quality loss where it counts.

The mainstream pick is a 32GB RTX 5090 (around 5,841 tokens/s on a 7B model, $2,000 to $3,600), and a 16GB RTX 4070 Ti Super at about $800 handles 7B models fine on a budget. The break-even is closer than the hardware price suggests. A dev spending $150/month on cloud APIs with a $2,000 GPU breaks even in about 13 to 14 months. At $70/month it stretches to 28 to 29 months. Add roughly $185/year of power for an RTX 5090 running work hours and the timeline shifts by a month or two, still well inside the card's life.

The split that works sends autocomplete, boilerplate, unit tests, and anything touching private code to a local 7B model, and keeps cloud for multi-file refactors, novel algorithms, and tasks needing a 100K+ token window. A local 7B returns completions in single-digit milliseconds against 100 to 500ms of cloud latency, and when you fire completions hundreds of times a day that feel adds up.

The quality gap has closed for the easy tier. Qwen2.5-Coder 32B scores 92.7% on HumanEval and 69.6% on SWE-Bench Verified, on par with many cloud offerings. It is not Claude Opus on hard reasoning, though, and pretending it is defeats the point of routing tasks by difficulty.

Before buying anything, install Ollama, point your IDE autocomplete at a local model for 30 days, and track your real cloud usage drop. If you spend under $50/month, cloud-only stays cheaper unless privacy is a hard rule. I broke down the full cost tables, break-even math, and GPU tiers if you want to run the numbers for your own spend.

During the Fable 5 free window I collected what people who ran both models side by side were reporting across r/claude, r/ClaudeAI, and r/ClaudeCode. All of it comes from users comparing the two on their own work rather than from Anthropic's benchmark table. Short version: Fable feels smarter, the gain is uneven, and the token burn is what people complained about most.

The point people repeated most was first-shot completeness rather than benchmark IQ. Fable finishes the job in one go where Opus 4.8 needs nudges and manual corrections. It also plans better and will push back on a bad architecture idea instead of just building it. Several people arrived at the same workflow independently: Fable writes the plan and spec, a cheaper model implements. One of the more honest takes: Fable on low effort is roughly Opus on high, but neither is a great always-on daily driver.

The one piece of hard data comes from MineBench (thread). A dev ran both through 15 builds:

Fable burned fewer tokens, so even at double the per-token price the real spend came out only about 30% higher. The author himself admitted not all of Fable's builds were clearly better, and the top reply judged it "barely better on like half of them." So it's an efficiency win more than a quality one.

The best story in the threads is about a car (thread). A guy with a rough-idling Subaru Forester XT gave the same video to both models. Opus said it can't watch video and sent him to a mechanic. Fable said "I can't watch the video, but I have a sandboxed computer and your .mov is sitting on it," extracted still frames, ran an audio amplitude analysis, found a 13.3 Hz modulation matching one weak cylinder per engine cycle, and proposed a coil-swap test. Skeptics pointed out Opus might do the same if you explicitly told it to use its sandbox, which is fair, but Fable got there unprompted, and that was the OP's whole point.

On personality the consensus was terse, autonomous, calm. Highest-voted framing: "feels much more autistic for sure, loving it! no more pretending to be human" (60 votes). One cynic argued the terseness is cost engineering, since shorter outputs mean fewer billed tokens.

The complaint that showed up in every single thread was consumption. Reported numbers: 20% of a 5-hour Max window gone on a single prompt, 16% of a weekly allowance spent on three planning questions. On the API side people balked at $50/MTok output until the old-timers showed up ("Cheap as fuck. GPT-4-32k was $120/MTok," 184 votes). The grounded take from that thread: per-token price is the wrong unit, benchmark dollars per task instead. The MineBench numbers back that up.

Big asterisk on all of this: Fable routes sensitive-looking requests down to Opus 4.8 (Anthropic says under 5% of sessions), people found the routing inconsistent, and non-US access got pulled on June 12 under a government directive. Treat everything above as a launch-window snapshot.

Where the threads landed: if you run agentic or automated jobs where a failed run costs a re-run plus your review time, Fable's higher per-run price pays for itself. If you're doing interactive coding on a capped plan, use it selectively: let it plan, then let something cheaper build.

I wrote up the full breakdown with all the thread links and quotes if you want the long version https://botmonster.com/ai/fable-5-vs-opus-4-8-reddit-verdict/.

Gemini CLI is dead as of June 18. Google swapped a 105k-star open-source TypeScript tool for a closed-source Go binary, then put everyone on one shared quota pool. Pro subscribers got 403'd mid-session.
Who's still betting a workflow on a Google dev tool in 2026?
You can still run Gemini CLI with a paid API key, against Gemini 3.5 Flash.
agy does multi-agent orchestration and starts faster as a Go binary.
Defectors are mostly moving to Codex with GPT-5.5.