GitHub Introduces Project HydraFusion: Runtime Multi-Model Orchestration That Builds a Workflow Per Coding Task in Copilot CLI
GitHub's Project HydraFusion research preview builds per-task multi-model workflows (Single, Cascade, Critique) in Copilot CLI, reporting +4.9 quality at 67% lower cost on TerminalBench 2.1.
Project HydraFusion is a research preview available on all GitHub Copilot plans inside Copilot CLI that treats model routing as workflow selection, choosing among Single, Cascade (draft plus quality gate), and Critique (cross-family reviewer) execution patterns per request. Against Claude Opus 5 baselines at medium reasoning, fixed HydraFusion policies cut estimated cost 67% while adding 4.9 quality points on TerminalBench 2.1, and cut cost 36% and 65% with slight quality dips on DeepSWE and CheckpointBench. Billing is per token at each underlying model's standard rate; there are no open weights or self-hosting options.
Implementation of Machine Learning Workflows with NVIDIA cuML, RAPIDS, GPU Benchmarking, Explainability, Clustering, and Model Inference
Hands-on tutorial implements NVIDIA cuML and RAPIDS to GPU-accelerate scikit-learn-style ML workflows with benchmarking, clustering, and inference.
The tutorial demonstrates NVIDIA cuML as a GPU-accelerated machine learning framework, using cuml.accel to speed up unmodified scikit-learn scripts with zero code changes and the native cuML API for CuPy/cuDF interoperability. It benchmarks CPU versus GPU implementations of PCA, K-Means, nearest-neighbor search, logistic regression, random forests, and DBSCAN on datasets up to 200,000 samples with 64 features. It also builds GPU pipelines with UMAP, t-SNE, and HDBSCAN, validates GPU-generated SHAP explanations, uses the FIL library for forest inference, and covers model serialization and GPU/CPU portability.
NVIDIA Open-Sources OSMO: One YAML Orchestrates Physical AI Training, Simulation, and Robot Testing
NVIDIA open-sourced OSMO, a Kubernetes-native YAML orchestrator running physical-AI training, simulation, and robot testing across mixed GPU tiers.
OSMO (Apache-2.0, latest release 6.3.1) lets teams describe training, simulation, and hardware-in-the-loop pipelines in a single YAML and routes tasks across datacenter GPUs (GB200), workstation RTX hardware, and edge devices like Jetson AGX Thor. It ships Helm charts and containers on NGC, uses the KAI Scheduler with NVLink topology-aware placement, and includes RBAC, OAuth2, and TLS termination. NVIDIA says it is battle-tested on GR00T, Isaac Lab, Isaac Sim, and Isaac ROS, and integrates with Claude Code, OpenAI Codex, and Cursor agents.
Rebuilding AUTOMATIC1111 with Gradio Workflow
Hugging Face demonstrates rebuilding the AUTOMATIC1111 Stable Diffusion web interface using its Gradio Workflow framework.
Hugging Face published a post showing how to rebuild the AUTOMATIC1111 Stable Diffusion WebUI experience with the Gradio Workflow framework. The article body was unavailable, so details beyond the title are limited, but the piece appears to be a tutorial on composing interactive AI interfaces with Gradio Workflow components.
Wire It, Run It, Deploy It: AI Workflows in Gradio
Hugging Face published a guide on wiring, running, and deploying AI workflows in the Gradio framework.
Hugging Face's blog post 'Wire It, Run It, Deploy It: AI Workflows in Gradio' is a tutorial on building AI workflows with Gradio. It covers wiring components, running applications, and deploying AI-powered apps. No security incident or vulnerability content is included.
Synthesized builds Test Data Agent to validate AI agents with production-like data
Synthesized announced a Test Data Agent that provisions production-like data and system states to validate enterprise AI agents before deployment.
Synthesized unveiled its Test Data Agent, an agentic infrastructure capability that generates, masks, and subsets production-representative data for testing AI agents under realistic enterprise conditions. It integrates with agent development, evaluation, testing, and orchestration frameworks, with purpose-built support for complex SAP estates including finance, procurement, and supply-chain workflows and ECC-to-S/4HANA transformation programs. The product runs in on-premises, private-cloud, and hybrid environments and exposes REST APIs and CI/CD triggers for repeatable validation scenarios.
Tines develops Cases to optimize automation and improve operational efficiency across the enterprise
Ask HN: How do you manage skills files?
A Hacker News thread debates whether agent skill files are worth managing, citing 2–4x output-token reductions on flagship models in one company's testing.
Commenters argue skills are stored prompts that help less-technical users compensate for weak prompting, while one participant reports company testing found skills reduce flagship-model output tokens by roughly 2–4x, a gap growing with newer models. Others note skills can bundle reusable scripts and inline commands for deterministic context building, and that harnesses now execute backticked commands before the agent sees the skill. Some argue improving model capability makes downloadable skills redundant.
GPT-6 Astra needs leaner prompts and fewer guardrails, OpenAI recommends
OpenAI's Eric Provencher advises developers using GPT-6 Astra to shorten skill descriptions, trim AGENTS.md reading requirements, relax approval rules, and define clear completion goals.
OpenAI's Eric Provencher published guidance on adapting developer setups when switching to GPT-6 Astra, arguing that overly long skill descriptions, blanket reading requirements, and rigid approval rules waste context or make the agent stop too early. Skills are Markdown prompt files whose names and descriptions enter Codex's context, and too many or conflicting skills cause truncation and wrong skill selection. He recommends selective document references in AGENTS.md, explicit permissions for safe operations like local test runs, and defining upfront what "done" means, since Astra may stop earlier than GPT-5.6 Sol even without restrictions.
Anthropic Adds Plugin Evals to Claude Code: 6 Grader Types, a No-Plugin Baseline, and a CI Gate for Skills
Anthropic ships a plugin evals workflow for Claude Code with six grader types, a no-plugin baseline arm, and a CI gate via threshold and cost flags.
Anthropic published a plugin evals workflow for Claude Code, exposed via the "claude plugin eval" command on v2.1.269+. Six grader types exist: regex, tool_used, tool_order, and file_exists are free transcript checks, while llm and baseline invoke a billed judge model. Every case runs with and without the plugin, and the delta (Δ) isolates the plugin's contribution; a Δ near zero with a failing tool_used:Skill grader indicates the skill never triggers. CI gating uses --threshold 0.8, --max-cost-usd, --trust-plugin, and --no-publish flags, with results written to a report.html under evals/results/.