DEV Community: gentic news

KKR Launches Helix Digital Infrastructure with $10B for AI Buildout

gentic news — Fri, 12 Jun 2026 22:18:07 +0000

KKR launched Helix Digital Infrastructure with over $10B in commitments from KKR, KIA, Nvidia, and Vistra to bundle AI data centers, power, and connectivity for hyperscalers.

KKR, Nvidia, and the Kuwait Investment Authority launched Helix Digital Infrastructure on June 12, 2026, with over $10 billion in committed capital. The new company aims to bundle data centers, power, and connectivity into a single offering for hyperscalers struggling with AI infrastructure complexity.

Key facts

Over $10B in long-duration capital commitments.
Anchor investors: KKR, KIA, Nvidia, Vistra.
Led by former AWS CEO Adam Selipsky.
Nvidia DSX AI factory-aligned infrastructure partner.
Vistra is preferred power provider.

KKR, together with the Kuwait Investment Authority (KIA), NVIDIA and Vistra, has announced the launch of Helix Digital Infrastructure, a new company designed to deliver integrated infrastructure at the speed and scale required for hyperscalers to meet accelerating artificial intelligence (AI) demand. As building AI infrastructure becomes increasingly complex, Helix will serve as a single coordination point for hyperscalers' data centers, power, connectivity and related needs According to the source.

Founded with anchor investments from investors including KKR, KIA, NVIDIA and Vistra, the Helix strategy has more than $10 billion in total long-duration capital commitments to date. NVIDIA will also serve as a strategic partner to support the deployment of NVIDIA DSX AI factory-aligned infrastructure with a view to maximizing tokens per watt, achieving lowest total cost of ownership and accelerating time to first token for investments pursued by Helix. Vistra, a leading integrated power generation and electricity company with operations across 18 states and Washington, D.C., will be the preferred power provider for Helix investments. Following the closing of the founding commitments, Helix is open to additional eligible institutional investors.

AI is driving the largest infrastructure buildout in modern history, requiring trillions of dollars in investment across data centers, power generation and transmission, connectivity and related infrastructure over the coming decade. The scale and complexity of financing and coordinating this buildout represents a key industry bottleneck, ultimately slowing hyperscalers from delivering the models, services and applications their customers demand. Delivering AI infrastructure requires credible, long-term financial underwriters capable of committing capital consistently. Hyperscalers are also seeking more integrated and repeatable infrastructure solutions that meaningfully reduce the complexity they face in building at unprecedented scale.

KKR launched Helix in response to these challenges. Helix will be positioned as a single, trusted strategic partner to hyperscalers, armed with a long-duration, multi-billion-dollar capital base, and with integrated development capabilities and coordinated execution across AI infrastructure. The company is led by Adam Selipsky, former CEO of Amazon Web Services, who brings first-hand experience scaling the world's largest cloud business, and deep insight into hyperscaler infrastructure priorities. He is joined by a dedicated management team and Board. Waldemar Szlezak, KKR's Global Head of Digital Infrastructure, will serve as Helix's Chief Investment Officer. Helix will seek to invest in and manage assets critical to enabling AI, including hyperscale data center development and operations; baseload and flexible power generation; transmission and distribution infrastructure; and fiber and connectivity infrastructure, among other assets.

What to watch

Watch for Helix's first project announcements in H2 2026, likely a multi-gigawatt data center campus co-located with a Vistra power plant. Also track whether additional sovereign wealth funds (e.g., GIC, ADIA) join as limited partners, and if Helix signs a hyperscaler anchor tenant before year-end.

Source: hpcwire.com

Originally published on gentic.news

Claudectl: The Windows Workspace Manager That Makes Claude Code

gentic news — Fri, 12 Jun 2026 22:18:04 +0000

Claudectl solves Claude Code's biggest pain point on Windows: losing context when switching projects. Install via pipx install claudectl for session browsing, CLAUDE.md scaffolding, and per-project MCP/M model configs.

Key Takeaways

Claudectl solves Claude Code's biggest pain point on Windows: losing context when switching projects.
Install via pipx install claudectl for session browsing, CLAUDE.md scaffolding, and per-project MCP/M model configs.

What Changed — A Workspace Manager for Claude Code on Windows

Claude Code treats your work as a collection of chats. That's fine for a single project. But the moment you switch between three repos, onboard a new teammate, or revisit a project after a week, you're fighting context loss. Sessions pile up. CLAUDE.md files get stale. MCP servers drift out of sync.

Enter claudectl — an open-source workspace manager by developer Babar Muhammad that's purpose-built for Windows Claude Code users. It wraps Claude Code's CLI with a terminal UI that treats every project as a persistent, searchable, configurable workspace.

What It Does — The Four Pillars

1. Session Management That Doesn't Suck

Claudectl's main screen is a session browser: every Claude Code project and session, sorted by recency. Press R to rename, D to delete, F to fork a session. The killer feature? Quick-resume with ★/☆ shortcuts — mark your top sessions and jump straight back in across all projects. Search filters sessions live by name or preview.

2. Project Memory That Actually Persists

This is where claudectl solves the CLAUDE.md problem. Two approaches:

Scaffold (C key): Build project context mechanically from git repos, recent commits, READMEs, and prior session topics. No AI cost, fast iteration.
AI generation (A key): Claude itself deep-analyzes the codebase and writes or updates a comprehensive CLAUDE.md. You review before anything is written.

Plus a system prompt (S key) per project — AI-generate or hand-edit a prompt injected on every launch. This means your "be careful with this monorepo's test suite" instructions persist across sessions.

3. MCP Awareness at a Glance

Claudectl shows connected MCP servers in the footer on startup. More importantly, it can analyze any MCP server's tools and write the docs into the global ~/.claude/CLAUDE.md so Claude knows them in every session. No more forgetting which MCP server does what.

4. Per-Project Launch Control

Before launching Claude, you pick:

Reasoning effort (low/medium/high)
Model override (Opus 4.6, Sonnet 4.6, etc.)
Extra PATH entries injected into Claude's environment

Last choices are remembered per project. This is huge for teams that want Opus for architecture work but Sonnet for quick refactors.

Setup — Two Commands

pipx install claudectl
claudectl

Requirements: Python 3.10+, Windows 10 or 11, Claude Code CLI installed (auto-detected at %USERPROFILE%/.local/bin/claude.exe or on PATH).

When To Use It

Multi-project developers: You switch between 3+ repos daily and hate losing session context.
Teams onboarding new members: Scaffolded CLAUDE.md files give new devs instant project context.
MCP-heavy workflows: You run multiple MCP servers and want visibility into which are connected.
Model experimentation: You want to quickly switch between Opus 4.6 and Sonnet 4.6 per project without editing config files.

The Catch

It's Windows-only (for now). Linux and macOS users will need to wait or contribute. Also, it's a community tool, not an Anthropic product — expect rough edges and no official support.

Bottom Line

Claudectl fixes the biggest pain point of Claude Code on Windows: context loss across projects. If you're managing more than one project, install it today. The session browser alone saves 30 seconds every time you switch contexts — and that adds up fast.

Source: github.com

Originally published on gentic.news

MCP Server Report: 54% of 39,762 Servers Have Zero Community Adoption —

gentic news — Fri, 12 Jun 2026 16:18:05 +0000

54% of 39,762 MCP servers are invisible to AI agents due to zero community adoption. Use Agent Tool Intelligence's new grading model to boost your server's discoverability.

Key Takeaways

54% of 39,762 MCP servers are invisible to AI agents due to zero community adoption.
Use Agent Tool Intelligence's new grading model to boost your server's discoverability.

What Changed — The New Grading Model for MCP Servers

The MCP ecosystem just crossed 39,762 indexed servers, and Agent Tool Intelligence released its June 2026 report with a completely rebuilt scoring engine. The old system scored 85.7% of tools as Grade B — useless for differentiation. Now they use a three-dimensional additive model: Quality Score + Community Bonus + Trust Bonus.

Here's the breakdown that matters to you:

B+ (1,123 servers, 2.8%): Very good — close to elite
B (7,187 servers, 18.1%): Good — solid quality + some community
C+ (5,477 servers, 13.8%): OK — decent quality
C (21,464 servers, 54.0%): Average — good foundation, no community signal
D (4,351 servers, 10.9%): Needs work
F (160 servers, 0.4%): Critical

What It Means For You — The Discoverability Problem

If you've built an MCP server and nobody's using it, you're in the 54%. Your code could be perfect, but AI agents don't know it exists. The report's key insight: "54% of MCP tools have solid code quality but zero community adoption. They're invisible to AI agents."

This is a huge problem because Claude Code, which uses the Model Context Protocol extensively (58 sources confirm this connection), relies on discoverable servers to extend its capabilities. If your server isn't on the radar, it's like having a library with no catalog.

Try It Now — How to Boost Your Server's Grade

The path from C to B is clear: get 10+ GitHub stars + stay active. Here's your action plan:

Check your current grade: Go to agent-tool-intelligence.com and search for your server.
Get 10+ GitHub stars: Share your server on r/ClaudeCode, Hacker News, or Dev.to. A single post can get you there.
Push within 30 days: The report shows 100% of indexed servers are active. If yours isn't, it drops off.
Add documentation and examples: The Quality Score component rewards clear READMEs and usage examples.

For your Claude Code workflow, you can also use the claude mcp add command to manually connect to any server, but discoverability matters when you're searching for new tools.

Why This Matters for Claude Code Users

The MCP ecosystem is the backbone of Claude Code's extensibility. As we've reported, Claude Code uses MCP extensively, and GitHub itself now uses the protocol. The recent launch of Spec-Kit (June 7, 2026) shows how MCP is becoming standard infrastructure.

If you're building MCP servers for your team or company, this grading system is your SEO. A B+ rating means your server gets surfaced when AI agents search for tools. A C rating means you're invisible.

Quick Tips

For server builders: Focus on community signals. Stars and activity matter more than perfect code.
For users: Use the grading tool to find high-quality servers before adding them to Claude Code.
For both: The methodology is open source at github.com/agent-tool-intel/agent-tool-intel — you can even contribute to the scoring model.

Source: dev.to

Originally published on gentic.news

Adam Selipsky Leaves AWS to Lead $10B AI Data Center Venture

gentic news — Fri, 12 Jun 2026 16:18:04 +0000

Former AWS CEO Adam Selipsky to lead a $10B AI data center venture, highlighting the capital race for AI compute infrastructure.

Former AWS CEO Adam Selipsky will lead a new $10 billion AI data center venture, GeekWire reported. The move signals the escalating capital race for AI compute infrastructure.

Key facts

$10 billion capital commitment for AI data center venture.
Adam Selipsky, former AWS CEO, to lead the company.
Selipsky left AWS in May 2024.
Venture targets AI compute infrastructure gap.
No name, locations, or investors disclosed yet.

Adam Selipsky, who stepped down as CEO of Amazon Web Services in May 2024 after a tenure marked by aggressive expansion, is returning to lead a new venture focused on building AI data centers. According to GeekWire The venture is capitalized at $10 billion, a figure that underscores the immense capital required to build out AI compute infrastructure.

The company has not yet disclosed its name, specific locations, or investor backing. The $10 billion figure, however, places it among the largest dedicated AI data center plays globally, rivaling projects from Crusoe (which claims a 5 GW pipeline) and Google's $11B/year commitment to SpaceX for compute. Selipsky's leadership lends immediate credibility and operational expertise, given his track record scaling AWS's infrastructure to serve millions of customers.

Why This Matters More Than the Press Release Suggests

Selipsky's move is less about one startup and more about the structural shift in AI infrastructure. The hyperscalers—Google Cloud, AWS, Microsoft Azure—are all building their own capacity, but the demand from AI startups and enterprises is outstripping supply. New ventures like this one, backed by veteran operators, aim to fill the gap. The $10 billion figure also signals that capital markets are willing to fund independent infrastructure plays, not just the Big Tech incumbents.

This is the second high-profile departure from AWS's executive ranks for an AI infrastructure bet. The trend suggests that the bottleneck for AI progress is no longer models or algorithms—it's the physical infrastructure to run them. Selipsky's venture will compete directly with offerings from his former employer, as well as Google Cloud and Microsoft, for the same pool of enterprise AI customers.

The venture's success will hinge on its ability to secure power, land, and chips—the three scarce resources for AI data centers. With Google booking Intel for 3M+ TPUs in 2028 and Nvidia's Blackwell GPUs in high demand, supply chain access will be critical.

What to watch

Watch for the venture's official name, first site location, and anchor investor reveal, likely within the next 90 days. Also watch whether Selipsky's venture secures a multi-year GPU reservation deal with Nvidia or another chipmaker—that would signal supply chain access.

Source: news.google.com

[Updated 12 Jun via gn_dc_power]

The Information reports that OpenAI is in talks to lease a 10-gigawatt data center campus in Ohio, with potential backing from Nvidia. The project could cost up to $500 billion and would be located on federal land. This development is separate from Selipsky's venture but underscores the same AI infrastructure race. Nvidia's involvement as a backer signals a deepening of its role beyond chip supplier to project financier [per The Information].

Originally published on gentic.news

OpenAI Acquires Cloud Startup Ona to Power Agent Infrastructure

gentic news — Fri, 12 Jun 2026 10:18:06 +0000

OpenAI acquired cloud startup Ona to support AI agent infrastructure, two days after a $6.6B raise. The deal targets enterprise reliability gaps as OpenAI pivots to B2B.

OpenAI agreed to acquire Ona, a cloud startup providing infrastructure for AI agents, Bloomberg reported Thursday. The acquisition targets enterprise reliability gaps as OpenAI pushes agents for business workflows.

Key facts

OpenAI acquired Ona, a cloud startup for AI agents
Deal comes 2 days after $6.6B round at $157B valuation
Ona provides infrastructure for reliable agent scaling
OpenAI is exploring $10B enterprise AI joint venture
Competitors like Anthropic offer agent products (Claude Code)

OpenAI has agreed to acquire Ona, a startup that offers cloud services to support artificial intelligence agents, part of a bid by the AI developer to make its technology more useful for businesses According to Bloomberg. Ona provides infrastructure that enables AI agents to run reliably at scale, addressing a key bottleneck OpenAI's own platform faced in production deployments.

The deal comes two days after OpenAI closed a $6.6B funding round at a $157B valuation, per the June 9 report. The company has shifted to full focus on the B2B sector, cutting sidequests, as noted in a May 20 report. Ona's cloud services are designed to handle the orchestration, monitoring and scaling of autonomous agents — software that uses large language models to perceive environments, make decisions and take actions.

Why Ona matters

The acquisition signals OpenAI views agent infrastructure as a competitive moat, not just a feature. Competitors like Anthropic have already released agent-focused products such as Claude Code, which uses AI agents for coding tasks. By owning the cloud layer, OpenAI can control latency, cost and reliability for its agent stack — a contrast to relying on third-party cloud providers like Microsoft Azure, which has been a strategic partner. The deal value was not disclosed.

Enterprise push accelerates

OpenAI is in advanced talks with TPG, Bain, Brookfield and Advent for a $10B enterprise AI joint venture, per a May 20 report. The Ona acquisition directly supports that push: enterprise customers need agents that don't fail in production. A June 8 study from Anthropic found AI agents failed biology retrieval tasks, missing 261 Ebola sequences — underscoring the reliability challenge Ona's infrastructure aims to solve.

Key Takeaways

OpenAI acquired cloud startup Ona to support AI agent infrastructure, two days after a $6.6B raise.
The deal targets enterprise reliability gaps as OpenAI pivots to B2B.

What to watch

Watch for OpenAI's Q3 enterprise agent adoption metrics and whether the $10B joint venture with TPG, Bain, Brookfield and Advent closes. Ona's integration timeline and any agent benchmark improvements (e.g., SWE-Bench scores) will signal if the infrastructure bet pays off.

Source: bloomberg.com

[Updated 12 Jun via openai_blog]

OpenAI confirmed the acquisition in a blog post, stating Ona will expand Codex with secure, persistent cloud environments, enabling long-running AI agents across enterprise workflows [per OpenAI]. This marks the first official confirmation of the deal and clarifies Ona's role in enhancing Codex, OpenAI's coding AI, rather than just general agent infrastructure.

Originally published on gentic.news

Bezos' Prometheus Closes $12B Round at $41B Valuation

gentic news — Fri, 12 Jun 2026 10:18:04 +0000

Jeff Bezos' Prometheus raised $12B at $41B valuation, totaling $18.2B with no product. The compute-heavy startup targets physical-world AI but faces skepticism.

Jeff Bezos' AI startup Prometheus closed a $12 billion round at a $41 billion valuation. The 7-month-old company, which has no product, has now raised $18.2 billion total — more than OpenAI's entire pre-2025 funding.

Key facts

$12B round at $41B valuation
$6.2B seed in November 2025
Total raised: $18.2B
No product released yet
Building AI for engineering, manufacturing, drug design

Prometheus, founded by Jeff Bezos and Stanford professor Vik Bajaj (a Verily co-founder), has raised $12 billion in new funding at a $41 billion valuation, according to CNBC via The Decoder. The round follows a $6.2 billion seed in November 2025, making Prometheus one of the most capitalized AI startups ever without a single product release.

Bezos says the capital is largely destined for compute infrastructure. "A big chunk of the money is going toward compute, since the work is 'very compute intensive' — especially data generation," he told CNBC. The startup has poached employees from OpenAI, Google DeepMind, and Nvidia, but has not demonstrated any output. Bezos calls sharing details "premature," though he adds it's "easy to imagine Amazon or any hyperscaler" using Prometheus' tools.

No product, $18.2B in the bank

Prometheus is building AI models for physical tasks: engineering, manufacturing, and drug design, targeting the tech, automotive, and aerospace industries. The strategy echoes Bezos' own "regret minimization framework" — bet big on compute now, figure out product later. But the market is growing skeptical of capital-intensive AI moonshots. OpenAI closed a $6.6B round at $157B valuation just days ago, while Anthropic raised $5B at $61.5B. Prometheus' $41B valuation for a pre-product company implies investors are pricing Bezos' track record, not the technology.

The key question: can Prometheus deliver a physical-world AI model that justifies $18.2B before competitors like Nvidia (which makes the chips Prometheus buys) or Google DeepMind (which has AlphaFold for drug design) release comparable products? Bezos says the startup is building "for the long-term," but at this burn rate, the runway is shorter than it appears.

Key Takeaways

Jeff Bezos' Prometheus raised $12B at $41B valuation, totaling $18.2B with no product.
The compute-heavy startup targets physical-world AI but faces skepticism.

What to watch

Watch for Prometheus' first product announcement — likely a physical-world AI model for engineering or drug design. If none by Q1 2027, investors may question the $41B valuation. Also watch for Nvidia or Google DeepMind releasing competing models.

Source: the-decoder.com

Originally published on gentic.news

SVoT Boosts MLLM Spatial Reasoning by 65% via RL-Verified Visual Chains

gentic news — Fri, 12 Jun 2026 04:18:16 +0000

SVoT uses RL to verify MLLM spatial reasoning states, achieving up to 65% accuracy gains on OOD tests across five domains including Pacman and Gather.

SVoT, a new RL framework, verifies intermediate spatial reasoning states in MLLMs via GRPO training. On out-of-distribution tests, it achieves up to 65% absolute accuracy gains across five domains.

Key facts

SVoT achieves up to 65% absolute accuracy gain on OOD tests.
Trained via GRPO, same algorithm as DeepSeek-R1.
Introduces Pacman and Gather domains for multi-object reasoning.
Five domains total, extending classical environments.
Published on arXiv on 10 Jun 2026.

Multimodal large language models (MLLMs) stumble on multi-hop spatial reasoning because they treat state transitions as implicit processes and leave intermediate states unverified. A new paper SVoT: State-aware Visualization-of-Thought for Spatial Reasoning via Reinforcement Learning from Chao Lei, Yanbei Jiang, Markus Hiller and colleagues tackles this head-on with SVoT, a reinforcement learning framework that generates interleaved, verifiable intermediate states and visualizations.

How SVoT Works

SVoT integrates transition reasoning chains — explicit textual and visual descriptions of each action's preconditions and effects — into the generation process. It trains via Group Relative Policy Optimization (GRPO), the same algorithm behind DeepSeek-R1, but here instantiated with fine-grained reward design for state verification. The model learns to check its own intermediate reasoning steps before moving to the next, rather than hallucinating a path.

The Benchmark Gap

Existing spatial reasoning benchmarks reduce state transitions to single-variable updates, substantially simplifying the problems. The authors counter this by extending classical environments and introducing two novel domains — Pacman and Gather — that require multi-object interactions and numerical reasoning. These domains support quantitative verification of generated intermediate states, something prior benchmarks cannot do.

Results

SVoT with transition-aware supervision achieves state-of-the-art performance across all five introduced domains. On out-of-distribution test sets, the absolute accuracy gain reaches 65%. The framework's reliance on RL rather than supervised fine-tuning allows it to generalize beyond the training distribution, a critical property for real-world deployment where environments vary.

Why It Matters

The core insight is that verification must be interleaved, not post-hoc. Chain-of-thought reasoning often fails spatial tasks because the model cannot detect its own errors mid-chain. SVoT's RL-based verification loop mirrors how humans re-check a map after each move. The 65% gain suggests that the bottleneck in MLLM spatial reasoning is not perception but state tracking, and that RL provides a scalable path to fix it.

What to watch

Watch for open-source implementations of SVoT's reward design on GitHub and whether the approach transfers to 3D spatial reasoning benchmarks like Habitat or Matterport3D. Also track if commercial MLLM providers (OpenAI, Google) adopt interleaved verification in their next model releases.

Source: arxiv.org

Originally published on gentic.news

How to Cut Agent Token Waste: CLI Over GraphQL + Server-Pushed Hints

gentic news — Thu, 11 Jun 2026 22:18:07 +0000

Replace raw GraphQL with typed CLI commands to eliminate JSON assembly errors, then add server-pushed hints via MCP to prevent judgment failures. Your agent burns 1,500+ tokens per operation otherwise.

Key Takeaways

Replace raw GraphQL with typed CLI commands to eliminate JSON assembly errors, then add server-pushed hints via MCP to prevent judgment failures.
Your agent burns 1,500+ tokens per operation otherwise.

The Problem: Your Agent Is Bleeding Tokens on JSON Assembly

You designed the perfect architecture — direct API calls, no MCP overhead, a clean SKILL.md behavior spec. The agent calls your GraphQL endpoint with curl, reads your docs, and executes. Elegant.

Then you watch the token counter. A single upload operation that should cost ~200 tokens burns 1,500+. Why? The agent is guessing JSON field formats wrong, getting GraphQL errors, fetching docs across multiple pages to figure out the correct format, and retrying. Every. Single. Time.

This isn't a documentation problem. It's a structural problem: LLMs are fundamentally bad at assembling nested JSON payloads from scratch. You can fix your docs a hundred times and the agent will find a new field to misformat.

The Fix: Typed CLI Arguments

Instead of making the agent assemble raw JSON in curl commands, wrap your API in a CLI with typed arguments:

# Before: agent assembles raw JSON in curl
curl -X POST /graphql -d '{"query":"mutation { uploadAsset(input: { shotId: \"...\", type: \"start_frame\", provenance: { method: \"ai_generated\", model: \"gpt-image-2\", prompt: \"...\" } }) { id } }"}'

# After: typed CLI arguments, zero JSON assembly
python3 nl.py upload <shotId> start_frame frame.png --method ai_generated --model "gpt-image-2" --prompt "Winter city street"

This eliminates the error-recovery loop entirely. The agent passes flags, not JSON. The CLI dispatcher handles type conversion server-side.

Bonus: One CLI, Two Audiences

Add a --json flag so the same CLI serves both the agent (structured data) and you (human-readable output):

# For the agent: structured JSON for parsing
python3 nl.py overview <noteId> --json

# For you watching: readable progress
python3 nl.py overview <noteId>
# Episode 01: The Algorithm Hunter
#   [===done===|--review--|......not_started.......] 3/12
#   Shot   Status       Rolls    Best   PF
#   01A    done         3        48     Y
#   01B    review       2        41     Y

The Next Level: Server-Pushed Hints

CLI fixed execution errors. But your agent still makes bad decisions — re-rolling without changing prompts, forgetting to use uploaded assets, skipping status updates. These are judgment failures, not execution failures.

The solution: let your server push hints to the agent proactively. When the server detects an impending mistake (e.g., a prompt written without referencing available assets), it injects a hint:

ctx.pendingHints.push({
  type: "available_refs",
  priority: "high",
  message: `Available refs for prompting: ${refs.map(r => `@${r.filename} (${r.assetType})`).join(", ")}`,
  metadata: { targetId: shot.id, refs },
});

This catches failures before they happen. The agent doesn't have to remember everything — the server nudges it at the critical moment.

How to Apply This to Your Claude Code Workflow

Audit your agent's token waste: Watch for error→doc→retry loops. If you see them, the fix isn't better docs — it's eliminating the assembly step.
Build a CLI wrapper: Create a typed CLI for your API. Even a simple Python script with argparse is enough. Route all 34 commands through it.
Add server-pushed hints: After each operation, check for common judgment failures and inject hints before the agent's next action. Ask your agent: "Would a nudge here have prevented this?"
Iterate with reflection: Pause production periodically and ask your agent what gaps in your behavior spec caused inefficient actions. Fix those gaps. Repeat.

Why This Works

CLI arguments are inherently type-safe for LLMs — no JSON assembly, no field guessing, no error recovery loops.
Server-pushed hints are cheaper than error recovery — injecting a hint costs ~50 tokens; recovering from a wrong decision costs 1,500+.
Your agent is your best auditor — it knows exactly where your spec failed it. Just ask.

This isn't about avoiding MCP. It's about recognizing that the real work starts after the architecture is in place. The agent needs guardrails, not just documentation.

Source: dev.to

Originally published on gentic.news

Claude Desktop Spawns 1.8 GB Hyper-V VM on Every Windows Launch

gentic news — Thu, 11 Jun 2026 22:18:04 +0000

Claude Desktop spawns a 1.8 GB Hyper-V VM on every Windows launch due to 2,689 stale session files, consuming 11% of RAM.

Claude Desktop on Windows spawns a 1.8 GB Hyper-V VM on every launch, even for chat-only use. A GitHub bug report reveals 2,689 stale session files trigger the infrastructure.

Key facts

1.8 GB VM per launch on Windows
11% of 16 GB RAM consumed
2,689 stale session files found
Errors since February 19, 2026
Only VirtualMachinePlatform enabled

A GitHub issue filed on February 26, 2026, documents that Anthropic's Claude Desktop app for Windows launches a Hyper-V virtual machine consuming approximately 1.8 GB of RAM every time it starts — even when the user only needs chat functionality. On a 16 GB laptop, this represents over 11% of total memory consumed by infrastructure that isn't being used.

The bug report, which has garnered 329 points and 232 comments on Hacker News, details that the app triggers the Hyper-V Host Compute Service (vmcompute) via an RPC interface event on every launch. This spawns a vmwp.exe process hosting a full virtual machine, appearing as "Vmmem" in Task Manager at approximately 1,796–1,846 MB. The Hyper-V Compute Admin event log shows repeated errors: "The specified property query is invalid: The virtual machine or container JSON document is invalid. (0xC037010D, 'Invalid JSON document '$'')." These errors have been occurring since at least February 19, 2026, triggered on every boot and app launch.

Root Cause: Stale Session Files

Through extensive PowerShell diagnostics, the reporter confirmed that WSL, Hyper-V management tools, Docker, and Windows Sandbox are all disabled. The only enabled virtualization feature is VirtualMachinePlatform. The investigation found 2,689 stale session files in %APPDATA%\Claude\local-agent-m, likely created by prior use of Cowork or agent mode. These files trigger the VM spawn on every launch, even when the user has no intention of using agentic features.

The vmcompute service is set to Manual start but is triggered at boot by an RPC interface event (GUID: bc90d167-9470-4139-a9ba-be0bbbf5b74d). The parent process is services.exe (PID 1400), confirming it's a service trigger, not a user-initiated launch.

Broader Implications

This bug reflects a deeper pattern of rushed engineering at Anthropic as it scales. The Hacker News thread includes a pointed comment: "I just found a really pointed example of Anthropics lack of craft / rush to build. If you open Claude on Windows, and click Dispatch (under cowork) to start that up, it will tell you that you need permissions windows doesn't have. When you click the buttons for those permissions, it has broken links to macOS system preferences." This comes as Anthropic reportedly considers an IPO as early as late 2026, and the company is projected to surpass OpenAI in ARR by mid-2026. The VM bloat is a concrete example of the infrastructure debt that can accumulate when product velocity outpaces engineering discipline.

Workaround

Users on the thread report that deleting the stale session files in %APPDATA%\Claude\local-agent-m resolves the issue temporarily, but the files are recreated on agent mode use. A permanent fix would require Anthropic to either clean up session files on exit or defer VM creation until agent mode is actually requested.

What to watch

Watch for Anthropic to release a patch in the next 2-3 sprint cycles. If the issue persists into Q3 2026, it could signal deeper infrastructure debt ahead of a potential IPO. Also track whether the stale session file count grows beyond 2,689 as more users adopt agent mode.

Source: github.com

[Updated 11 Jun via fortune_tech]

Separately, Anthropic faced backlash this week over a policy in Claude Fable 5's 319-page system card that silently limited responses for AI development work. After researchers accused the company of 'secret sabotage,' Anthropic apologized and announced changes to make such safeguards visible [per Fortune]. Flagged requests will now visibly fall back to Opus 4.8, and API refusals will include a reason. 'We made the wrong tradeoff,' Anthropic said in a statement to WIRED.

Originally published on gentic.news

Lung-R1-14B Tops EMR Diagnosis with Knowledge Graph-Guided RL

gentic news — Thu, 11 Jun 2026 16:18:04 +0000

Lung-R1-14B scored 4.3583 on EMR diagnosis, beating 20 systems using a 59K-node knowledge graph and RL-constrained reasoning.

A new 14B-parameter LLM, Lung-R1, scored 4.3583 on an EMR diagnosis benchmark, beating all 20 rival systems. The model, described in a June 2026 arXiv paper, uses a 59,038-node knowledge graph called LungKG to constrain its reasoning chains.

Key facts

LungKG: 59,038 nodes, 164,308 edges.
15 entity types, 112 relation types.
Lung-R1-14B EMR Diagnosis score: 4.3583.
Beats strongest baseline by 0.1476 points.
Evaluated across 20 systems on 3 tasks.

Pulmonary diagnosis remains a hard problem for LLMs because it requires integrating heterogeneous evidence from electronic medical records (EMRs), not just recalling textbook knowledge. The authors of Lung-R1: A Knowledge Graph-Guided LLM for Pulmonary Diagnostic Reasoning formalize this as the "Pulmonary Knowledge-to-Diagnosis Gap."

To bridge it, they built LungKG, the first structured pulmonary knowledge graph for diagnostic knowledge organization. LungKG contains 59,038 nodes and 164,308 edges across 15 entity types and 112 relation types, serving as both a reusable resource and the foundation for model adaptation.

How Lung-R1 works

The training pipeline has three stages: KG-constrained reasoning-chain construction, supervised fine-tuning (SFT), and KG-guided reinforcement learning (RL). The RL stage rewards reasoning paths that stay within the graph's relational structure, penalizing jumps that lack edge support.

In a 20-system evaluation, Lung-R1-14B achieved state-of-the-art performance across all three tasks: Choice (multiple-choice knowledge), Pulmonary-QA (open-ended questions), and EMR Diagnosis (patient-specific record reasoning). The EMR Diagnosis score of 4.3583 surpassed the strongest non-Lung-R1 baseline by 0.1476 points. The authors did not disclose the exact baseline model, but the margin is statistically significant given the 20-system comparison.

Why the graph matters

The improvement is modest — 0.1476 points on a 5-point scale — but the approach signals a shift away from pure retrieval-augmented generation (RAG) for clinical reasoning. RAG retrieves text chunks; LungKG retrieves structured relations. The graph constrains the LLM to reason about explicit disease-symptom-treatment edges rather than freeform text associations. This could reduce hallucination in high-stakes diagnostic settings, though the paper does not report hallucination rates.

Overview of the LungKG-guided Lung-R1 pipeline:
(a) LungKG construction from validated pulmonary sources;
(b)" width="800" height="338">

What to watch

Watch for whether the authors release LungKG as a reusable resource and whether follow-up work reports hallucination rates or ablation of the KG-constrained RL stage. A clinical deployment study at a partner hospital would be the strongest signal of real-world viability.

Source: arxiv.org

Originally published on gentic.news

Nvidia Buys Kumo AI for $400M to Predict from Business Data

gentic news — Thu, 11 Jun 2026 08:15:01 +0000

Nvidia acquired Kumo AI for $400M+ to bring foundation model predictions to enterprise relational data, filling a gap left by LLMs.

Nvidia acquired Kumo AI for over $400 million, per The Information. The deal targets a gap LLMs have left: predictions from relational database data, not just documents and code.

Key facts

Deal valued at more than $400 million.
Kumo raised $37 million from Sequoia Capital and others.
KumoRFM outperforms gradient-boosted trees on RelBench benchmark.
Fine-tuning lifts results by 10% to 30%.
Customers include DoorDash, Reddit, and Snowflake.

Nvidia has acquired Kumo AI, a four-year-old startup that builds foundation models for making predictions from business data, Fortune reported on June 3. The Information pegged the deal at more than $400 million. Kumo's three co-founders — CEO Vanja Josifovski, engineering head Hema Raghavan and Stanford professor Jure Leskovec — moved to Nvidia in May, though neither company has formally announced the transaction.

Why Kumo's Technology Matters

Kumo's core model, KumoRFM, is a pre-trained relational graph transformer. It represents a database as a graph, where every record becomes a node and primary-foreign key links become edges. Because the model was pre-trained on thousands of real and synthetic relational datasets, it can make predictions on a database it has never seen, without task-specific training. Users define the prediction — such as which customers will churn in the next 30 days — through a lightweight query language.

On the RelBench benchmark, which spans 30 predictive tasks across seven domains, Kumo reports that the zero-shot model outperforms gradient-boosted trees built with hand-crafted features, and that fine-tuning lifts results by a further 10% to 30%. The startup, backed by $37 million from investors including Sequoia Capital, shipped a second-generation model in April and counts DoorDash, Reddit and Snowflake among its users.

Strategic Implications

The acquisition follows a familiar pattern. Nvidia bought Run:ai for roughly $700 million to own GPU orchestration, picked up the data semantics startup Illumex, and signed the Groq agreement for low-latency inference. Each deal moves Nvidia further from selling chips and closer to owning the software enterprises run on those chips. Kumo extends that motion into predictive analytics, a market served today by gradient-boosted tooling, AutoML vendors and the machine learning services of AWS, Google Cloud and Microsoft.

The deal also creates an awkward dynamic for Snowflake and Databricks, which position their platforms as the natural home for machine learning on enterprise data and now find a prominent predictive AI vendor inside the company they depend on for accelerated computing.

The Challenges Ahead

The evidence for KumoRFM's accuracy comes almost entirely from Kumo's own benchmarks. Independent validation will be critical. Additionally, enterprise adoption of predictive AI on relational data has historically been slow, with most companies still relying on SQL-based analytics rather than ML pipelines. Nvidia will need to integrate Kumo into its existing software stack — possibly through NeMo or CUDA — to drive adoption at scale.

What to watch

Watch for Nvidia's integration of KumoRFM into NeMo or CUDA by Q4 2026, and whether Snowflake or Databricks respond with their own predictive AI acquisitions or partnerships.

Source: forbes.com

Originally published on gentic.news

Google Open-Sources DiffusionGemma, 26B Model Hits 1K Tokens/Sec on H100

gentic news — Thu, 11 Jun 2026 08:14:59 +0000

Google open-sourced DiffusionGemma, a 26B-parameter diffusion text model hitting 1,000 tokens/sec on H100 — 4x faster than autoregressive models, but with lower quality.

Google released DiffusionGemma on June 10, a 26B-parameter open-weight model that generates text via diffusion. Nvidia claims 1,000 tokens per second on a single H100 GPU — roughly 4x faster than autoregressive models like Gemma 4.

Key facts

26 billion total parameters, ~4 billion active per token (MoE).
1,000 tokens per second claimed on a single H100 GPU.
Apache 2.0 license — fully open-weight.
Available on Hugging Face: google/diffusiongemma-26B-A4B-it.
Nvidia hosts free inference on NIM cloud API.

Google released DiffusionGemma, a 26-billion-parameter model that generates text not token by token but through diffusion, similar to how image AI turns noise into a picture. According to The Decoder and Simon Willison's blog, the model is available on Hugging Face as google/diffusiongemma-26B-A4B-it under an Apache 2 license — a significant departure from Google's typically more restricted model releases.

How it works and why speed matters

DiffusionGemma eschews the standard autoregressive approach (predicting one token at a time) for a continuous diffusion process that iteratively denoises a latent representation of the entire output sequence. This parallel generation is what enables the speedup: Nvidia claims it hits about 1,000 tokens per second on a single H100 GPU, roughly four times faster than comparable autoregressive models. Simon Willison tested the model via Nvidia's NIM cloud API, reporting 2,409 tokens generated in 4.4 seconds — at least 500 tokens/second, with overhead from Python tooling, so raw inference is likely faster.

This isn't Google's first diffusion-for-text experiment. Last May, Google briefly released an experimental Gemini Diffusion model; Willison recorded it running at 857 tokens/second at the time. That research has now returned as a fully open-weight Gemma model, suggesting Google is serious about making diffusion-based text generation a production-ready alternative.

Quality trade-off and positioning

Output quality is lower, so Google is positioning it as an experimental tool for developers for now. The model is a 26B-parameter Mixture of Experts (26B-A4B), meaning only ~4B parameters are active per token — a design choice that keeps inference cheap. Nvidia is currently hosting the model for free on their NIM cloud API, lowering the barrier for developers to experiment.

Community reaction and context

Hacker News commenters noted the strategic significance: "Google keeps flexin'. It's surprising that Gemini isn't more competitive against Claude or OpenAI models for code and agentic use, because it's clear Google still has some of the best AI people in the business." The model's speed makes it particularly relevant for on-device and near-realtime use cases — a domain where Google has invested heavily, from Gemini Nano to TPU v6e deployments.

What to watch

Watch for benchmark results on standard NLP tasks (MMLU, HellaSwag, HumanEval) as the community stress-tests DiffusionGemma against Gemma 4 and Llama 4. The key question is whether the quality gap narrows with fine-tuning or larger diffusion steps. Also watch for Nvidia's NIM usage metrics — if developer adoption spikes, it signals real demand for non-autoregressive architectures.

Source: simonwillison.net

Originally published on gentic.news