AI coding

Everything about AI writing code: coding assistants, vibe coding, code model evals and new developer workflows.

1,196 picksRelated topicsAgents Cursor Tutorials

Latest picks

921–940 of 1,196

May 12Tuesday

Computing Life · YageMay 12, 07:00

How AI Caused and Fixed My Insomnia

The author used AI to build a HealthKit export tool and run multivariate regression, found that post-dinner AI use correlated negatively with sleep duration, and added 1 hour 40 minutes of average nightly sleep after avoiding AI for several weeks.

Why it matters: HKR-H/K/R all pass: the personal reversal is clickable, the HealthKit/regression setup adds testable detail, and sleep loss hits AI practitioners directly. Scope is anecdotal, so it stays at the featured floor.

Take

The sharp part is not that AI diagnosed insomnia; it is that AI turned “light computer use after dinner” into sustained cognitive labor. The author spent five minutes generating a HealthKit export app, pulled Apple Watch, iPhone, Withings-style health streams, then ran multivariate regression. The strongest negative correlate was the last evening AI session; after several weeks off post-dinner AI, average sleep rose by 1 hour 40 minutes.

I buy the mechanism more than the causal claim. This is one person, a few weeks, and the article does not give p-values, coefficients, or a randomized crossover. Still, every heavy agent user knows the loop: run several sessions, poll outputs, split tasks again, keep reading. There is no idle wait. Compared with YouTube or games, late-night AI looks less like screen time and more like sneaking a strategy meeting into bed.

Bloomberg TechnologyMay 12, 05:31

GitLab Says It Will Cut Jobs to Spend on Growth in the “Agentic Era”

GitLab said it will cut jobs to free up money for the market opportunity around AI agents; the RSS snippet does not disclose the number of roles, budget size, or execution timeline.

Why it matters: HKR-H and HKR-R pass: Bloomberg reports GitLab tying job cuts directly to agent investment, a strong devtools labor signal. HKR-K is weak because headcount, budget, and timing are missing.

r/LocalLLaMAMay 12, 05:17

I catalogued every way local models break JSON output and built a repair library across 288 model calls

Reddit user kexxty ran 288 structured-output calls through OpenRouter models, including Llama 3, Mistral, Command R, DeepSeek, and Qwen, and found similar JSON failure categories across local and API-only models. The MIT-licensed Python library outputguard validates against JSON Schema, applies 15 ordered repair strategies, includes 2,001 tests, and has no LLM provider dependency.

Why it matters: HKR-H/K/R all pass: 288 tests, the outputguard library, and a 15-step repair chain give practitioners reusable detail. Source is a single Reddit post, so it stays in the 72–77 featured band, not 78+.

Take

The useful part is not “local models break JSON too”; it is the boring repair layer turned into code. The summary says 288 OpenRouter calls across Llama 3, Mistral, Command R, DeepSeek, and Qwen. outputguard validates with JSON Schema, then applies 15 ordered repair strategies, backed by 2,001 tests. That is more honest than the usual “turn on function calling and ship it” advice.

I don’t buy the title’s “every way.” Reddit returned 403, so model versions, prompts, schema complexity, temperature, and failure distribution are not visible here. And 288 calls is a smoke test, not a taxonomy of structured-output failure. Still, it hits the part practitioners keep rediscovering: structured output is not a model feature once it enters an agent pipeline. It becomes I/O fault tolerance, even with OpenAI or Anthropic JSON modes.

AI HOT (Curated Pool)May 12, 04:45

Introducing Daybreak: Frontier AI for Cyber Defenders

OpenAI introduced Daybreak for cyber defenders, combining OpenAI models, Codex, and security partners; the post does not disclose pricing, launch timing, or concrete defense metrics.

Why it matters: OpenAI’s Daybreak announcement clears HKR-H/R as a security-focused product hook, but HKR-K fails: no defense metrics, access terms, or pricing. That keeps it in the 72–77 product-update band.

AI HOT (Curated Pool)May 12, 02:48

Using LLMs in Script Shebang Lines

Simon Willison demonstrates using an LLM command in a script shebang line, with fragments generating SVG, the -T option calling llm_time, and a YAML template defining Python tools to compute 2344×5252+134 and return 12,310,822.

Why it matters: HKR-H/K/R all pass: Simon Willison shows a reproducible LLM-in-shebang workflow with concrete flags. Impact stays within CLI/script automation, not a model or platform release, so it sits in the low featured band.

AI HOT (Curated Pool)May 12, 01:34

Replit launches parallel agents with support for 10 concurrent agents

Replit launched parallel agents that run up to 10 agents concurrently, with each agent holding an independent copy of the app, working on its own machine, and merging the results through an agent workflow.

Why it matters: HKR-H/K/R pass: the post gives a concrete 10-agent parallel workflow with isolated app copies and merge. This is a mid-weight dev-tool update, below a Cursor Agent-mode-scale launch, so it sits at the featured threshold.

Take

Replit is betting on concurrency, not a smarter single coding agent. The concrete hook is strong: up to 10 agents run at once, each gets an independent app copy, works on its own machine, then merges through an agent workflow. That fits UI variants, scaffolding, migrations, and isolated chores. It gets fragile fast on shared state, architecture changes, and test-coupled work.

The missing product is the merge layer. The snippet says “agent workflow” handles merging, but gives no conflict rate, rollback path, CI gate, or human approval model. Devin, Cursor, and Claude Code have all shown the same pattern: generation is rarely the last bottleneck; context boundaries and review cost are. If Replit nails task decomposition plus test-backed merging, this is useful for small teams. If not, ten agents just fail in parallel.

AI HOT (Curated Pool)May 12, 01:22

Anthropic Launches Claude Platform on AWS

Anthropic launched the Claude platform on AWS, letting AWS customers use existing authentication, billing, and committed-spend credits to access the full Claude API feature set, including hosted agents, code execution, and the Files API.

Why it matters: HKR-K and HKR-R pass: Anthropic brings Claude Platform into AWS procurement, billing, and committed spend. HKR-H is weak because this is distribution, not a model or capability launch.

The Verge · AIMay 12, 00:09

Google Stopped a Zero-Day Hack It Says Was Developed With AI

Google says GTIG found and stopped its first AI-developed zero-day exploit, and the attackers planned a mass exploitation event to bypass two-factor authentication on an unnamed open-source web-based system administration tool; the post does not disclose the tool name.

Why it matters: This hits HKR-H/K/R: Google-backed AI zero-day claim, a concrete 2FA bypass target, and clear security resonance. Missing tool name and exploit details keep it in the 78–84 band.

Take

Google’s story reads more like a security narrative upgrade than a sudden attacker capability jump. GTIG’s concrete evidence is a Python exploit with a “hallucinated CVSS score” and textbook-style formatting. The target was a 2FA bypass in an unnamed open-source web-based admin tool, planned for mass exploitation. The tool name, vulnerability details, model, and generation path are not disclosed.

I buy “LLM-assisted exploit development.” I don’t buy “AI autonomously discovered a zero-day” from this snippet. Code models have already been good at PoC adaptation, glue code, and debugging loops for a year; Claude and GPT-class systems lower the scripting bar fast. But zero-day work still depends on target knowledge, a test harness, and validation cycles. The practical signal for defenders is uglier: more mediocre exploit code at scale, with AI fingerprints that are weak evidence by themselves.

May 11Monday

AI HOT (Curated Pool)May 11, 23:16

Cog House Opens for the First Time: Scott Wu and the Rise of Cognition AI

Cognition AI disclosed internal footage of Cog House, while Devin reached $445 million in annualized revenue within 18 months of launch and the company is valued at about $25 billion.

Why it matters: HKR-H/K/R all pass because the story combines a rare Cognition AI inside look with hard Devin ARR and valuation figures. It stops below P1 because this is a profile-style reveal, not a funding, product, or model release.

Take

Cognition is no longer selling the idea of an “AI software engineer”; it is showing that enterprises pay real money for Devin. $445 million in annualized revenue within 18 months, a roughly $25 billion valuation, and named customers including the U.S. Army, Goldman Sachs, and Mercedes-Benz put it past the toy-agent bucket. Devin’s early public demos drew plenty of developer pushback for getting stuck and failing tasks, yet the product survived that backlash and landed procurement dollars.

The missing numbers matter: net revenue retention and inference gross margin. Code agents can turn revenue into token burn very fast, especially when they run long tasks with retries. Scott Wu’s IOI résumé and Cog House footage make a clean founder myth, but enterprise software renewal cycles do not grade on genius biography.

AI HOT (Curated Pool)May 11, 22:24

Pareto Code Reorders Model Selection Using Market Demand

OpenRouter says Pareto Code observes the Pareto frontier using real market demand; DeepSeek V4 Pro ranks first, followed by GPT 5.4 Mini and Gemini 3.1 Pro, while the post does not disclose the scoring formula or evaluation sample size.

Why it matters: HKR-H/K/R all pass, but the source is a single OpenRouter post with no sample size, time window, or pricing basis disclosed. It clears featured as a model-selection benchmark, not the 78+ band.

r/LocalLLaMAMay 11, 15:05

ExLlamaV3 Major Updates

ExLlamaV3 added DFlash in v0.0.31, raising Coding throughput from 59.21 t/s to 177.67 t/s; v0.0.32 optimized five models, with Trinity-Nano gaining 72.4% on 6000 Pro², while v0.0.33 adds DFlash model quantization plus bug fixes and efficiency work.

Why it matters: HKR-H/K/R all pass, but the blast radius is mostly LocalLLaMA and ExLlama users. This fits a mid-weight open-source inference update, not a same-day industry-wide story.

Xinzhiyuan · WeChatMay 11, 13:05

Largest IPO Nears, Topping SpaceX; 2028 AI Self-Iteration Countdown

Xinzhiyuan says Anthropic is considering a near-$1 trillion valuation, with ARR rising to $45 billion in five months; Jack Clark predicts a greater than 50% chance that AI systems can autonomously build better versions of themselves by the end of 2028, while the article cites a 72% Kalshi probability of an IPO announcement before November 1.

Why it matters: HKR-H/K/R all pass: the hook is sharp and the post gives valuation, ARR, and 2028 odds. Source is secondary and IPO/ARR claims lack official confirmation, so it stays in 78-84.

Take

Anthropic’s story gets dangerous because it braids three very different claims: a near-$1T valuation, $45B ARR, and Jack Clark’s 2028 self-improvement forecast. The numbers are huge, but the article does not define ARR: booked contracts, run-rate, cloud resale, committed spend, or recognized revenue. In enterprise AI, that accounting gap is where the hype hides.

Clark’s “over 50% by end-2028” claim is a serious safety forecast. Kalshi’s 72% odds for an IPO announcement before Nov. 1 is a market bet. Joining them into “Wall Street is pricing intelligence explosion” is too clean. Claude Code and enterprise workflows clearly hit developer budgets, and Anthropic has one of the strongest commercial ramps in AI. But moving from tool adoption to recursive self-improvement requires reproducible capability evidence, not a bigger financing number.

Xinzhiyuan · WeChatMay 11, 13:05

Claude Mythos Hits 50% Success on 16-Hour Tasks in METR Time Horizons

Claude Mythos Preview reached a 50% success rate on METR Time Horizons tasks that take humans 16 hours, while only 5 of 228 tasks exceeded the 16-hour range, so the article says METR lacks enough samples to quantify longer-horizon performance.

Why it matters: HKR-H/K/R all pass: the 16-hour task result is a strong hook, and the METR sample caveat adds substance. Capped at 82 because only 5 tasks exceed 16 hours, so the 2027 extrapolation is not same-day P1 material.

Take

Mythos reaching 50% success on METR’s 16-hour Time Horizons tasks is a serious capability signal. The article overdrives it into apocalypse math. The hard constraint is right there: only 5 of 228 tasks exceed 16 hours, and METR says longer-horizon measurement lacks enough samples. That proves the ruler is too short; it does not prove a 2027 singularity countdown.

The security section reads like stitched escalation. Palo Alto’s “3 weeks equals 1 year,” 25-minute attack chain, and Mozilla’s 423 Firefox fixes in April are useful hooks, but the snippet gives no test setup, baseline team size, or severity distribution. I buy the direction: agentic security work is compressing cycles fast. I don’t buy the alien-civilization framing; that’s benchmark extrapolation wearing a disaster-movie costume.

Synced · WeChatMay 11, 12:09

ICML 2026: PRISM Brings Efficient Test-Time Scaling to dLLMs

PRISM raises LLaDA-8B-Instruct on GSM8K from 67.58% to 85.30% by combining hierarchical trajectory search, partial remasking, and self-verified feedback, reducing dLLM test-time scaling cost from O(NT) toward O(N+KT) under a final candidate width K.

Why it matters: HKR-H/K/R all pass: the hook rejects brute-force scaling, the post gives GSM8K and complexity numbers, and it speaks to inference cost. Still an ICML framework paper, not a mainstream product release, so it sits in 78–84.

QbitAI · WeChatMay 11, 12:04

Math Majors in Trouble: Fields Medalist Tests ChatGPT 5.5 Pro, Gets Paper-Level Result in 17 Minutes

Timothy Gowers tested ChatGPT 5.5 Pro on additive number theory problems, where it produced an optimal quadratic upper-bound construction in 17 minutes 5 seconds, then generated a LaTeX preprint in 47 minutes; the article says arXiv rejects AI-generated content, so the result remains on Gowers’s blog.

Why it matters: All three HKR axes pass: Gowers’ first-person test, 17m05s, and a 47-minute preprint are concrete and discussable. It is not a model release, but the named experiment and math-reasoning impact put it in the must-write band.

Take

Gowers’ test punctures the low-end moat of mathematical research. ChatGPT 5.5 Pro produced a quadratic upper-bound construction in additive number theory in 17m05s, then wrote a LaTeX preprint in 47 minutes, with Gowers saying he gave no mathematical guidance. The painful detail is the problem class: Nathanson-style open problems were plausible first-paper material for PhD students, not contest puzzles.

I don’t buy the headline panic that “math majors are doomed,” but the training pipeline is exposed. On the h-fold sumset variant, the model took 16m41s to move to a subexponential bound, then 13m33s to push toward a polynomial one; Isaac Rajagopal judged the ideas basically sound. Tao’s “proof digestion” line is right, but publication, attribution, and starter-problem supply have already broken.

AI HOT (Curated Pool)May 11, 04:01

Codex autonomously completes a security audit and earns a bounty

A user instructed Codex to earn $5; Codex spent about 22 hours finding an open-source security audit bounty, submitting a valid PR, communicating with maintainers, passing GitHub verification, and ultimately receiving a $16.88 payment.

Why it matters: HKR-H/K/R all pass: a Codex agent allegedly closed a bounty loop in 22 hours with concrete money and workflow details. Single social-post evidence lacks reproducible logs, so it stays below P1.

r/LocalLLaMAMay 11, 03:25

MTP benchmark results: task type determines speculative inference speedups or slowdowns

A Reddit LocalLLaMA user ran 300+ tests on Qwen 3.6 27B MTP quants, finding coding draft acceptance at 79-89% and F16 coding speed up 171%, while Q4_K_M creative writing slowed down 9%.

Why it matters: HKR-H/K/R all pass: this is a single Reddit experiment, not a market event, but 300+ Qwen 3.6 27B MTP quantization tests give practical numbers for local inference tuning.

May 10Sunday

r/LocalLLaMAMay 10, 20:12

We tried vectors, ASTs, and brute-force context stuffing for code retrieval; LLM semantic graphs worked best

ByteBell open-sourced a code indexing system that stores per-file LLM-generated purpose, summary, business context, entities, classes, functions, keywords, and imports in a Neo4j graph, then uses full-text search instead of vector similarity, with SHA-256 diffing to reindex only changed files and keep LLM calls proportional to churn.

Why it matters: HKR-H/K/R all pass: the hook is counterintuitive, and the post gives a concrete Neo4j semantic-graph mechanism with SHA-256 incremental rebuilds. Reddit sourcing and missing metrics keep it at the 72–77 featured threshold.

r/LocalLLaMAMay 10, 19:35

I have DeepSeek V4 Pro at home

Reddit user fairydreaming ran DeepSeek V4 Pro Q4_K_M with a modified llama.cpp CUDA repo on one RTX PRO 6000 Blackwell Max-Q workstation GPU, using an 859GB model file; the shared log reports a 1M context window and 8.6 tokens per second generation speed.

Why it matters: HKR-H/K/R all pass: the hook is single-GPU local inference, with concrete file size, context, speed, and runtime path. Reddit single-source sourcing keeps it below must-write model-release territory.

Synced · WeChatMay 10, 14:03

A Framework for Mechanic-Aware Iteration in AI Game Generation

CreativeGame makes an agent write a mechanic contract before four code-generation stages, then evaluates iterations with CreativeProxyReward, two hard gates for runtime and static errors, and lineage-aware memory shared within each game evolution tree.

Why it matters: HKR-H/K/R pass, but this is a game-generation research framework without disclosed open-source status, metrics, or production adoption. It fits the 72–77 band rather than a must-write item.

Take

I buy the direction: CreativeGame drags game generation away from vibe-scored prompts and into mechanic contracts, staged code, and hard failure gates. The agent writes a mechanic contract first, then generates Skeleton, Feature, Visual, and Refinement stages. CreativeProxyReward checks structural mechanic change, novelty, runtime robustness, and static errors. Failed runs and broken loops get punished, which is exactly how you fight the usual LLM 7/10 or 8/10 self-rating inflation.

But calling this a “game designer” is premature. The examples are genuinely more mechanical than cosmetic: death echoes for Flappy Bird, programmable ink for Happy Glass, projectile storage in a Plants vs Zombies-like tower defense. The missing evidence is player-side: no playtest scores, retention, completion rate, or blind review against human designers. It proves traceable mechanic mutation. It does not prove fun.