Connection Profiles
Relevant source files
The following files were used as context for generating this wiki page:
Connection Profiles define how Conduit interfaces with different Large Language Model (LLM) providers and self-hosted agents. These profiles manage credentials, base URLs, and protocol-specific configurations to allow the client to communicate with various backends, ranging from local on-device models to complex self-hosted server environments.
Sources: README.md:94-118, packages/conduit_core/pubspec.yaml:4-8
Profile Types and Architecture
Conduit supports multiple connection types, each categorized by the underlying technology or hosting environment. These connections are managed within the conduit_core package, which handles the business logic for authentication, API communication, and direct connections.
Sources: README.md:120-131, packages/conduit_core/pubspec.yaml:4-8
Core Connection Categories
| Profile Type | Description | Key Capabilities |
|---|---|---|
| Open WebUI | Connects to a self-hosted Open WebUI server. | Full feature set including folders, tools, web search, and image generation. |
| Direct | Connects straight to a model provider or local endpoint. | Supports OpenAI-compatible APIs, Ollama, and OpenRouter. |
| Apple On-Device | Uses Apple's local SystemLanguageModel (iOS 26+). | Works offline; supports streaming and JSON-schema. |
| Apple PCC | Uses Apple Private Cloud Compute (iOS 27+). | Reasoning levels, image input, and live quota status. |
| Hermes Agent | Connects to a self-hosted Hermes server. | Tool execution with live approval and scheduled agents. |
Sources: README.md:120-131, README.md:133-146
Connection Flow Diagram
The following diagram illustrates how a user selects and configures a connection profile during the initialization or setup process.
Sources: README.md:218-261
Direct Connection Configuration
Direct connections allow users to bypass intermediate servers and communicate directly with model endpoints. This system uses openai_dart and ollama_dart packages to facilitate standardized API calls.
Sources: packages/conduit_core/pubspec.yaml:26-30, README.md:133-138
Key Configuration Elements
- Base URL: The endpoint address for the API provider (e.g., local Ollama instance or OpenAI).
- API Key: Authentication token stored in platform secure storage (Keychain for iOS, Keystore for Android).
- Custom Headers: Users provide specific headers such as
X-API-Keyor organization routing IDs for restricted environments. - History Synchronization: Users choose if direct chats stay only on the device or sync with an Open WebUI history when signed in.
Sources: README.md:133-138, README.md:204-210, README.md:237-241
Authentication and Security
Connection profiles manage sensitive credentials through the platform's secure storage mechanisms. Conduit avoids plain-text local storage for keys and session state.
Sources: README.md:204-210, README.md:271-274
Supported Authentication Paths
Conduit accommodates various self-hosted authentication realities:
- Standard Auth: Username, password, and LDAP.
- Modern Auth: Manual JWT entry, SSO, and OAuth providers.
- Proxy Auth: Supports
oauth2-proxy, Authelia, Authentik, and Cloudflare Tunnels by capturing session cookies on-device.
Sources: README.md:202-214
Data Flow for Credentials
Implementation Details
The connection logic is primarily implemented in packages/conduit_core. It utilizes several libraries to manage diverse communication protocols.
Sources: packages/conduit_core/pubspec.yaml:1-60
Relevant Dependencies in Core
| Dependency | Usage in Connection Profiles |
|---|---|
dio | HTTP client for API requests and error classification. |
openai_dart | Implementation for OpenAI-compatible endpoints. |
ollama_dart | Native implementation for Ollama connections. |
web_socket_channel | Token streaming and terminal sessions. |
socket_io_client | Real-time communication for specific server types. |
mcp_dart | Support for Model Context Protocol (MCP) servers. |
Sources: packages/conduit_core/pubspec.yaml:20-56
Summary
Connection Profiles serve as the foundational bridge between the Conduit mobile client and the various intelligence backends it supports. By providing a unified interface for Open WebUI, direct API providers, on-device models, and specialized agents, the system enables secure and flexible LLM access on mobile devices while prioritizing privacy and self-hosted compatibility.
Sources: README.md:94-118, README.md:267-279