Unboxing Joule Studio: Exploring the jl CLI : Your First Steps
Walks through the jl CLI's full command surface: solution and asset management for @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's nine asset types (agent, cap-app, mcp-server, n8n-workflow among them), login against SAP Cloud Identity Services, and the jl mcp and jl a2a groups for testing tool bindings and agent-to-agent calls. A CI/CD example runs jl solution validate, build and deploy from a GitHub Actions step, and jl init claude wires Claude Code into a project over MCP with Intent-Based Development skills fetched from the backend. It contrasts this terminal-driven pro-code path with Joule Studio's browser-based low-code builder, noting both produce the same deployable artifact registered with the same Joule runtime.
Where it sits
Who is behind it
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · joule-tag.
For your agent
- Ref
content:unboxing-joule-studio-exploring-the-jl-cli-your-first-steps- JSON
- /content/unboxing-joule-studio-exploring-the-jl-cli-your-first-steps.json
- MCP
- Connecting an agent