· 05:30 PM PDT

OpenAI and Cursor part ways as local AI surges.

Overview

OpenAI is terminating its model supply agreement with Cursor following its acquisition by SpaceX, marking a significant shift in the developer tool ecosystem. The local AI community is equally dominant, with massive engagement around Qwen3.8 optimizations, aggressive model compression, and real-world benchmarking that prove desktop hardware can now rival cloud inference. Across the broader industry, a growing consensus is forming around the gap between AI hype and practical software engineering, with experts stressing that organizational culture and disciplined workflows matter more than raw model capabilities. Meanwhile, regulatory and market movements continue to reshape the landscape, from Debian officially approving responsible AI integration to legal rulings and corporate feuds defining the next phase of the AI race.


Hacker News Stories

Our decision on Cursor following its acquisition by SpaceX

793 points · 486 comments · by meetpateltech

OpenAI announcement banner about Cursor decision

OpenAI is terminating its contract to provide AI models to the Cursor developer tool following its acquisition by SpaceX, with the service scheduled to shut down on November 12, 2026. The company cites a loss of confidence in SpaceX's ability to comply with OpenAI's terms of service, pointing to prior contract violations by Elon Musk's Twitter/X and xAI ventures. OpenAI is utilizing a change of control clause to delay the cancellation to the latest permissible date while withholding access to its upcoming Astra model.

Interesting Points
  • The proposed service shutoff date is November 12, 2026, which OpenAI states is the maximum notice allowed by their contract.
  • OpenAI references a recent court proceeding where Elon Musk admitted under oath that xAI violated OpenAI's terms by distilling and using OpenAI data to train its own models.
  • The termination relies on a change of control provision in the custom agreement that opens a limited cancellation window after Cursor's acquisition.
  • OpenAI will not provide access to its upcoming model, Astra, to Cursor as part of the phased termination strategy.
  • The Cursor CEO reportedly stated that OpenAI models represented only about 5% of total user traffic within the tool.
Top Comments

Is there some kind of alternative to Cursor in these terms

  • fast because the code is already indexed no need to start every prompt rediscovering the world with rg

  • in editor/VSCode review much better than relying on git diff at the very end. You can click on next button to jump there. Quick edit in place. Or a quick prompt (seconds) to fix something small

  • in editor completion / quick edits, when you do things by hand.

It seems that everyone loves agentic Claude code things these days but I don't understand how you can review what it did and remain as much in the flow as you do with cursor.

Also I find that incredibly slow. By the time Claude finished a prompt I could have done a few in cursor.

And mind you, I've been wanting to use zed instead but the clunky vscode fork called cursor. But cursor has just a better UX for AI integration even though it's slow and guzzle up RAM.

jackjeff (thread)

I use Cursor because I listened to YouTube interviews with the teams behind most of these products and I trusted their team the most.

pianopatrick (thread)

Bummed, but I guess for me, doesn't mean cursor subscription ending though. Grok is a pretty amazing model for the speed and price on Cursor.

hargup (thread)

Seems you're looking for an editor with agent, not just a agent, so something like Zed?

lloeki (thread)

Codex

thatscot27 (thread)


Debian votes to allow "responsible use of generative AI"

470 points · 432 comments · by pluc

Debian has officially approved a resolution allowing the "Responsible Use of Generative AI" across its software development, packaging, and documentation processes. The decision strikes a pragmatic balance by acknowledging that AI tools can significantly boost volunteer productivity while maintaining strict requirements for code quality and legal compliance. Under the new guidelines, the project maintains a neutral official stance, neither endorsing nor banning AI usage. Contributors are explicitly mandated to review, test, and modify any AI-generated output before submission, as the policy ensures that tool usage does not reduce personal accountability for the work.

Interesting Points
  • The official voting results designate the winning policy as "Choice 5: Responsible Use of Generative AI."
  • The resolution explicitly states that using generative AI does not diminish a contributor's personal responsibility for the quality, correctness, and legal compliance of their submissions.
  • Contributors are required to actively understand, test, and modify AI-assisted output rather than passively integrating it into Debian media.
  • The policy recognizes that automating routine tasks with AI can free up limited volunteer time for work demanding technical expertise and collaboration.
  • Debian maintains a strictly neutral official position, neither endorsing nor prohibiting generative AI across software development, packaging, or documentation.
Top Comments

New policy boils down to "AI or not, it's still your code and you're responsible for it". I can get on board with that.

chuckadams (thread)

This is the way it should've always been. I don't care what tool you use, but you'd better be ready to stand by and explain the results if necessary.

oooyay (thread)

86Box is like that and I like it.

trollbridge (thread)

Debian - and others - could take the opportunity to raise their standards (not that they were relatively low).

A new technology, AI, greatly reduces costs in software development. When a new technology makes inputs cheaper, there's a choice: Reduce the cost of the product, or keep the cost the same and spend the newly available resources on improving product (or somewhere between those poles). For example, if the cost of chickens goes down, the farmer can buy a lot more chickens and produce a lot more eggs, or they can keep their expenses the same and now afford higher quality chickens or production (free-range!).

In software development, facing this new trade-off, people seem to overwhelmingly choose to produce the same software but far more of it, whether or not anyone wants it.

What if instead we made much higher quality software? Larger projects, at least, haven't wanted more pull requests; they have wanted better code. With the AI handling much of the work, the developer's attention can be applied to more difficult tasks. We absolutely need better software, especially with AI systems finding exploits.

mmooss (thread)

Debian Rust rewrite incoming.

DarmokTanagra (thread)


I accidentally turned LLM memory into program analysis

274 points · 73 comments · by matt_d

Lemmalog Datalog-based memory system diagram

The author created Lemmalog, a Datalog-based memory system for LLMs that treats agent knowledge like program analysis state rather than relying on vector retrieval or full conversation history. By splitting natural language extraction from deterministic rule-based reasoning, the engine automatically tracks fact dependencies and invalidates outdated conclusions when new information contradicts them. Benchmarked on LongMemEval and LoCoMo, Lemmalog achieves competitive scores with dedicated memory systems while drastically reducing the context window required for queries.

Interesting Points
  • Lemmalog achieved an F1 score of 0.463 on LongMemEval, outperforming full-context GPT-4.1 prompting (0.197 F1) by more than double while using roughly 38 times fewer tokens per query.
  • The system tops the Knowledge Update category on LongMemEval with a 0.579 score, successfully handling scenarios where earlier beliefs are disproven and conclusions must be automatically invalidated.
  • On the larger LoCoMo benchmark (1,986 questions), Lemmalog scored 0.533 F1, placing it third behind PropMem and OpenClaw, but significantly outperformed full context on adversarial questions containing false premises.
  • Initial benchmark performance was less than half the final score; improvements came from fixing concrete computer science issues like broken date comparisons, plural stemmer mismatches, and faulty entity reconciliation rather than scaling the language model.
  • The architecture separates the LLM's role as a probabilistic front-end for extracting structured facts from a deterministic Datalog engine that maintains provenance, temporal validity intervals, and incremental evaluation.
Top Comments

I reached a similar conclusion: LLMs should only really sit at the terminals of request fulfilment.

  1. User request understanding: natural language -> a more rigorous representation, in my case Datalog.

  2. Result interpretation: facts and derived facts -> natural language.

Between those terminals, the work should be mechanical reasoning over some ontology or formal knowledge structure.

That connects to another principle I've been thinking about, which I call Weathering: useful reasoning should change the shape of the system. If an LLM has already had to infer a relation, mapping, rule, or abstraction, repeated use should wear that inference into the system so that the next similar request doesn't require discovering it again from scratch.

With continued use, a weathering-capable system should therefore require less and less probabilistic intelligence for recurring work. Put another way, there should be a declining marginal cost of cognition since the products of intelligence harden into structure that can subsequently be reused and evaluated mechanically.

sim04ful (thread)

Datalog seems like a way to "spell" knowledge graph (KG).

The article touches on Datalog statements changing over time. One ingredient I think would be good to add to the system is to make every statement carry "providence" metadata. The providence should be sufficient to enable later confirmation that a statement is still valid or if the statement needs to be reformed without the need to remake the entire graph from scratch.

I would make at least some forms of providence follow a strict schema that is defined for the subject matter that is being captured. For example, statements about a code base should refer to the source files and their version (file modification date, content hash) from which the statements were concluded. When a source file is modified we may then find all statements made from them and reevaluate just those statements.

The next level would be to keep statements even if reevaluation breaks them and add a method to derive a subgraph for a given state of the subject. For example, over many releases of a code base, a lot of statements would not change, some would. Having a graph that spans all conclusions about all releases of a code base and a way to form the subgraph for a specific release would allow the system to efficiently target queries for a particular release.

frumiousirc (thread)

Is this sort of re-inventing Graph RAG from another angle, or does it feel novel?

fizx (thread)

Very cool. I recall an HN submission (which I can't find offhand unfortunately) that did something similar -- it used an LLM to decompose articles into a set of statements which were used to construct an entity-relationship graph of facts and events. It then queried that using conventional graph query methods, much like DataLog / Lemmalog is doing here. I remember it was particularly effective at answering timeline-based queries that LLMs (back then) sucked at.

(See also Cyc: https://en.wikipedia.org/wiki/Cyc)

I think approaches like this are going to be (or maybe already are?) the basis of effective grounding of LLM responses in authoritative data sources. It should be possible to pinpoint any error to an incorrect traversal or an incorrect "fact." This would work best for concrete, unambiguous facts, however; fuzzy, ambiguous or opinion-based information will probably remain the purview of LLMs.

keeda (thread)

So he's using an LLM to generate data stored in an "is_a" representation. That's so classic AI.

Soon, he'll discover that he needs quantifiers. Then that "for all" is too strong sometimes, and he needs "for most". That way lies Cyc.

It's not a bad idea. But it does have a history.

Animats (thread)


Good Culture Is the Biggest Productivity Hack, Not AI

225 points · 50 comments · by gpi

Newsletter header image

The article argues that organizational culture, not AI tooling, is the foundational driver of engineering productivity. While executives frequently chase AI efficiency claims, the author warns that AI merely amplifies pre-existing communication patterns and architectural quality, making it ineffective or destructive in toxic environments. Instead of using AI to replace talent or mandate top-down adoption, leaders should prioritize psychological safety, clear decision-making autonomy, and outcome-based rewards. Ultimately, companies will gain a competitive edge by hiring more engineers to scale output exponentially, using AI as a multiplier for an already high-performing team.

Interesting Points
  • Conway's Law dictates that an organization's communication structure directly shapes its system designs, meaning poor culture guarantees poor technical and architectural outcomes.
  • Many executive claims of 10x AI-driven productivity gains are often marketing tactics designed to sell specific tools or partnerships rather than reflecting genuine internal results.
  • AI adoption cannot be enforced top-down because the tooling landscape evolves too rapidly, requiring continuous, bottom-up knowledge sharing among engineers.
  • The author asserts that companies should actively hire more engineers rather than reducing headcount, arguing that increased talent density exponentially boosts productivity when paired with AI.
  • AI acts as an architectural amplifier, accelerating the delivery of bad code and flawed systems just as quickly as it does for well-structured, high-quality engineering.
Top Comments

I think the points being made here are mostly good-ish. The last place I worked created a team of principles whose whole goal was to create a system to turn jira tickets into PRs and it was incredibly demotivating and bore no fruit before I left.

But, and maybe I'm just a curmudgeon, but I kind of wonder why we write articles like this. Like if a culture is bad, is it likely a CEO is going to be looking for random blog posts for constructive criticism?

Or even managers? I look at the market forces at play, and I just don't think many (any?) organization successfully create an incentive structure where performance on intangibles (specifically management) can be assessed well enough to make a bad culture into a better culture. I've worked at zero places where managers where seriously held to account for how "motivated" their employees were; when there were surveys of engagement engineers almost never truly believed they were anonymous (and why would they?) and were hesitant to give honest feedback.

In short, being a CEO is a skill of crafting and debugging a machine of people, a skill that I think life gives almost no training for, and a skill that most people with that title have no awareness or aptitude for.

zug_zug (thread)

It's easier to deploy AI than it is to create good culture.

joshheitzman (thread)

AI accelerates dysfunction. It will help you get to the wrong place faster if you're already heading there.

I do believe the opposite is true too. If you have a strong culture, a product or idea with promise, and a team of smart and capable people, it can move you faster in the right direction too.

The problem is that every person or company in group 1 thinks they are in group 2.

aesthetics1 (thread)

The biggest stock-price hack for a CEO is:

  • announce that effective immediately, the company will begin its transformation to an "AI-first" organization, with AI driving most development workflows by end of year

  • percolate the message through upper management down to line managers that they are to assure their reports that the aim of the transformation is to augment current employees, not reduce headcount

  • stealthily start lopping off heads anyway

bitwize (thread)

Without good culture, everything else won't work well

Except the market is full of proof this isn't true. You can still do very well with a broken culture if you have an oligopoly, through tactics like vendor lock-in, by buying up upstart competition early, using VC funding to capture the market by selling below cost, etc.

And now that you have hundreds of thousands of people who have been laid off from high-paying jobs, it's an employer's market.

ElProlactin (thread)


StemDeck, a free, open-source and local AI stem separator

199 points · 58 comments · by thclpr

StemDeck is a free, open-source desktop application that performs local AI-based audio stem separation, splitting tracks into up to six isolated components like vocals, drums, and bass. Built on Meta AI's Demucs htdemucs_6s model and wrapped in a Tauri v2 interface, it processes files entirely on the user's machine without requiring accounts, subscriptions, or cloud uploads. The tool includes a DAW-style multitrack mixer, waveform visualization, and metadata analysis features like BPM and key detection, positioning itself as a privacy-focused alternative to commercial services.

Interesting Points
  • Uses Meta AI's open-source htdemucs_6s neural network with automatic hardware detection for NVIDIA CUDA, Apple Silicon MPS, or CPU fallback.
  • The initial setup downloads a roughly 170 MB model file and a ~500 MB Python runtime, but subsequent launches skip these steps to start in seconds.
  • Includes a song analysis module that calculates BPM, musical key, scale confidence, and integrated LUFS loudness using librosa and pyloudnorm.
  • Processes audio through a cancellable job queue that automatically purges incomplete or old job directories based on a configurable 24-hour time-to-live.
  • The desktop app is built with Tauri v2 using vanilla JavaScript and the Web Audio API, explicitly avoiding heavy frontend frameworks or build steps.
Top Comments

I built StemDeck, a free and open source desktop application that separates songs into vocals, drums, bass, guitar, piano, and other stems. It started as a small project for my kid, who was learning bass and drums. Finding suitable backing tracks was surprisingly inconvenient. Most tools required an account, uploaded the audio to a remote server, imposed usage limits, or required a subscription. I wanted something simple that could process music locally.

StemDeck now includes:

  • Local six-stem separation using Demucs
  • NVIDIA CUDA, Apple Silicon MPS, and CPU processing
  • Native releases for Windows, macOS, and Linux
  • Local file support for MP3, WAV, FLAC, M4A, MP4, OGG, and Opus
  • YouTube and SoundCloud imports
  • Direct search for YouTube songs, playlists, and SoundCloud tracks
  • Search-result previews before processing
  • Playlist imports and a persistent, reorderable job queue
  • A browser-based multitrack mixer with volume, mute, solo, and VU meters
  • Waveform navigation, zooming, and loop regions
  • Playback-speed and pitch-transposition controls
  • Automatic BPM, key, scale, LUFS, and peak analysis
  • A generated click track that follows the song
  • Custom mix, loop-region, individual-stem, ZIP, and video exports
  • A persistent local library with folders and search
  • A mobile-friendly interface accessible over the local network through a QR code
  • Docker and Unraid support
  • An in-app updater and nine interface languages

The backend uses Python, FastAPI, Demucs, FFmpeg, yt-dlp, librosa, and Web Audio. The desktop shell is built with Tauri. Processing happens on the user's machine, and audio is never uploaded to a StemDeck service. There are no accounts, advertisements, subscriptions, credits, quotas, or telemetry. StemDeck is licensed under Apache 2.0, and I intend to keep it free and open source. It is still alpha software. Separation quality depends on the source material, CPU processing can be slow, and there are undoubtedly edge cases I have not encountered. Feedback, bug reports, architectural criticism, and contributions are all welcome.

thclpr (thread)

Stream deck Steam deck Stem deck

We really suck at naming things...

nubinetwork (thread)

I got excited about an open source steam deck...

newsomix9xl (thread)

This is incredibly cool. I tried a few songs and it was pretty accurate. Really useful.

magicmicah85 (thread)

This is just a wrapper of htdemucs, if anyone's wondering if it was a new/better model.

ipsum2 (thread)


Run Qwen3.8 27B locally: real numbers from my Mac Studio

129 points · 98 comments · by speckx

Benchmark chart showing Qwen3.8 27B token speeds across quantization levels

The author benchmarks Qwen3.8 27B, a dense multimodal local model with hybrid attention, on a Mac Studio M3 Ultra to evaluate its real-world performance and hardware requirements. While the new model generates at half the token speed of its Qwen3.6 predecessor (~14 vs ~28.6 tok/s), it requires roughly half the output tokens per answer, resulting in nearly identical wall-clock completion times. The article also tests a highly compressed 1-bit quantization that runs quickly on minimal RAM but sacrifices decisiveness and tool-calling reliability. Ultimately, the model proves highly suitable for privacy-focused background automation tasks, provided users update their inference runtimes to support the new qwen35 architecture.

Interesting Points
  • Runtime compatibility requires recent builds; older versions of llama.cpp or Ollama will fail to load the model with an unknown model architecture: 'qwen35' error.
  • Hardware scaling shows that a 16GB mini PC can run the 1-bit or 2-bit quants, while 32GB is needed for the default Q4_K_M, with higher-end Strix Halo or Mac systems required for Q8 and BF16 variants.
  • During generation on the M3 Ultra, the GPU cores max out at 100% utilization drawing roughly 64W, while the CPU remains nearly idle at 6W.
  • Testing Unsloth's 1-bit quant reveals that while factual recall remains intact, the model struggles with decisiveness, often cycling through alternatives without committing to a final answer, which aligns with the developer's warning against using it for tool-calling.
  • Community benchmarks on AMD's Strix Halo platform estimate the Q4_K_M quant can reach 20.4 tok/s generation and 292 tok/s prompt processing, offering a viable non-Apple alternative to Apple silicon.
Top Comments

Qwen3.8 27B (Q4_K_M, 17GB) generates at ~14 tokens/s on my Mac Studio M3 Ultra ~14 tokens/s For anyone reading that has never ran local llms, please understand that anything under 100 tok/sec is worthless. You are faster typing stuff into Gemini free version that you get with a google account and copy/pasting it in (and you can easily build browser automation with playwright or any other js runtime to have this available in a chat window)

ActorNightly (thread)

Apart from learning, I cant see the point of spending that kind of money and energy to get such awfull token generation speed. Assuming memory bandwith is the bottleneck, is it just a matter of time until we start to see hbm4 based chip able to run qwen3.8 for normal people running at more than 500 token / seconds? Is memory speed the only technological bottlenecks that prevent us from having fast local model?

mickael-kerjean (thread)

The local LLM scene needs a Draw Things equivalent for Mac. Too much fiddle for things that doesn't make sense (Qwen 3.8 27B should be exactly the same speed as Qwen 3.6 27B). It feels like that I am teasing (I am the author of Draw Things) something, because it is.

liuliu (thread)


vLLM v0.28.0

93 points · 31 comments · by mrrrcs

vLLM released version 0.28.0, continuing its work as a leading open-source inference engine for large language models. The release brings updates to the framework used by many companies running open models at scale, though community feedback highlights ongoing stability challenges with newer model architectures.

Interesting Points
  • The release continues to be the go-to inference engine for running open models at scale across H200, B300, and RTX 6000 hardware.
  • Community reports indicate ongoing stability issues with newer models like DeepSeek-V4-Flash, where different versions exhibit different types of output corruption.
  • Users note that staying on the bleeding edge often requires out-of-tree patches, especially for newly released models.
Top Comments

I love vLLM, but damn if it isn't frustratingly buggy.

I was recently running DeepSeek-V4-Flash on a B300. On v0.26 it was totally broken, and I had to add three out-of-tree patches to fix it. I updated to v0.27 -- no patches necessary now, but the output is now broken as it randomly starts responding with garbage (repeated token loops). On my workstation where I run Gemma-4 on an RTX 6000 the whole process tends to get stuck and stops responding, and needs to be killed and restarted to start working again. On my friend's 4x RTX 6000 box where he runs DeepSeek-V4-Flash high concurrency also triggers some kind of a bug where it spews out garbage, but this time it's not a single repeated token and looks like this: (this is copy-pasted from what the model did output, genuinely looks like it was in pain trying to end its thinking trace but not being able to)

Don't know if it's just my (and my friends') bad luck or what, but in every single release something is critically broken, and it's not like we're using niche models or hardware. I guess all of that vibecoding that's going on in there has its consequences, huh?

kouteiheika (thread)

I was hoping to see the reasoning_content mess get robustly fixed, but all we got was this doc change: https://github.com/vllm-project/vllm/pull/50624

joshheitzman (thread)

Still way behind on LLM sampler support compared to llama-cpp. Where's support for top-n-sigma? for DRY? for XTC? C'mon guys!

Der_Einzige (thread)

Did some loadtests on vllm, managed to crash it :-)

zoobab (thread)

I just wish they'd support Pascal :(

Nvidia might have given up support but it doesn't mean vllm have to (llama.cpp didn't).

SillyUsername (thread)


The growing divide between AI hype and software engineering reality

59 points · 74 comments · by jruohonen

Featured image for the article

The article argues that a growing number of open-source projects and platforms are implementing strict bans or heavy guardrails on AI-assisted contributions due to fundamental mismatches between LLM capabilities and software engineering requirements. Rather than representing genuine intelligence, the author contends that LLMs exploit human psychological tendencies and information asymmetry, flooding maintainers with unverified, flawed code that wastes senior developers' time and stifles mentorship. While acknowledging LLMs as useful tools, the piece emphasizes that current benchmark scores mask significant real-world error rates, making human oversight and original craftsmanship essential for reliable engineering.

Interesting Points
  • A review of 120 open-source projects found that 37 have adopted total AI bans, with major projects like GCC, QEMU, SDL, Gentoo, Zig, and Ghostty explicitly rejecting AI-assisted submissions.
  • Current state-of-the-art models score just under 77% on SWE-bench and approximately 50% on Humanity's Last Exam, underscoring that automated code generation remains highly unreliable for production engineering.
  • Linux kernel maintainer Greg Kroah-Hartman publicly stated that even the best current LLMs produce results that are flat out wrong or harmful in at least one-third of cases.
  • The author identifies information asymmetry as the core friction point, where inexperienced developers use AI to bypass learning, causing senior maintainers to halt mentorship to avoid wasting time on unreviewable submissions.
  • Platforms like Codeberg, Sourcehut, and Flathub have expanded AI restrictions beyond code to include documentation, bug reports, and review comments to prevent the spread of AI slop.
Top Comments

I think this post (and the OSS projects that he mentions that ban AI) are very reactionary.

But the idea that AI has or will surpass humans any time soon in either capabilities or efficiency is simply not true

AI is already better than most developers. I'm not sure what alternative reality people are remembering, but human coders for the most part have been really awful at writing code. I think the average PR from an LLM is head and shoulders above the average PR from a human. Does it write code in the preferred style and architecture of the project maintainer 100% of the time? No, and neither did humans.

I think there are many legitimate criticisms of AI, but "they suck at coding" isn't one of them. The progress we've seen in the last couple of years alone suggest that very soon they will be better at coding than any person. As a coder of over 30 years, I've embraced this fact and come to terms with it. Leverage your knowledge of systems, software engineering and product design and you can be living in a golden era for software development. That's how it feels to me at least.

slowin (thread)

I generally agree with this. One of the strangest things about LLM driven engineering is holding two seemingly contradictory positions in your head: they’re both better than the median developer, and they’re also much worse at producing artifacts that are comprehensible to humans.

I often find myself throwing away large amounts of LLM driven code not because it’s bad, but because it doesn’t fit within my attention span. The code itself looks very reasonable, passes tests, benchmarks well, etc. But I throw it away because the models don’t yet “explain” their decisions in ways that elicit psychological safety. Humans are still very good at that, even when their engineering is worse.

woodruffw (thread)

This conversation again?

They go nowhere because people are using wildly different definitions and contexts. There's one already in here about how ai is better than humans at coding.

  • Yes llms are better at the mechanics of coding

  • no they're not good enough for overall software dev.

  • yes, this stuff should've been automated years ago in frameworks and in libs, or through sane programming langs that dealt with memory and logic flow better.

  • yes, they're much more useful for documentation, search, etc. than they are at actual coding

  • no, your stats aren't useful - 90% of coding is meaningless if you've also massively increased the amount of slop produced

  • yes, llms do make you more productive overall, whether it's 10-30% or 1000% is context dependent

  • yes and no that AI will change everything; no it doens't make sense to keep comparing pre-ai and post-ai worlds, it is very likely that the gains cancel each other out and we all just move up a layer of abstraction, and end up in a simlar situation to now.

  • no we don't know what will actually happen to the job market, things can remain irrational longer than you can remain solvent. We've had the technology to be where are 20-30 years ago if we were focused as a society. Things take time, and real world is complicated.

preommr (thread)

The problem is that skill at coding is not exactly the same thing as skill at developing and maintaining software, and AI can help there as well, but a swarm of cowboy coder agents will get you to a legacy codebase very very quickly.

And even if the AI is better than most humans, the speed means that you get more defects and issues! If a human developer has a change failure rate of say 10%, (1 in 10 changes causes a defect or issue), and AI is twice as good and only introduces bugs 5% of the time, but submits 10x as many changes, then you go from 1 bug per unit of time to 5 bugs per unit of time, so your velocity is up 10x but your defect rate is up 5x...

datadrivenangel (thread)

I really want to agree but the arguments he brings up make that extremely hard

Also, it seems that many don’t want to learn but instead expect to have all understanding outsourced to LLMs. Many seniors have noticed this and have stopped teaching juniors as the seniors don’t like the feeling of having their time wasted by teaching people who don’t want to learn.

Or may be it is because now a junior dev is expected to deliver to output of a senior?

Also stop saying “please” to an LLM. It does not have any feelings.

Yes, but I still prefer a nice tone. Like why should I change my manners just because it has no feelings? If anything the statistic predicts a friendlier answer when I say "please".

Again, I recommend people try running small LLMs locally where temperature and other settings are fully exposed and configurable to see this themselves. It is a good antidote to falling for the illusion that LLMs would actually be intelligent.

It's like recommending someone to buy the cheapest Lenovo Thinkpad to prove that Lenovo sucks.

However, the best models still have a pass rate of only about 50% on the Humanity’s Last Exam.

Haha, as if he (or really most people) even would understand 50% of those questions. I find it rather mind blowing that it's possible to put such diverse knowledge into a couple of TB. Or may be I'm just an idiot and it's common knowledge, "how many paired tendons are supported by the sesamoid bone of hummingbirds within Apodiformes".

LLMs are not a scam, but a useful tool and technology that has its uses. But the idea that AI has or will surpass humans any time soon in either capabilities or efficiency is simply not true

He's not wrong that LLMs are just useful tools but isn't it the purpose of a tool to surpass human capabilities and efficiency? Like even a bicycle makes traveling more efficient than just walking and a car has the capability to transport more items than any human. And its know more than two decades since computer surpassed human capabilities in chess. If a tool is neither more capable nor efficient, it's just a useless tool.

I mean I get his point that GenAI is to some degree over hyped but his arguments just dont hold in my opinion.

ma2kx (thread)


Warp builds self-improving agents on Claude

55 points · 54 comments · by shenli3514

Warp blog header image

Warp has implemented a self-improving agent architecture on the Claude Platform by leveraging file-based Agent Skills to capture and compound human feedback over time. Instead of relying on static prompts or session-based memory, the system uses two distinct skills: a base skill for domain-specific instructions and a scheduled improver skill that analyzes past feedback to propose targeted edits to the base. These updates flow through standard code-review workflows, ensuring human oversight while allowing agents to iteratively refine their outputs across tasks like code review and issue triage. This approach transforms one-off agentic helpers into compounding systems that adapt to team-specific conventions and reduce noisy, low-quality interactions.

Interesting Points
  • Warp processes 400K+ Claude Code sessions per week inside its terminal, accumulating 40M total agent conversations to date.
  • The architecture explicitly separates procedural domain knowledge stored in stable skill files from auto-generated inference-time memory to prevent uncontrolled state drift.
  • The outer improver skill operates on a schedule rather than per-task, using bundled scripts to pull feedback signals and draft mergeable PRs for base skill updates.
  • The team emphasizes that feedback quality outweighs volume, noting that a few highly detailed comments from senior engineers can be more valuable than mass binary ratings.
  • To maintain signal quality, the system assumes human feedback will occasionally be wrong and requires source filtering and final human approval before any skill file is merged.
Top Comments

Agents need to handle recurring tasks reliably and effectively

This core problem remains unsolved. The solution presented in the article with Human In The Loop and some skill-magic such as "Write principles, not rules etc." is unsatisfactory because it offers no guarantees whatsoever. I find it difficult to harness agents into deterministic workflows which need to produce reliable outcomes.

bwfan123 (thread)

What if it turns out the real AGI was the SKILL.md files we made along the way?

themgt (thread)

I've already been playing with something similar locally where the agent updates the review skill if human reviewers make valid criticisms of the code which the agent failed to detect.

01100011 (thread)

I was bit confused in the beginning thinking its some product from Anthropic, looks like Warp is the startup, most likely getting rebate on using Claude and providing functionality to users, trying to get them addicted to the feature. And Anthropic is the one thats doing marketing for them cause eventually its their LLM which is being used. Not sure about the agents but this arrangement is definitely increasing the value of both companies in circular fashion.

sandeepkd (thread)

I already knew what Warp is (I switched to Ghostty and haven't looked back), but I find it odd that the "The quick pitch" card at the top of this article makes no mention of what the company actually does. Who cares more about their founder/growth/age over that?

JLO64 (thread)


LLMs are making me lose my savviness

51 points · 65 comments · by me2too

Author photo of Paolo Galeone

Paolo Galeone argues that while large language models dramatically accelerate software prototyping, they are actively eroding his practical engineering skills and professional satisfaction. He contends that the iterative process of prompting, evaluating, and fixing AI-generated code bypasses the hands-on mistake-making that traditionally builds deep technical comprehension. Furthermore, he warns that corporate pressure to adopt these tools without rigorous human oversight will likely increase technical debt rather than deliver genuine productivity. Ultimately, he fears that developers are surrendering their hard-won expertise to model trainers without gaining the underlying skills in return.

Interesting Points
  • He defines professional "savvy" as practical shrewdness gained specifically through debugging and iterative problem-solving, rather than consuming pre-packaged explanations or summaries.
  • When he corrects an LLM's mistake, the provider uses that interaction to fine-tune their model, meaning he will never encounter that specific error again and permanently loses the chance to retain the knowledge.
  • Setting up a local inference machine remains the only genuinely engaging part of his AI workflow, standing in stark contrast to the boredom of routine prompt-and-evaluate cycles.
  • Modern LLMs can now replicate his standard code output when given upfront guardrails and design documents, yet still fail to provide the cognitive reward and engineering challenge of actual implementation.
Top Comments

It's like every time we discuss this on hn we have to go back to basics.

Builders/makers can be roughly subdivided into two camps: some like building for the final products; others like building for the process itself.

I'm in the latter camp. OP probably too. You probably are in the former.

And that's fine. But let's just stop pretending the other side doesn't exist.

klez (thread)

Prior to AI, I'd spend hours debugging and figuring how to make something work. It felt exciting in the end; the journey not so much. It was frustrating sometimes, and the overall output was not great. Sometimes I couldn't try out all of my ideas simply because I had no capacity to do it. Anything requiring multiple months of work, I'd get burned out and never finish anything.

Now I delegate all the grinding to AI. I still feel accomplishment when I get the final result. But more importantly, I can now build something in couple of weeks that would otherwise take me half a year. I can focus now less on the for-loop vs while-loop and more on the big picture, like keeping things tidy and separation of concerns. The front-end and how end-users will interact with what I build is now more important to me, as well as the design. Previously, I had brain capacity only for writing my clever backend algorithm. Now I can make an equally clever front-end for it.

Maybe we never enjoyed the grind? We just came to accept it and convinced ourselves to enjoy it, because there was no other way. If you wanted something cool, it meant you had to put in hours. Now you just need to word it correctly and get the prerequisites.

zerof1l (thread)

Begging the question here. Author is aware that they can choose not use LLMs and they... don't? It's like living at walking distance from town, being used to going in and around on foot, then electric scooters became available, so they start using them to get around while complaining that they aren't getting the exercise they want anymore.

skeledrew (thread)

What are you talking about lmao, tons of carpenters have said that. The subjective experience of your craft is shaped by the tools you chose to use. For some people, and I venture this is most often true for master craftspeople, not only is the journey is more important than the destination, but the limitations of the path breed the creativity needed to even arrive at the destination.

thot_experiment (thread)

I've experienced that great feeling of "this is a great idea" coming out of nowhere while doing unrelated activities, and having to rush back at my desk to write it down and implement it. That was great - it was rewarding, it was really meaningful.

This is it for me. It's a pretty incredible tool but it killed the vibe and challenge of building things.

cliche (thread)


35 more Hacker News stories

Reddit Stories

Delivery robots using humans to cross the street

1328 points · 174 comments · r/singularity · by u/japie06

Delivery robots using humans to cross the street

A video showing delivery robots using pedestrians to cross the street, highlighting the unpredictable behavior of autonomous systems in shared spaces.

Top Comments

If these companies get big enough they will likely pay the city to integrate wireless push of crosswalk button for these robots

u/Prudent-Sorbet-5202 (249 points · permalink)

socialising the costs, privatising profits. A little humorously, but technically true.

u/psichodrome (236 points · permalink)

That is not how I imagined Ex_Machina.

u/anycept (88 points · permalink)


The worst thing about ChatGPT

1218 points · 231 comments · r/ChatGPT · by u/shadex07

The worst thing about ChatGPT

A user posted an image generated by ChatGPT's 5.6 Sol model at max effort depicting a yellow car that turned into taxi yellow in the second response, sparking a discussion about AI sycophantism and the uncanny valley in AI image generation.

Interesting Points
  • The image was generated using ChatGPT's 5.6 Sol model at max effort settings.
  • The second response changed the car color to taxi yellow, which users found more realistic but less desirable.
  • The top comment received 760 points with a humorous take on what 'max effort' might entail across datacenters.
Top Comments

https://preview.redd.it/1uheh325y1mh1.jpeg?width=1170&format=pjpg&auto=webp&s=5c996b2bd9e178a4b006569bd0bd189c828f275d

5.6 Sol Max effort. Admittedly in a project though, so not clear context

Edit: everything is default for characteristics

u/MeruOnline (760 points · permalink)

Max effort

I just imagined how this went down.

- Multiple datacenters cross states got spun up in red alert with flashing red messages of "MAX EFFORT REQUEST - ALL HANDS ON DECK - POWER CRITICAL"

- Panic phone calls flying left and right

- At the local power plant, people in hard hats running around crazy with sirens going off, their donuts still in their mouth, giant switch switch being pulled, sparks flying, powerplant meltdown imminent

- Local dam is opened up to flood the area for cooling, water bombers dumping water directly on the roof

- The red phone at the president's office rings, Moscow trying to make sure it is not an immediate attack.

- Seismic readings across the world, tsunami warning in Japan

- Single dos prompt with cursor blinking at the end waiting for user prompt, everybody holding their breath

SYSTEM READY_

"yella, or more dark yella?"

u/FischiPiSti (329 points · permalink)

Technically, people are like this. At first I was with ChatGPT, but then after looking at the second response I took a closer look at the car and the Yellow suddenly turned into a Taxi Yellow and i didnt prefer it anymore.

u/DinoZambie (389 points · permalink)

Yeah, I can see why. Sycophantism is probably the most realistic option. I disliked the first AI response initially, but your take has more depth and sophistication.

u/Necessary-Sugar7513 (178 points · permalink)


the fuh

1217 points · 68 comments · r/ChatGPT · by u/No_Refuse_4241

the fuh

A meme post that has resonated with the ChatGPT community, likely referencing a recent AI development or model behavior.

Top Comments

Crack the code😏

u/PaleProgrammer6476 (133 points · permalink)

These fake posts are boring.

u/JRubenC (130 points · permalink)

What does "I'll let you crack Siri" even mean?

u/GrenadineBombardier (52 points · permalink)


Moderna stock, $MRNA , surges over +110% after announcing the first ever positive Phase 3 results for a personalized cancer vaccine.

1121 points · 118 comments · r/singularity · by u/Fantastic-Emu-3819

Moderna stock, $MRNA , surges over +110% after announcing the first ever positive Phase 3 results for a personalized cancer vaccine.

Moderna stock surged over 110% after announcing the first-ever positive Phase 3 results for a personalized cancer vaccine, a major milestone in AI-assisted drug development.

Top Comments

We cured cancer before gta 6

u/Famous-Reach-6730 (348 points · permalink)

Moderna being called MRNA is fucking hilarious i love it

u/Head-Needleworker849 (239 points · permalink)

So far this result is for melanoma, but there is a decent hope that this type of treatment to be effective against a larger variety of cancers. (though melanoma is uniquely suited to it).

The somewhat unfortunate news is that this type of treatment is inherently expensive, think in the order of magnitude of ~150k per person, so unless there is further huge developments in efficiency not cost effective for the whole world.

u/Dangerous-Sport-2347 (160 points · permalink)

Mapping the human genome was crazy expensive 30 years ago, it's like dirt cheap now. Same can happen here hopefully

u/das_war_ein_Befehl (124 points · permalink)

Almost like they planned it

u/flyingflail (111 points · permalink)


Robot taunting opponent

1019 points · 63 comments · r/singularity · by u/kernelangus420

Robot taunting opponent

A video of a robot taunting its opponent during a competition, showcasing advances in robotic behavior and social interaction.

Top Comments

robots dancing better then me... RIP

u/RafyKoby (90 points · permalink)

For sure somebody's programming a teabag movement at this moment.

u/AndalusianGod (65 points · permalink)

Eugenic robots?

u/Senorbob451 (25 points · permalink)

That balancing on 1 leg is something

u/etadude (24 points · permalink)

In 5 years, robots will be dancing after killing you.

u/Kurk_Lazaris (29 points · permalink)


Apparently you can get Minimax H3 Max to run faster than real time, someone made a Rick and Morty interdimensional cable stream (but it keeps getting taken down)

778 points · 140 comments · r/singularity · by u/TFenrir

Apparently you can get Minimax H3 Max to run faster than real time, someone made a Rick and Morty interdimensional cable stream (but it keeps getting taken down)

A community member reports that Minimax H3 Max can run faster than real time, and someone has created a Rick and Morty interdimensional cable stream using the model. The stream keeps getting taken down, highlighting the ongoing tension between AI-generated content and platform moderation policies.

Interesting Points
  • Minimax H3 Max can run faster than real time, enabling real-time interactive applications.
  • Someone created a Rick and Morty interdimensional cable stream using the model.
  • The stream keeps getting taken down, highlighting tensions between AI-generated content and platform moderation.
Top Comments

had this same idea, so glad somebody did it, this is sick

u/SanoKei (180 points · permalink)

Morty’s voice turned into Rick’s.

u/Gandalfthebran (98 points · permalink)

Morty sounds to much like Rick. Code bullet did this a few years ago when the tech was not ready, endless r&m episodes on twitch, the voices were better but the video was based on fixed assets on a game engine, I wonder what it would be like now

u/throwaway275275275 (62 points · permalink)

Could someone explain what I’m seeing? I’ll give a pointless Reddit award for the help

u/BackendSpecialist (60 points · permalink)

Welcome to the multiverse

u/Fragrant-Hamster-325 (64 points · permalink)


Trump says NASA is building a nuclear-powered starship set for a 2028 Mars mission

777 points · 343 comments · r/singularity · by u/Distinct-Question-16

Trump says NASA is building a nuclear-powered starship set for a 2028 Mars mission

Trump announced that NASA is building a nuclear-powered starship set for a 2028 Mars mission, marking a significant acceleration in space exploration timelines.

Top Comments

he can say anything I wont believe him

u/liebebio (667 points · permalink)

"essentially unlimited fuel", "don't have to fill up the tanks every so many miles"

He should stick to the teleprompter....

u/code_the_cosmos (245 points · permalink)

They objectively are working on it, it was announced in March. It's a scientific mission, not like a manned spacecraft.

The House appropriations committee and the chair of the Senate subcommittee for NASA funding are pushing to fund it, the Presidential budget ignored it entirely and the administration is currently futzing around with management structures at NASA.

So ironically Trump is actually the biggest force working against this project right now.

https://www.nasa.gov/mission/space-reactor-1-freedom/

u/JoshAllentown (216 points · permalink)

Sure grandpa, let's go to bed

u/FeDeKutulu (79 points · permalink)

I'm pretty sure he's referring to the SR-1 mission NASA is planning to launch in 2028

u/kabekew (162 points · permalink)


You're out of mana! Take this!

662 points · 70 comments · r/ChatGPT · by u/Watermelon_Sherbert

An AI-generated image of a cat giving a potion to a fantasy character

A humorous AI-generated image showing a cat offering a potion to a fantasy character who has run out of mana, playing on RPG mechanics in a whimsical crossover between gaming and pet culture. The post generated significant engagement for its creative blend of fantasy tropes and internet cat culture.

Top Comments

I thought kitties brought her a Dyson.

u/I_am_Ledger (156 points · permalink)

What the fuck?

u/lofgrenator (68 points · permalink)

One less tree planted

u/MahatmaGandhi01 (47 points · permalink)

Very kind of that dragon to patiently wait while she "raises her mana".

u/AnthropoidCompatriot (36 points · permalink)

AI is going to cure cancer….

Well it would cure cancer…

But we choose to use it for this instead

u/koulourakiaAndCoffee (24 points · permalink)


A startup found a drug to make your blood young. People close to the company are already taking the drug weekly. Benefits include improved vision in a 64-year-old female, longer landscaping sessions for a 59-year-old man, longer badminton games, improved hand grip, better erections than with Viagra

631 points · 126 comments · r/singularity · by u/ilkamoi

A startup found a drug to make your blood young. People close to the company are already taking the drug weekly. Benefits include improved vision in a 64-year-old female, longer landscaping sessions for a 59-year-old man, longer badminton games, improved hand grip, better erections than with Viagra

A biotech startup has developed a blood rejuvenation treatment that early adopters within the company are already using weekly. Anecdotal benefits reported include improved vision in a 64-year-old woman, increased stamina for physical activities, improved hand grip strength, and enhanced erectile function surpassing Viagra. The treatment has not yet undergone peer-reviewed clinical trials, and the specific compounds remain undisclosed, but the anecdotal evidence has generated significant excitement in the longevity community.

Interesting Points
  • People close to the company are already taking the drug weekly, reporting improvements across multiple health markers.
  • Reported benefits span vision improvement, physical stamina, hand grip strength, and erectile function.
  • No peer-reviewed evidence has been published yet — the claims are based on anecdotal reports from company insiders.
  • The treatment appears to combine existing generic drugs rather than introducing a novel compound.
Top Comments

Longer badminton games??? This is revolutionary!

u/badumtsssst (435 points · permalink)

Seems all they do is package two already existing generic drugs and sell it as an anti age package. Likely oxytocin paired with an Alk5/TGF-β pathway inhibitor.

A combination of those could give the effect described. So it isn't a scam per se as it could work, just nothing revolutionary.

u/SwePolygyny (180 points · permalink)

No peer-reviewed evidence only marketing

Though I'm still kinda hyped, what if it's true?

u/Midnight_Minaaa (99 points · permalink)

You jest, but clearly you have never played badminton with a racket strapped to your erection.

u/CiegoDiego (227 points · permalink)

gif

u/almostsweet (59 points · permalink)


Tencent compressed Hy4-preview from 1.5TB to about 200GB GGUF and kept about 98% performance.

620 points · 98 comments · r/LocalLLaMA · by u/RedditUsr2

Tencent compressed Hy4-preview from 1.5TB to about 200GB GGUF and kept about 98% performance.

Tencent has successfully compressed the Hy4-preview model from 1.5TB down to approximately 200GB in GGUF format while retaining about 98% of its original performance. This represents a significant achievement in model compression and demonstrates the potential for running very large models on more accessible hardware.

Interesting Points
  • Tencent compressed Hy4-preview from 1.5TB to approximately 200GB in GGUF format.
  • The compression retained about 98% of the original model's performance.
  • The achievement demonstrates the potential for running very large models on more accessible hardware.
Top Comments

WTF! That's insane. Someone test this lol.

u/shy_monkee (139 points · permalink)

I posted the same thing earlier, but it got caught in the Reddit filter. Maybe direct X link is not allowed here?

Anyway, It implies two things IMHO:

  • The future of local models is brighter than expected. We can still compress them further.
  • Hy4 has not yet been sufficiently (post-)trained. Its official release will achieve significantly high scores on benchmarks.

u/cometkim (109 points · permalink)

Awesome. Only 190 GB more to go and then I will run it on my RTX 3080.

u/RickyRickC137 (100 points · permalink)

If the reported numbers hold up, that's not just quantization, that's making a previously absurd model genuinely practical.

u/GasSmooth7439 (4 points · permalink)


203 more Reddit stories

Updates: 05:30 AM PDT · 08:30 AM PDT · 11:30 AM PDT · 02:30 PM PDT · 05:30 PM PDT