AI Provider for Osaurus

AI Provider for Osaurus wires the Osaurus local LLM runtime into the WordPress AI Client that ships with WordPress 7.0. After activation, any plugin that calls wp_ai_client_prompt() (Gutenberg AI features, official provider plugins, third-party code) can route prompts to Osaurus running on the same machine. Prompts never leave the local network. Why use it

• Privacy first — prompts stay on your machine, no third-party API receives the data.
• Zero cost — no API keys, no metered requests.
• Fast — MLX-backed inference on Apple Silicon.
• OpenAI-compatible wire format — streaming, tool calls, JSON output, and chat history work out of the box.

Capabilities

• Text generation
• Chat history
• Function / tool calls
• Structured JSON output
• Streaming

Image generation, embeddings, and text-to-speech are not supported because Osaurus does not currently expose those endpoints. Pair this plugin with an image-capable provider such as the official AI Provider for OpenAI when you need images. How it works The plugin registers a provider with AiClient::defaultRegistry() and points it at the Osaurus HTTP server. Because Osaurus speaks the OpenAI Chat Completions wire format, the implementation extends the SDK's OpenAI-compatible base classes — so capabilities like streaming and tool calling flow through automatically. Configuration The plugin resolves the Osaurus base URL in this order (first match wins):

1. OSAURUS_BASE_URL PHP constant defined in wp-config.php.
2. osaurus_ai_connector_base_url option, settable from Settings → Connectors in wp-admin.
3. Default: http://127.0.0.1:1337/v1 (works out of the box for bare-metal WordPress on the same Mac as Osaurus; Docker setups must override).

Pick the right URL for your setup WordPress can run in many places — the right base URL depends on how it reaches your Mac, where Osaurus is listening.

• Bare-metal WordPress on the same Mac (MAMP, Laravel Valet, Local, WordPress Studio, native PHP): http://127.0.0.1:1337/v1 (this is the default — no configuration needed)
• Docker-based WordPress on the same Mac (DDEV, Lando, Docker Desktop): http://host.docker.internal:1337/v1
• WordPress on a different machine on your LAN, Osaurus on your Mac: http://<your-mac-LAN-IP>:1337/v1 — make sure Osaurus is bound to a non-loopback interface and your firewall allows port 1337.
• Remote Osaurus you operate (e.g. a Mac mini on Tailscale, a colocated server): http://<remote-host>:1337/v1 or https://... if you front it with TLS.

The fastest way to confirm a URL works from the WordPress host: run curl <base-url>/models from the same shell environment WordPress runs in. A JSON list back means the connector will work. Osaurus project home: osaurus.ai Osaurus documentation: docs.osaurus.ai

1. Install and start Osaurus on your Mac (Apple Silicon required).
2. Confirm Osaurus is reachable, e.g. curl http://127.0.0.1:1337/v1/models.
3. Install this plugin from the WordPress.org plugin directory, or upload the plugin folder to wp-content/plugins/.
4. Activate AI Provider for Osaurus on the Plugins screen.
5. Visit Settings → Connectors. The Osaurus row should report as connected once a model list is available.

If WordPress and Osaurus run on the same host, no further configuration is required — the default http://127.0.0.1:1337/v1 works as-is. If you run WordPress inside Docker (DDEV, Lando, Docker Desktop), switch the URL to http://host.docker.internal:1337/v1 from Settings → Connectors or set OSAURUS_BASE_URL in your environment config.

0.4.2

• Initial release: registers Osaurus as a WordPress AI Client provider with text generation, chat history, tool calls, structured JSON output, and streaming. Custom Connectors UI with URL input, bare-metal / Docker presets, live connection status, and a default-model picker.