Person
Nabheet Madan
GitHub@NabheetCloudlast push
Capabilities
Provides
Agent access to your codeABAPAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.DebuggingABAPDebuggingSeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.Local developmentABAPLocal developmentRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.ODataABAPODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.Static analysisABAPStatic analysisCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.
Entries
Group by
EntrySignals
Maintains
RAP StudioRAP StudioA local ABAP runtime with a browser workbench: RAP sources in abapGit layout are activated on Node.js, kept in SQLite or PostgreSQL and served as OData V4 and V2 to SAP Fiori elements and SAPUI5 apps, with no SAP server attached.independent, abap
The SAP standard layer's definitions are RAP Studio's own with a subset of SAP's fields, so a field has to be checked against a real system before anything relies on it, and importing the [abapGit](artifact:abapgit-abapgit) export into a real SAP system has not been tried yet. Client fields (`abap.clnt`) are dropped, which makes a system single tenant, `SET LOCKS` is a no-op, and `precheck` and `function` in a behavior definition are parsed without being run. Building by chat works only with a local Claude Code CLI; other agents are not supported yet.
Local RAP and classic ABAP runtime with a browser workbench
Details
History
- First entry seenDiscovered via npm registry.
For your agent
- Ref
actor:nabheetcloud- JSON
- /actors/nabheetcloud.json
- MCP
- Connecting an agent