ABAP已解锁的AI代理开发——任何启用ADT的系统，7.50以上。 可用表面因版本而异，vsp compat 会根据系统报告：RAP 需要 S/4，AMDP需要HANA，而S/4上的一些ADT资源在ERP中缺失。

蒸汽朋克家族的一部分： open-steamgate（一个可以克隆的ABAP应用服务器）， abapiti（TypeScript 和 WASM 转为 ABAP）， Open-RFC-GO（RFC）和 Open-Diag-Go（SAP 图形界面诊断）。

ADT ↔ MCP Bridge：赋予 Claude（及其他 AI 助手）对 SAP ADT API 的完全访问权限。 阅读、编写代码、调试、部署、运行测试——所有这些都通过自然语言（或用于自动化的DSL）进行。

最近三版新增——根本原因中始终无法被工具装进去的部分：

• MIME 仓库，字节精确。 任何人通过SMW0上传的文件——图片、音频、字体、游戏——都被阅读回读 整体。字节是一个由255字节行组成的数据集群，其最后一行被填充，所以 集群无法说明文件的结束位置;而 WWWPARAMS 中的 filesize 可以，即 那一步，让它变得非常准确，而不是几乎正确的。服务器上没有安装任何东西。
• 集群表，已解码。

Vibing Steampunk (vsp)

AI-Agentic Development Unlocked for ABAP — any system with ADT enabled, 7.50 upwards. The available surface varies by release, and vsp compat reports it per system: RAP needs S/4, AMDP needs HANA, and some ADT resources present on S/4 are absent on ERP.

Part of the steampunk family: open-steamgate (an ABAP application server you can clone), abapiti (TypeScript and WASM to ABAP), open-rfc-go (RFC) and open-diag-go (SAP GUI DIAG).

ADT ↔ MCP Bridge: Gives Claude (and other AI assistants) full access to SAP ADT APIs. Read code, write code, debug, deploy, run tests — all through natural language (or DSL for automation).

New in the last three releases — the part of a root cause that never fit in a tool:

• The MIME repository, byte-exact. Every file anyone uploaded through SMW0 — images, audio, a font, a game — read back whole. The bytes are a data cluster of 255-byte lines whose last line is padded, so the cluster cannot say where the file ends; filesize in WWWPARAMS can, and that is the step that makes it exact rather than nearly right. Nothing installed on the server.
• Cluster tables, decoded. BALDAT, INDX, STXL — every table an EXPORT ... TO DATABASE ever wrote — read over plain ADT and decoded here: SAP’s LZH and LZC decompressed in Go, the cluster format walked, the fields named from DD03L. What only IMPORT could read, without a line of ABAP.
• A dump’s own why — dumps --explain now reads the whole ST22 document, not just the stack: the message it raised with its variables, the system fields, the failing source line, and the runtime’s chosen variables per frame — so a stale handle or an unresolved pointer is on screen, not dug out by hand.
• The application log with its messages, by object and date range, and the same log from a bare SE16H export of two tables.
• Spool and jobs — SP01’s list decoded from TemSe, a job’s steps and its log, exported for the whole night in one command.
• Where the settings are — a report’s variants with the screen’s own labels, SE37’s saved test data, SE61 documentation as Markdown, and the IMG searched by title with the activity’s transaction.