惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

P
Proofpoint News Feed
Blog — PlanetScale
Blog — PlanetScale
GbyAI
GbyAI
C
Check Point Blog
腾讯CDC
Stack Overflow Blog
Stack Overflow Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
The GitHub Blog
The GitHub Blog
A
About on SuperTechFans
Recent Announcements
Recent Announcements
L
LangChain Blog
Microsoft Azure Blog
Microsoft Azure Blog
小众软件
小众软件
J
Java Code Geeks
博客园_首页
Jina AI
Jina AI
美团技术团队
H
Help Net Security
MyScale Blog
MyScale Blog
Engineering at Meta
Engineering at Meta
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
人人都是产品经理
人人都是产品经理
Y
Y Combinator Blog
S
SegmentFault 最新的问题

Swift for Visual Studio Code comes to Open VSX Registry | InfoWorld

Notion courts developers with a platform for AI agents and workflow automation Using continuous purple teaming to protect fast-paced enterprise environments A better way to work with SQL Server Evidence-driven workflows: Rethinking enterprise process design AWS debuts Graviton-powered Redshift RG instances to cut analytics costs First look: Lemonade serves up local AI with limitations GitLab CEO sees developer tool bill increasing 100-fold Red Hat adds support for agentic AI development What’s new and exciting in JDK 26 Kill the loading spinner with local-first data and reactive SQL A networking revolution at AWS Tokenmaxxing is super dumb How to add AI to an existing product (without annoying users) Your AI doesn’t need another database What happens when engineering teams reorganize around AI agents Python isn’t always easy When cloud giants meddle in markets 12 model-level deep cuts to slash AI training costs The best new features in Python 3.15 Teradata launches platform for enterprise AI agents moving beyond pilots Three skills that matter when AI handles the coding MongoDB targets AI’s retrieval problem Building AI apps and agents with Microsoft Foundry Designing front-end systems for cloud failure No, AI won’t destroy software development jobs Diskless databases: What happens when storage isn’t the bottleneck Vibe coding or spec-driven development? The agentic AI distraction Vibe coding or spec-driven development? How to choose Cloud providers are blinded by agentic AI
SAP’s AI promises last year? Most are still rolling out
2026-05-13 · via Swift for Visual Studio Code comes to Open VSX Registry | InfoWorld

SAP made bold promises about AI at Sapphire 2025: Knowledge Graph, Joule Studio, and AI Agent Hub would ship by the end of the year. Those tools are now technically available, but adoption has lagged, and SAP is already announcing version 2.0.

“Joule Studio adoption has been minimal compared to what we’d like,” said Manoj Swaminathan, SAP’s chief product officer for Business Suite, in a briefing ahead of this year’s Sapphire. The tool “was limited to content-based experiences,” he said. “Anytime more complex agents were involved, it had limited capabilities.”

The issue, according to SAP’s chief AI officer Jonathan von Rüden, was that SAP had favored ease of use over power in its original architecture. “People wanted to see more pro-code flexibility,” he said in an interview at Sapphire 2026. “We had gone with a low-code approach. You could give it extension points and tools, but you couldn’t touch the core of it. Now you can build a custom agent, connect it to your own GitHub.”

Customers also came with “big plans” but needed hard rules and approval gates that the original Joule Studio didn’t support natively. “What people want is agentic flows with clear gates and workflows and subagents,” von Rüden said. “Old Joule didn’t provide that. Now it’s all baked together.”

What actually shipped

Joule and AI Agent Hub are generally available, though the latter is now getting a “massive revamp” with version 2.0. The Knowledge Graph is live and has expanded beyond its original scope. Initially used for building Joule skills, it now feeds context directly to AI agents so they can “figure out how to call something dynamically,” von Rüden said.

Joule Studio, however, is still in early customer adoption; general availability is expected in the third quarter — a year behind the original target. Joule Work, the new engagement layer announced this week, isn’t expected until the second half of this year.

What’s different in 2.0

The revamped Joule Studio addresses the gaps that held back adoption. Beyond the pro-code flexibility, developers can now build with popular agent frameworks like LangGraph and AutoGen. and agents will have a native understanding of SAP’s proprietary code and data models that generic tools can’t replicate.

It’s an evolution, not a reset, according to von Rüden. “The first runs were geared toward automation,” he said. “Now agents need to bring optimization and intelligence as well.” Customers, including Ericsson, Mercado Libre, and Siemens, are already using Joule agents in production.

Meanwhile, SAP is rethinking how it gets AI tools into customers’ hands. Joule Desktop, launching this week, lets individual users build automations without going through IT — a bet that grassroots adoption will move faster than centralized rollouts.

This article first appeared on CIO.