The U.S. Department of Energy announced the public release of Genesis Agent Skills for the Genesis Mission on October 15. The package provides reusable instructions and workflows that AI coding tools can use in scientific work.
Meta engineers built Forum, a separate app for Facebook Groups, by placing an AI agent inside the planning, implementation, testing and verification loop. The company defined success as production-ready changes that build, pass tests and survive review, rather than the amount of code generated.
Google.org awarded a UC San Diego team $2.35 million to improve climate models and guide new ocean observations. The team plans to use AI agents alongside physics-based models and observational data.
Komprise published results from a September 2026 survey of 500 technical decision-makers. While 68% said their organizations were maturing or mature in AI, 28% said they had quantified AI return on investment. Only 7% reported that at least 70% of their data was cleaned and classified for AI; 57% said half or less was ready.
MLCommons was selected to develop the MLPerf Agents benchmark under a two-year, $3.5 million AI Efficiency Challenge supported by the U.S. National Science Foundation. The planned benchmark will measure complete workflows—not just model token serving—including the agent harness, model choice, retrieval, tool execution, orchestration, state management, failure recovery and validation.
Databricks announced its Predictive AI Functions in beta for forecasting, anomaly detection, driver analysis and prediction through SQL. The set includes an updated ai_forecast plus ai_top_drivers, ai_detect_anomalies, ai_predict_value and ai_predict_class. Functions can be called in SQL; some are also exposed through the Genie interface.
An Arm technical post dated October 13 argues that local AI requires choosing models, frameworks and processors across the whole workflow. It cites event demonstrations of a translation pipeline using more than 30 models and speech synthesis running on one Arm CPU core.
An AWS guide dated October 12 demonstrates a Ray LLM container setup on EKS that splits one LLM across two GPU nodes, running prefill and token generation separately. The post focuses on deployment and configuration.
An IBM Research explainer dated October 12 outlines methods in the llm-d framework, including cache-aware routing, KV-cache offloading, flow control and phase disaggregation. Performance figures are attributed to llm-d demonstrations cited in the post.
Alteryx and Google Cloud published an architecture example combining Live Query and BigQuery for unstructured-document workflows. Invoice PDFs remain in Cloud Storage; Alteryx authors the flow in a browser, while SQL pushdown runs transformations and reconciliation in BigQuery. Gemini AI.GENERATE extracts invoice fields in the worked example.
Microsoft said in an October 15 report that its internal Smart DRI agent supports more than 40 teams, with over 7,800 AI-assisted interactions and nearly 6,000 proactive incident notifications. The company estimates engineering time savings at 600 hours per month; the report does not disclose the calculation method.