OpenClawDocs
On this page

On this page

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page

Providers

Poolside (Laguna)

Poolside provides Laguna models and the Poolside Agent CLI. Choose the integration for the work you want OpenClaw to do:

Goal Integration
Use Laguna models with the OpenClaw agent Poolside-maintained provider plugin
Run the Poolside Agent as an external coding harness ACP with the pool target

Laguna model provider

Install the external @poolside/openclaw-provider plugin:

bash
openclaw plugins install clawhub:@poolside/openclaw-provider

Follow Poolside's OpenClaw guide for authentication, model selection, and hosted or self-managed endpoints. The plugin owns Poolside's model catalog and request compatibility.

If you use POOLSIDE_API_KEY, make it available to the Gateway process before restarting the Gateway. For a managed service, put it in the global runtime .env file or the service environment. Exporting it later in an interactive shell does not update the running service. See Environment variables.

Poolside Agent over ACP

The pool ACP target launches pool acp. Install and authenticate the Poolside CLI on the Gateway host, and make sure pool is on the Gateway's PATH. Configure CLI authentication separately from the OpenClaw provider plugin.

Enable the ACP runtime plugin as described in ACP quickstart. If acp.allowedAgents is set, include pool. Then start a session:

text
/acp spawn pool

See ACP setup for permissions and Poolside's OpenClaw guide for CLI setup.

Was this useful?