CLICLItypeA command you run, rather than a dependency you import.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

@sap/joule-studio-cli

SAP’s CLI package for both legacy Joule digital assistants and the new Joule Studio 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 Studio. 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 package also supplies jl; SAP’s current pro-code tutorial installs @sap/joule-studio-cli. The package’s installation section specifies Node.js 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

Latestv2.0.4ReleasedLicenceSAP DEVELOPER LICENSE AGREEMENT 3.2

Where it sits

Lives in
Provides
Agent toolingBTPCAPAgent toolingcapabilityBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.
Serves
Requires
@sap/cds-dk@sap/cds-dkartifactwhen using the cap-development skill after jl init, to build and run CAP Node.js applications
Designs
Integrating and Extending JouleIntegrating and Extending Joulereference architecturepro-code tool to build, compile and deploy capabilities for Joule

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14
@SAP
maintainer

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

Connections3

Install

npm add @sap/joule-studio-cli

Derived from the package name. No recipe recorded; the README has the configuration.

Where @sap/joule-studio-cli runsBy its type: a CLI is run from a terminalcallsdocumentedrequiresYour terminal, actorYour terminal@sap/joule-studio-cli, module@sap/joule-studio-cli@sap/cds-dk, module@sap/cds-dk
SAPnot SAP's, or the project's ownstated in the documentdocumented only

README

quoted from @sap/joule-studio-cli@2.0.4 under SEE LICENSE IN LICENSE, read
@sap/joule-studio-cli@2.0.4/README.mdOn npm

Joule Studio CLI

Installing @sap/joule-studio-cli gives you two commands:

CommandDescription
jouleJoule Studio Legacy CLI — compile, deploy and manage digital assistants
jlJoule 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 .feature files

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
CommandDescription
joule loginLog 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 listList 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 configManage configuration for the digital assistant
joule statusDisplay current login status
joule logoutLog out from the CLI

Run joule help or joule <command> --help for full usage details.

Global options
OptionDescription
-V, --versionPrint the CLI version number
-d, --debugGenerate a debug file in the current directory
-w, --no-colorDisable colorized output
-h, --helpPrint 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: jl requires 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>:

RequirementSkills that need it
Python 3sap-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

SAP DEVELOPER LICENSE AGREEMENT 3.2, read licence

History

Latest

v2.0.4

  1. v2.0.2

  2. v1.5.21

On npm
138downloads per week, npm
Weekly downloads for @sap/joule-studio-cli26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 138.27 Apr – 3 May: 514 May – 10 May: 8811 May – 17 May: 11318 May – 24 May: 27125 May – 31 May: 2741 Jun – 7 Jun: 1628 Jun – 14 Jun: 27715 Jun – 21 Jun: 33322 Jun – 28 Jun: 29029 Jun – 5 Jul: 2036 Jul – 12 Jul: 28113 Jul – 19 Jul: 47720 Jul – 26 Jul: 56927 Jul – 2 Aug: 3043 Aug – 9 Aug: 30810 Aug – 16 Aug: 52717 Aug – 23 Aug: 41024 Aug – 30 Aug: 44431 Aug – 6 Sept: 3407 Sept – 13 Sept: 23214 Sept – 20 Sept: 27821 Sept – 27 Sept: 32028 Sept – 4 Oct: 4035 Oct – 11 Oct: 71312 Oct – 18 Oct: 23819 Oct – 25 Oct: 138
Agent tooling
  1. Joule Studio, classic editionLow-code SAP Build capability for custom Joule skills and agents
  2. Joule StudioSAP's managed environment for building custom agents and workflows
  3. @sap/joule-work-dev-cli-early-adoptersPro-code CLI for building and deploying Joule Studio solutions
  4. SAP JouleSAP's AI engagement layer across SAP applications

Details

Sources3
Added by handdiscovered herechecked
npm registry, @sap/joule-studio-cliversion, releases, installschecked
README.mdquoted, and what the entry declareschecked

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
runtimesnode
latestv2.0.4
first release
releases and cadence3, ~190d median
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, ai-and-agents
History in the atlas2
  1. both joule and jl in the published package
  2. First seen.
For your agent
Ref
artifact:sap-joule-studio-cli
JSON
/artifacts/sap-joule-studio-cli.json
MCP
Connecting an agent