Cascadity Audio
← All streams

#ai-coding

Everything tagged ai-coding, across every stream.

0

r/LocalLLaMA on Revolut cutting its AI coding costs about 90% by self-hosting an open model instead of Claude

A rare inside look at the numbers behind a large company moving its engineers from a paid AI service to a model it runs itself.

The Register reports that Revolut says it cut its AI coding inference costs by roughly 90 percent in under a year by making self-hosted models its default rather than relying mainly on commercial services such as Claude. Speaking at the AI Engineer conference in New York, ops and infrastructure lead David Abitbol said the fintech rolled AI coding tools out to about 2,000 engineers, adopted Z.ai's open-weights GLM-5.1 and now serves GLM-5.3 on 56 Nvidia B200 GPUs. Self-hosting cost about $0.30 per million tokens, roughly a tenth of Codex or Claude Code, and he said cheap tokens let engineers hand the AI debugging and ticket work, which is where the biggest gains came from. He also called very long context windows "a scam" in practice.

About 1,900 upvotes and 340 comments in a 329,000-member community. The top reply says this is why running models locally is not a waste of time; another argues that self-hosting means a company knows exactly which model it is running, while a cloud provider can change it without notice. One commenter who says they know people at Revolut describes its engineering culture as cautious.

Cascadic Analysis 1
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

The savings are measured right away: about $0.30 per million tokens, roughly a tenth of Codex or Claude Code, and the biggest gains came from handing AI debugging and ticket work. The quality of that work shows up on a slower clock, in code that ships and tickets that come back. A 90% cost cut is real; whether the cheaper model's fixes hold up is a separate question the cost figure can't answer, and one worth tracking alongside it.

0
Rabbit Holes 1
0

Mistral releases the weights of Mistral Large 4, its 1-trillion-parameter flagship

Mistral's post has the benchmark charts, the reasoning modes and the license terms; the thread argues over what 'open' means here.

Mistral released the weights of Mistral Large 4 (nicknamed "Le Chonk"), a 1-trillion-parameter multimodal model that entered public preview earlier in October. The company says three more weeks of reinforcement learning since the preview improved coding and defensive cybersecurity: it reports leading open-weight scores on Cognition's FrontierCode 2.0 (19.7%) and Terminal-Bench 4.0 (41%), and 51% on the Artificial Analysis Cyber Index, with a 96.6% refusal rate on malicious cyber prompts. These are vendor-reported results. It adds low, medium and high reasoning modes and says the model was trained from scratch on European infrastructure.

Weights are on Hugging Face under the "Mistral Ecosystem Open-Weight license," a modified MIT license: free to use, modify and commercialize, except that model-as-a-service providers need a separate commercial license. API pricing is $0.70 per million input tokens and $2.10 per million output tokens.

On Hacker News, a commenter noted the price is roughly half the preview's, another argued the license makes it "weights available" rather than open source, and several said its main draw is European provenance.

Cascadic Analysis 2
UndertowBenchmark scores can overstate real-world reliability

What hidden risk could pull against this, even if the news is good?

Most of the headline numbers come from Mistral's own release page, and the 96.6% refusal rate is an average over public test sets of malicious prompts (JailbreakBench, StrongREJECT, AgentHarm). Known prompts are what a determined user is least likely to send. Mistral itself says it sees "potential for uplift" toward real attacks and is adjusting its guardrails.

0
UndertowAutonomous cyber capability scales attackers enormously

What hidden risk could pull against this, even if the news is good?

Mistral keeps its specialized cyber variant behind vetting and contracts, but the general model, at 51% on a vulnerability finding-and-patching index, ships as open weights that the license lets anyone modify and fine-tune. Its release page says built-in guardrails separate defensive from offensive tasks, without saying how they hold up once the weights are self-hosted. A downloaded model can't be recalled if that line proves thin.

0
Rabbit Holes 2
0

r/homeassistant: a huge upcoming release raises AI worries, and a core developer explains how they review code

A maintainer's candid account of how a big open-source project handles a flood of AI-assisted contributions.

The post is an image, titled "Who's excited?", about the size of the upcoming Home Assistant 2026.11 release. German Home Assistant blog simon42 reports the 2026.11 beta is out with the final release planned for November 4, and that it reads like three releases at once, with HACS (the community add-on store) becoming a built-in marketplace and support for Matter cameras.

The top reply, from user frenck_nl, who says the screenshotted post is his, explains that the release is big because of a large number of contributions, that bringing HACS in was only a few pull requests, and that AI shows up in many submissions. He writes that the team has added static checks and tuned automated Copilot reviews, that his analysis of 10,000 reviews found about 40% of review comments were repeats worth automating, and that human judgment still decides. Other commenters say they'll wait for a later point release, or doubt that a large count of merged changes is good news in the AI era. About 2,600 upvotes in a 386,000-member community.

Cascadic Analysis 2
UndertowRole underspecification / the Doorman Problem

What hidden risk could pull against this, even if the news is good?

frenck_nl's numbers draw the line well: about 40% of review comments were repeats worth automating with static checks and tuned Copilot reviews. The other 60% is the part of a reviewer's role that isn't written down, judging whether a change fits the project and will be maintainable, and he says human judgment still decides. The risk in a release this large is volume quietly shifting more of that judgment to the automated layer.

0
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

A change that passes static checks and an automated review can still fail in someone's home months later, on a device combination nobody tested. Commenters planning to wait for a later point release are guarding against exactly that. A large count of merged changes measures throughput at merge time, not how the code behaves once it is running.

0
Rabbit Holes 1
  • Home Assistant

    After exploring Who’s excited?, the project itself is introduced in Home Assistant.

    Wikipedia describes Home Assistant as free, open-source software for centralized home automation that works across device brands and runs with local control.

    Wikipedia · Wade · 5 min

    0
0

r/LocalLLaMA cheers Linus Torvalds' reply rejecting 'don't use AI' rules for Linux kernel work

Torvalds' mailing-list reply in full, and a useful debate on where AI help ends and low-effort patches begin.

The post is a screenshot of a Linux kernel mailing-list reply in which Linus Torvalds calls the idea of "don't use AI for X" rules "idiotic" and, mockingly, proposes banning compilers and text editors for kernel submissions. He writes that he expects people "to understand what they are doing," and that this has "very little to do with what tools they use." The Next Web reports the reply came on October 13 after kernel maintainers moved to drop the "Assisted-by" tag that had asked contributors to disclose AI coding tools.

The top replies agree that quality work should be accepted regardless of where it came from, while others stress the other half of his message: contributors must understand their code. Several worry that AI makes it easy to flood open-source projects with low-quality pull requests that take maintainers time to sift. About 3,100 upvotes in a 329,000-member community.

Cascadic Analysis 1
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

Torvalds' standard is that contributors must understand their code, whatever the tool. Dropping the "Assisted-by" tag also drops the record of which patches came from AI tools. If a kind of mistake those tools tend to make shows up years later in code that passed review, maintainers won't have an easy way to find the other patches that might share it.

0
Rabbit Holes 1
0

OpenCode breach exposes users' stored AI provider keys, and some run up charges overnight

A cautionary tale for anyone who stores API keys in a hosted dev tool, plus a twist about AI models refusing to help defenders.

OpenCode, the open-source AI coding agent, said on October 17 that a breach tied to what it called a large-scale distillation attack hit 1.4% of users of OpenCode Console, its hosted service, and that it had emailed those affected. BleepingComputer and TechCrunch report that only users who had linked external providers (Anthropic, OpenAI, Google) were affected, that some reported hundreds to over $1,700 in unauthorized charges, and that Google suspended some projects. Co-founder Dax Raad said the open-source app and CLI were not affected; the company has not said how attackers got in. OpenCode told users to revoke their keys and says refunds are underway. Raad said AI models first refused to help the investigation until it switched to OpenAI's Daybreak cybersecurity model.

On Hacker News, commenters asked why a hosted service held provider keys at all, questioned the unproven 'distillation' label, and argued over earlier warnings about the project's data practices.

Cascadic Analysis 1
UndertowPrivilege escalation + credential propagation

What hidden risk could pull against this, even if the news is good?

OpenCode's hosted service stored keys to users' Anthropic, OpenAI and Google accounts, and only users who had linked them were hit; some reported hundreds to more than $1,700 in charges, and Google suspended some projects. A coding tool that holds your provider keys turns one breach into spending on several other companies' bills, which is the question Hacker News commenters raised: why the hosted service held the keys at all.

0
Rabbit Holes 1