OpenClaw
Personal agent runtime
AgentsAgents. Models. Your business.
Bring OpenClaw, Claude, Codex and your agent frameworks into one control plane. Choose the models behind them. Connect the business systems they work with, through scoped operations and explicit authority.
Explore the ecosystemLaunch specification · Versioned support matrices accompany releases

Built around your environment
Explore agents, frameworks and model providers first, then corporate software, data and infrastructure. Each integration has a distinct role. Logos identify launch targets; release manifests publish exact versions, operations and conformance evidence.
63 ecosystem targets
Personal agent runtime
AgentsOpenShell sandbox and agent lifecycle
AgentsAnthropic coding agent
AgentsOpenAI coding agent
AgentsGoogle terminal agent
AgentsStateful agent orchestration
FrameworksMulti-agent crews and workflows
FrameworksEnterprise agent orchestration
FrameworksCustom agent applications
FrameworksGPT and reasoning model families
ModelsClaude model family
ModelsGemini model family
ModelsGLM model family
ModelsDeepSeek model family
ModelsQwen and Qwen Coder families
ModelsKimi model family
ModelsMistral and Codestral families
ModelsGrok model family
ModelsLlama model family
ModelsMiniMax language models
ModelsCommand model family
ModelsNemotron model family
ModelsNova model family
ModelsGranite model family
ModelsJamba model family
ModelsOwner-managed model serving
Model servingSelf-hosted inference engine
Model servingLocal models and inference server
Model servingManaged Inference Endpoints
Model servingMail, calendars and organization content
Business softwareTeam messages and review notifications
Business softwareSites, documents and knowledge sources
Business softwareMail, calendars and workspace content
Business softwareFiles, documents and knowledge sources
Business softwareCRM records and customer workflows
Business softwareService requests and incident workflows
Business softwareIssues, projects and workflow updates
Business softwareTeam documentation and knowledge
Business softwareMessaging and scoped approval notifications
Business softwareWorkspace pages and knowledge
Business softwareIssues, projects and release coordination
Business softwareRepositories, pull requests and workflow events
Developer toolsSource control, merge requests and CI
Developer toolsOperational signals and observability
Developer toolsScoped database operations
Data platformsGoverned warehouse queries and results
Data platformsData workflows and bounded job operations
Data platformsCloud resources and service operations
InfrastructureCloud resources and service operations
InfrastructureCloud resources and service operations
InfrastructureContainer packaging and service lifecycle
InfrastructureCluster resources and workload operations
InfrastructureTenant identity and access signals
IdentityOrganization identity and access signals
IdentityApplication identity and access signals
IdentitySelf-hosted identity federation
IdentityDesktop workspace
SystemsDesktop workspace
SystemsDesktop and server
SystemsMobile SDK and companion
SystemsMobile SDK and edge
SystemsLinux distribution
SystemsLinux distribution
SystemsEnterprise connections
Read a document in SharePoint. Prepare a Salesforce update. Propose a Jira change. Every operation declares its tenant, resource, credential scope, side effects and expected evidence before execution.
Explore connections · Coming soonOAuth and identity establish access. LNSAT or a selected authority adapter binds permission to the exact operation.
What compatibility means
An adapter declares which instructions, tools, context and lifecycle hooks a target understands, and which require adaptation.
Identity and policy systems contribute evidence. A matching authority path must still bind the exact action, scope and execution.
Conformance fixtures, version ranges, limitations and result evidence travel with the adapter. Unsupported capabilities remain visible.
The future is open
Let’s build an AI ecosystem worth trusting.
