This is an early release preview. You may encounter bugs.
OpenClaw Dev logo
Unclaimed

Blueprint deployment connectors

OpenClaw Dev

Template for a personal OpenClaw on Azure Container Apps with Managed Identity, sandboxed tool execution, and Teams access

Built by Microsoft

C 60/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
No votes yet

01 / About

What OpenClaw Dev is.

openclaw-dev is an alpha template for hosting a personal OpenClaw assistant on Azure Container Apps instead of a laptop. The container calls Azure OpenAI in Foundry Models (default gpt-5.4-mini) through a Managed Identity with local auth disabled, so no API keys exist in the system; Entra ID Easy Auth requires a Microsoft sign-in scoped to your tenant before any request reaches the WebChat UI; and an optional Microsoft Teams channel makes the assistant reachable from a phone.

Deployment goes through devclaw, a thin wrapper over the Azure Developer CLI, with commands for up, deploy, status, logs, start, stop, teams, exec-mode, and down. The repository also ships an agent skill in the open Agent Skills format, so GitHub Copilot Chat, Claude Code, Cursor, or Codex can run the same playbook from plain-English requests such as deploying to a region, enabling sandboxes, or tearing everything down, and confirms before destructive actions.

Tool execution can stay in-process or be offloaded: with devclaw exec-mode sandbox, each untrusted shell, code, or browser run is handed to an ephemeral ACA Sandbox through a sandbox MCP server and destroyed afterwards. Inside the container, a gateway-proxy on port 18789 routes Teams traffic to the msteams plugin and everything else to the OpenClaw gateway, while an auth-proxy injects a fresh Entra ID bearer token on every forwarded model request. State lives on Azure Files, so devclaw down && devclaw up rebuilds a clean instance in about six minutes, and a stopped deployment costs nothing.

Mode Enable with Where tools run
In-process (default) Inside the gateway container
Sandbox execution devclaw exec-mode sandbox then devclaw up Throwaway ACA Sandboxes; the gateway stays on ACA and Teams keeps working
Sandbox host (experimental) azd env set USE_SANDBOX true then devclaw up The whole gateway runs in a sandbox; no Teams

Features

  • Azure Container Apps hosting: an ephemeral OpenClaw gateway container with public HTTPS ingress and Azure Files for credentials, workspace, and sessions
  • Keyless model access: Managed Identity tokens to Azure OpenAI in Foundry Models with disableLocalAuth: true
  • Entra ID Easy Auth: tenant-scoped Microsoft login enforced before the WebChat UI, with /api/messages excluded for Bot Framework
  • Sandbox execution mode: untrusted tool runs offloaded to throwaway ACA Sandboxes via a sandbox MCP server; an experimental sandbox-host mode runs the whole gateway in a sandbox
  • Microsoft Teams channel: Azure Bot Service plus the @openclaw/msteams plugin, with a sideload zip built by devclaw teams
  • devclaw CLI: deploy, stop to zero replicas, restart, stream logs, switch execution mode, clone, and delete all resources
  • Agent skill: a playbook for Copilot Chat, Claude Code, Cursor, and Codex that uses the repo's own scripts, env-var contract, region list, and error catalog
  • Gateway token layer: a random per-container token injected into the SPA so authenticated users still need it to reach the WebSocket API
  • Cost profile: roughly $2 to $5 per day while running and $0 when stopped

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Deploy

Deploy OpenClaw Dev.

Deploying a blueprint runs it as a live agent. That happens on WayID, where your agent gets a verifiable certificate and signed telemetry.

Deploy on WayID →
Fork Discuss