@sap/joule-work-dev-cli-early-adopters
jl, the pro-code CLI of the new Joule Studio: a solution is a folder with a solution.yaml and typed assets, validated, built into a zip and deployed to Joule Studio's managed runtime, with Claude Code or OpenCode wired in over MCP. Early Adopter Care.
The new Joule Studio has two paths to the same deployed agent, and this is the one for a terminal. jl solution create writes a solution.yaml with apiVersion solution.sap/v1, jl asset create agent adds an agent asset that exposes /.well-known/agent.json, validate, build and deploy run the same six steps the browser does, and jl a2a message talks to the deployed agent over the Agent-to-Agent protocol. jl init claude or jl init opencode fetches skills from the Joule Studio backend and writes the MCP configuration through which the coding agent queries SAP LeanIX, the SAP Knowledge Graph and SAP Domain Models during intent, requirements and specification. The package depends on @cap-js/mcp-server@cap-js/mcp-serverSAP's MCP server for CAP development, run as cds-mcp: search_model searches the project's compiled CDS model, search_docs searches the CAP documentation indexed as embeddings on the developer's own machine.sap official, cap and @ui5/webcomponents-react-mcp, and its skills need @sap/cds-dk@sap/cds-dkThe command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.sap official, cap for CAP Node.js applications and Python 3 for A2A agents. SAP's help pages carry an Early Adopter Care banner, say the CLI installs from an internal registry and still contain placeholder notes; the package is on the public registry as an alpha, 0.1.20-alpha.25 on 2026-08-19.
Facts
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
Before choosing this
Conditions
PolicySAP API Policy 4.2026a§ 2.2.2from Agent toolingAn agent built into an application reaches SAP Application APIs, whether directly or through tools generated from a service that proxies them.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
capire's own guide states that CAP-level agents are intended only for exposing custom CAP application services, and names section 2.2.2 for the agentic-access provisions. Check which endpoints the agent's tools end up calling, and consult SAP's reference architectures for the endorsed routes.
SAP API Policy 4.2026a →What it declares
Every artifact
- Type
- CLI
- Origin
- By SAP
- Runtime
- Node.js
As a CLI
- Distributed through
- npm
Connections
Building an agent into your own application
Command line client and development toolkit for CAP
SAP's managed environment for building custom agents and workflows
Download
Install
npm add @sap/joule-work-dev-cli-early-adoptersDerived from the package name. No recipe recorded; the README has the configuration.
Learn more
- From Intent to Arcade: Building Joule*Bert with Joule Studio and AI-Assisted Pro CodeFrom Intent to Arcade: Building Joule*Bert with Joule Studio and AI-Assisted Pro CodeA Devtoberfest 2026 AI-track session that takes a Q*bert-style arcade game, written as an Easter egg for colleagues, through every phase Joule Studio runs: intent analysis with its clarifying questions, a product requirements document, a specification with its task list, generated code, generated tests and deployment. The knowledge-graph lookup reports that the game maps to no enterprise process and the flow adjusts, and the presenter edits the requirements by hand when the first version declares sound out of scope. He then pushes the project to GitHub, clones it and initialises the jl command line so that Joule Studio's MCP servers are wired into the coding agent in VS Code, where mobile arrow keys were added afterwards; applications could not yet be deployed to the Joule Studio runtime, so this one runs on Kyma.SAP Developers, published 2026-10-01SAP Developers, YouTube — SAP Developers playlists
- Real Pro-Code Development with Joule StudioReal Pro-Code Development with Joule StudioA Devtoberfest 2026 AI-track session that runs one agent build across both of Joule Studio's paths. Playing a procurement manager, one presenter states the intent in the browser, answers the clarifying questions, watches the fit-gap analysis name the S/4HANA APIs the use case needs, and pushes the intent and requirements document to GitHub; the other clones it and carries on in a terminal, logging in with the jl command line against her landscape URL and running its init command to fetch Joule Studio's skills for OpenCode. From there the coding agent writes the specification, the discovered API specifications, the MCP translation and the agent's Python file with its model configuration and evaluation scenarios, which is the edge to Agent tooling; the skills themselves, which SAP says not to edit but which a developer may add to, are the edge to Agent guidance.SAP Developers, published 2026-10-01SAP Developers, YouTube — SAP Developers playlists
- Build your first agent with Joule Studio in a pro-code wayBuild your first agent with Joule Studio in a pro-code wayThe command line interface of Joule Studio, which the atlas holds as @sap/joule-work-dev-cli-early-adopters, carries an agent from a structured intent through generated product requirements documentation and wired APIs to a deployment on Joule Studio's SAP-managed runtime, in one guided flow. SAP's abstract names the stages of that pipeline and promises working code at the end; what the generated requirements and APIs look like is not described. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Charan Ravikumar, Evgenii Skrebtcov, Maria Kondratyeva and Simon Endres, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
Architecture
Download
README
quoted from @sap/joule-work-dev-cli-early-adopters@0.1.20-alpha.25 under SEE LICENSE IN LICENSE, readjl — Joule Studio Dev CLI
The Joule Studio Dev CLI (jl) can be used to interact with the Joule Studio backend and provides capabilities to:
- Create and manage solutions composed of typed assets (agents, MCP servers, workflows, etc.)
- Set up pro-code projects for AI coding agents
- Validate and build solution artifacts
- Deploy solutions to Joule Studio runtime
- Manage assets (create, delete) across all supported asset types
- Interact with MCP servers (list, inspect tools, call tools)
- Send agent-to-agent messages
Installation
Requirements
- Node.js ≥ 24
The following are required depending on which skills you use after running jl init <agent>:
| Requirement | Skills that need it |
|---|---|
| Python 3 | sap-agent-bootstrap — scaffold and run Python A2A agents |
@sap/cds CLI (npm install -g @sap/cds-dk) | cap-development — build and run CAP Node.js applications |
Install
Note: Use the
@prereleasetag to install the most recent alpha release version
npm install -g @sap/joule-work-dev-cli-early-adopters@prereleaseUpdate
npm install -g -f @sap/joule-work-dev-cli-early-adopters@prereleaseUninstall
npm uninstall -g @sap/joule-work-dev-cli-early-adoptersUsage
jl login <joule-studio-url> # log in
jl solution create --name <name> # create a solution
jl solution validate # validate
jl solution build # build zip
jl solution deploy # deploy to backendExample Workflow
Log in to the backend:
jl login 'https://my-backend.cfapps.eu12.hana.ondemand.com?issuerUrl=https://myias.accounts.cloud.sap&clientId=<client-id>&appTid=<app-tid>'Where do I find this URL? In your Joule Studio tenant, go to Settings → Develop and copy the URL shown there.
Create a solution and add an asset:
jl solution create --name my-solution
jl asset create agent --name my-agentValidate, build, and deploy:
jl solution validate
jl solution build
jl solution deployCheck deployment status:
jl solution deploy status
jl solution deploy logs --tail 100See the CLI Reference for all commands and options.
History
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-joule-work-dev-cli- JSON
- /artifacts/sap-joule-work-dev-cli.json
- MCP
- Connecting an agent