Keep the business rationale with the work
Use another connected client today to retain the objectives, decisions, and open questions behind a process. That knowledge stays available in Angareion while your team evaluates Joule connectivity.
Explore Angareion shared memory for SAP Joule Work Desktop: business context, reusable workflows, and handoffs, with clear early-access requirements.
Joule Work Desktop · early access

The direct answer
Angareion provides an early-access connector guide, a combined skill package, and a local proxy for SAP Joule Work Desktop. The skill import format is validated; end-to-end MCP execution remains unverified because current workspace policy blocks custom connections. Availability depends on your Joule workspace and administrator policy.
Understand shared AI memoryBuilt around your work
Business work crosses assistants as well as applications. Angareion’s Joule integration is designed to bring retained project knowledge into that flow, with its early-access status and workspace requirements clearly documented.
Use another connected client today to retain the objectives, decisions, and open questions behind a process. That knowledge stays available in Angareion while your team evaluates Joule connectivity.
Save a brief in ChatGPT or Claude with the business goal and next steps. Once the Joule connector is permitted and verified in your environment, that authorized context can be retrieved through it.
The combined Joule skill package includes guidance for memory, knowledge, handoffs, outputs, and specialists. Importing the package is separate from establishing and validating its MCP connection.
Inside Angareion
The Connect guide walks you through your client’s setup. Choose the appropriate connection, approve access, and verify the tools before asking for your context.

Your work can travel
This illustrates the intended workflow once Joule connectivity is permitted and verified. The saved context is already usable in other connected clients.
“Save this business brief in Angareion. Include the process objectives, decisions, and the Joule connection policy that still needs validation.”
“Retrieve the business brief saved for Joule. Help me prepare the decision memo while the workspace connection is being evaluated.”
Illustrative prompts. Your assistant must call the connected tools; chat history and local files are not automatically transferred.
How an AI handoff worksMake the connection
Confirm Joule Work Desktop access and ask your administrator whether custom MCP connectors are permitted. Review the documented early-access limitations.
Follow the remote connector guide. Where organizational policy permits it, the separate localhost proxy can forward requests to Angareion. It is not a way around workspace restrictions.
Import the combined Joule skill ZIP without extracting it. Confirm actual Angareion tool execution in your workspace before relying on cross-client recall.
Questions, answered
What carries over, what needs connecting, and how to keep the work moving.
Explore the knowledge libraryThe Joule Work Desktop skill package, local proxy, and connection instructions are available for evaluation. The skill format is validated, but end-to-end MCP execution remains unverified because current workspace policy blocks custom connections. Verify execution in a permitted workspace before relying on it.
Angareion retains knowledge outside the underlying model. Access depends on Joule Work Desktop exposing a working, authorized MCP connection, rather than on a named model family. This integration does not provide a Joule model selector.
That is the intended cross-client workflow once Joule connectivity is permitted and verified. The context must first be saved in Angareion, and Joule must use the same agent or an authorized shared scope. End-to-end Joule execution is currently unverified.
No. The localhost proxy forwards requests to the same Angareion server. Use it only where your organization permits that connection and data flow. If policy blocks custom connectors, work with your administrator rather than assuming the proxy makes them allowed.
Retain useful facts and decisions as memories, add reference material to knowledge sources, save complete work products as outputs, and preserve unfinished work as handoffs. These are explicit workflows: Angareion does not automatically record everything you do in every assistant.
Access follows your Angareion agent identity and permitted memory scopes. Reusing the same agent across clients provides continuity; team or institutional sharing requires the appropriate scope and permissions. Connecting a new client does not give it unrestricted access to every memory.
Request Angareion private-beta access, then follow the connection guide for your client. Angareion does not supply the AI client’s subscription or change its account requirements. Compare the current Angareion editions and check the client’s own eligibility before connecting.
Keep what you learn
Request Angareion access, connect SAP Joule, and build a body of knowledge that can travel with your work.
Private beta. Access is granted from a waitlist.