Watch the walkthrough above without a cluster, or follow the live script below.
Interactive recording: Building Agentic AI in a Developer Sandbox (Arcade).
Use LiteMaaS Qwen (litemaas-qwen) for any tool-calling step. Shared Granite is chat-only — Lightspeed/Continue will hallucinate CVEs if you leave it selected in Agent mode.
Part A — Helm catalog install
- OpenShift Console → Developer perspective → your Sandbox project
- +Add → Helm Chart → search
rhdh-agent-sandbox→ Install Helm Chart - Release name
rhdh-agent, chart 0.1.11, Form view - Set Cluster Router Base and OpenShift token (shared models) (
oc whoami -t). Leave LiteMaaS API key empty if Secretlitemaas-credentialsalready exists - Create → wait until Topology group rhdh-agent is Ready (Hub 2/2, LiteLLM, MCP, applier, PostgreSQL)
Part B — Hub agent loop (~5 min)
- Open the Developer Hub Route → Enter as Guest
- Catalog → filter
mcp→ browse MCP API entities and their Documentation - Create → Deploy Agent (Golden Path) (Python / LangGraph,
tool-agent, modelgranite) - Open the new Component → Topology after the BuildConfig finishes (no git push)
- MCP Chat →
litemaas-qwen→ ask forpods_list_in_namespacein this namespace
Part C — DevSpaces + Red Hat Security MCP (~5 min)
- Create → Agent-friendly DevSpaces AI Workspace (workspace starts stopped)
- Dev Spaces dashboard as the Sandbox user → Start → Trust
- Continue → model LiteMaaS Qwen (LiteLLM) → Agent or Plan (not Chat)
- Customer Portal SSO via the public http-8080 helper (not Che
code-redirect) - Ask
get_cve_by_idfor CVE-2024-3094 (xz). Expect live tool chips, Red Hat severity — not NVD folklore - Stop the workspace when done to free quota
Wrap-up
oc get bc,deploy -l app.kubernetes.io/part-of=rhdh-agent-sandbox
oc get dw