@sap/joule-studio-cli
SAP’s CLI package for both legacy Joule digital assistants and the new Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrella solution workflow, through the joule and jl commands.
Installing this package supplies two commands: joule compiles and manages legacy digital assistants, while jl creates, validates, builds and deploys typed solutions to Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrella. The jl workflow also configures a coding agent, calls MCP tools and sends A2A messages. The separately published @sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersjl, 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.sap official, btp package also supplies jl; SAP’s current pro-code tutorial installs @sap/joule-studio-cli. The package’s installation section specifies Node.jsNode.jsA cross-platform JavaScript runtime that servers, command line tools and scripts written in JavaScript are run with. For the things here, the prerequisite a repository names when its build is a set of npm scripts. 22–24 and a Linux keyring, with a separate requirement of Node.js 24 or later for jl. SAP’s README designates the CLI for testing and development and says it is not intended to manage personal or confidential data.
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
For agent tooling
- Protocols
- MCPA2A
Connections
Building an agent into your own application
Skills for building an A2A agent for Joule and deploying it to CF
Command line client and development toolkit for CAP
Download
Install
npm add @sap/joule-studio-cliDerived from the package name. No recipe recorded; the README has the configuration.
Architecture
Download
README
quoted from @sap/joule-studio-cli@2.0.4 under SEE LICENSE IN LICENSE, readJoule Studio CLI
Installing @sap/joule-studio-cli gives you two commands:
| Command | Description |
|---|---|
joule | Joule Studio Legacy CLI — compile, deploy and manage digital assistants |
jl | Joule Work CLI — create and manage solutions, agents, MCP servers, and more |
joule — Joule Studio Legacy CLI
The joule command provides capabilities to:
- Compile the designtime artifact into a runtime artifact
- Deploy a digital assistant via its runtime artifact
- Test deployed Joule assistant
- Get a list of all deployed digital assistants
- Delete deployed digital assistants
- Launch deployed digital assistants
- Run static lint checks and convert YAML test scenarios into
.featurefiles
Installation
You can install both CLIs globally using npm.
Requirements
- Node.js v22 – v24
- For Linux: libsecret or a compatible keyring (for secure credential storage)
Install
npm install -g @sap/joule-studio-cli
Update
npm install -g -f @sap/joule-studio-cli
Uninstall
npm uninstall -g @sap/joule-studio-cli
Usage
Important Security Notice
The Joule Studio Command Line Interface is designed solely for testing and development purposes and is not intended to manage personal or confidential data. Users should ensure that any content provided for testing contains only non-real, non-sensitive information to maintain security and privacy.
Available Commands
| Command | Description |
|---|---|
joule login | Log in to the CLI |
joule compile <source> <target> | Compile a DTA folder into an RTA artifact |
joule deploy <assistant> | Deploy a digital assistant to Joule |
joule list | List all deployed assistants |
joule get <assistant> | Retrieve details of deployed assistant |
joule launch <assistant> | Launch the Web Client for a deployed assistant |
joule delete <assistant> | Delete a deployed assistant |
joule update <assistant> | Update a deployed capability |
joule remove <assistant> | Delete a deployed capability |
joule lint <path> | Run the static linter |
joule config | Manage configuration for the digital assistant |
joule status | Display current login status |
joule logout | Log out from the CLI |
Run joule help or joule <command> --help for full usage details.
Global options
| Option | Description |
|---|---|
| -V, --version | Print the CLI version number |
| -d, --debug | Generate a debug file in the current directory |
| -w, --no-color | Disable colorized output |
| -h, --help | Print usage information for the CLI or a specific command |
Login
To log in to a production landscape, run:
joule login
The API URL will be automatically determined based on the authentication URL provided. To connect to a custom API URL, use:
joule login --apiurl <apiurl>.
Example Workflow
-
Log in to Joule:
joule login -
Compile designtime artifacts into runtime artifacts:
joule compile -
Deploy the digital assistant:
joule deploy ./da.sapdas.yaml -
Launch it in the web client:
joule launch my_assistant_name
jl — Joule Work CLI
The jl command 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
Note:
jlrequires Node.js ≥ 24.
Usage
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 backend
Example 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-agent
Validate, build, and deploy:
jl solution validate
jl solution build
jl solution deploy
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 |
See the CLI Reference for all commands and options.
Built on @sap/joule-studio-cli-core-v2.
Documentation
Full product documentation is available at: SAP Help Portal – Joule Studio Tools
License
Copyright © SAP SE
This project is licensed under the SAP Developer License
History
Others providing
Compare all 5 on the Agent tooling page →- Joule Studio, classic editionJoule Studio, classic editionThe low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.sap official, btpLow-code SAP Build capability for custom Joule skills and agents
- Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrellaSAP's managed environment for building custom agents and workflows
- @sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersjl, 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.sap official, btpPro-code CLI for building and deploying Joule Studio solutions
- SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btpSAP's AI engagement layer across SAP applications
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
- both joule and jl in the published package
- First seen.
For your agent
- Ref
artifact:sap-joule-studio-cli- JSON
- /artifacts/sap-joule-studio-cli.json
- MCP
- Connecting an agent