Everything in UI5
Type: 2
Domain
Origin
Signals
More
Group by: Capability
Distributed through
Installs into
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
VS Code extension to serve, proxy, build and deploy UI5 projects
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
SAPUI5 extension for Visual Studio Code
Its README assumes a `manifest.json` with an app ID, JavaScript files that start with `sap.ui.define`, and access to ui5.sap.com to preload the standard library metadata. It says of TypeScript that ts-morph, its parser there, has drawbacks, and that not all linters work for TypeScript.
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
VS Code extension generating OData mock data from service metadata
VS Code side bar view of the SAPUI5 and OpenUI5 API reference
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.