Skip to main content

Aventail Connect

Aventail™ Connect configures supported apps to send their model requests through Aventail™ Link. Start a compatible model, open Connected apps in Link and choose Connect. Link handles the supported app's connection settings for you.

You need a registered Link device and the app installed on the same computer. For your first check, download and serve a compatible model. Coding tools also need suitable model tool support and enough context and memory for the task.

Example: connect Claude​

The same connection pattern applies to the supported apps listed below. The macOS example was recorded on 23 October 2026, using Claude Desktop and a model displayed as Gemma4. Your model name can differ.

AVENTAIL / CONNECT

From a serving model to Claude

Full view

Start in the Models tab

The full Link window places Models, Connected apps and Settings in the top navigation. Gemma4 is the model serving in this capture.

Slide 1 of 6: Start in the Models tab.

Reviewed macOS captures from 23 October 2026. Gemma4 is the captured model, not a requirement for every device. Use the arrows or progress marks to move between slides.
AVENTAIL / CONNECT

From a serving model to Claude

Full view

Start in the Models tab

The full Link window places Models, Connected apps and Settings in the top navigation. Gemma4 is the model serving in this capture.

Slide 1 of 6: Start in the Models tab.

Watch the recorded Claude connection
Silent recording, 23 October 2026. Open Link from the menu bar, open Connected apps and choose Connect beside Claude. The status changes through Connecting to Connected · Gemma4. Claude Desktop is closed during the change and uses Link when next opened. The written steps below give the full procedure.
Check the processing destination

Connect governs model requests. A routing policy can send them to an approved peer or hosted provider, even when the app connects to a local address. Peer and hosted routing are in beta; provider requests leave this computer and may incur charges. Review the app's file access, tools, storage and other network activity separately.

Read the app connection and verification steps

Connect an installed app​

  1. In Link's Models tab, choose a compatible model and select Start serving. Wait for Ready to serve. The model may load on its first request.
  2. Open Connected apps, find the app and choose Connect. Apps Link cannot find appear under Other supported apps; install the app on this computer first.
  3. Read the status beneath the app. If a change is waiting for Claude to close, finish the open work and fully quit Claude Desktop or close the Claude Code sessions concerned. Closing a desktop window alone may only hide it. Link does not quit or restart another app for you.
  4. Open a fresh session and send a harmless question. In the Claude Desktop example, select Gemma4 via Aventail in its model picker. This connects Claude to the chosen model; it does not run Anthropic's Claude model weights locally.
  5. Confirm a completed answer, then check the effective policy and Recent usage in Control to establish where the request ran. A model label or successful response alone is not proof of the destination. See routing verification.

For the supported automatic setup, you do not need to invent a provider entry, edit an API endpoint or paste a provider key into the app. Organisation-managed settings can prevent a connection; ask the administrator rather than overriding them.

Supported apps​

  • Claude Desktop: choose Claude in Link. After the connection is applied, reopen Claude Desktop and choose the connected model. Fully quit it from its menu or tray when Link is waiting for it to close.
  • Claude Code: uses the same Claude connection. Choose the serving model in Link and start a fresh session once the change finishes. This Connect path does not require an Anthropic account.
  • OpenCode: choose OpenCode in Link. Check that the model supports coding tools and has enough context. The app's own web tools and plugins have separate settings.
  • Codex CLI, editor extension and desktop app: choose Codex in Link. They share Codex's user configuration. Open sessions keep their model; the desktop app takes up changes when it next starts.

The Codex connection uses the Responses API. The reviewed route supports local models, peers and OpenAI; other cloud providers are not supported for Codex on this path.

While Claude Code uses the Connect gateway, account-based claude.ai connectors are unavailable. Locally configured MCP servers and plugins retain their own settings and data flows.

App, operating-system, model and runtime versions affect compatibility. Successful chat does not establish reliable tool use, long-context work or session resumption. See compatibility and versions.

For other clients, use the Link integration reference. The existing Continue in VS Code, Open WebUI, Obsidian and OpenClaw guides describe their own configuration paths.

Disconnect or recover​

Choose Disconnect beside the app. Link restores the settings it changed while preserving unrelated edits. Read any warning if settings were edited or cannot be restored automatically. A Claude change may wait for the relevant sessions or desktop app to close; Cancel the change cancels a waiting change.

Once the change finishes, reopen the app or start a fresh session. Check the restored provider and model before continuing: a previous configuration may use another service. Codex sessions already open keep their current model until they end.

SymptomNext check
App not foundInstall the supported app on this computer, then return to Connected apps.
No model availableCheck that a compatible model is Ready to serve. A remote-only setup needs a supported, applied routing policy.
A change is waitingFinish the Claude sessions or fully quit Claude Desktop as requested, then inspect the status again.
An unexpected model answersStart a fresh session and check the configured default, effective route and Recent usage.
Chat works but coding failsTest model tool support and context capacity; retain the actual error rather than weakening application permissions.

You can also inspect connections and waiting changes from a terminal:

aventail connect --list