Connections

The Connections screen (labelled Integrations in the navigation) centralises every external system that AKOS talks to. Sections are organised into three groups in the left-hand section rail:

Inbound

Providers

LLM providers that agents can use to run inference. Each provider card shows:

• Provider name and logo.
• Connection state: Connected (key verified), Configured (key saved but not verified), or Not connected.
• A Verify button to test the key.
• A Configure button to add or update the API key.

Only connected or configured providers appear in the agent model picker.

Supported provider types include cloud AI services and local providers (for example, Ollama running on the same machine).

External integrations

OAuth-based connections to third-party SaaS applications. Each card shows the provider, its connection state, and a Connect button that launches the OAuth flow. Connected integrations can be used by agent tools and trigger webhooks.

Coding agents

Configuration hub for AI coding agent providers (for example, Claude, GitHub Copilot, or a locally-hosted model). Each provider card shows its connection state and a Configure button to set the API key or endpoint. Provider settings entered here appear automatically in the Coding screen's provider dropdown.

The coding agent provider list is managed in the Connections screen so that all external integrations live in one place. Use the Coding screen for running tasks; use this tab to add or rotate credentials.

Knowledge sources

A read-only summary of RAG knowledge sources configured for this workspace. This tab shows which sources are indexed and their current status. To add, remove, or rebuild sources, navigate to the Knowledge screen.

This tab was added so that all inbound data integrations — LLM providers, OAuth apps, coding agents, and RAG sources — are visible together in Connections.

Outbound

Output sinks

Destinations where AKOS sends workflow outputs (for example, a Slack channel, an email address, or a custom HTTP endpoint). Click Add sink to configure a new destination, choosing the channel type and its settings.

Exporters

Telemetry exporters that forward AKOS observability data to external monitoring systems (for example, OpenTelemetry collectors, Datadog, or custom NDJSON sinks). This section is only available in deployments with the observability cluster enabled.

Workspace

External secrets

References to secrets stored in an external vault (for example, HashiCorp Vault, AWS Secrets Manager). Instead of storing a raw API key in AKOS, you store a vault reference (vault://path/to/secret). AKOS resolves the reference at runtime.

To add an external secret reference:

1. Click Add secret.
2. Enter a local alias (the name agents and flows will use to look up the secret).
3. Enter the vault URI.
4. Save.

SQL connections

Named database connections that agents with SQL tools can use. Click Add connection to fill in the connection form:

• Name — the identifier used in SQL tool calls.
• Driver — PostgreSQL, MySQL, SQLite, or other supported drivers.
• Connection string — the database URL. For sensitive credentials, use an external secret reference instead of a raw password.

Click Test to verify the connection before saving.

Cloud sync

Sync workspace configuration and agent data to a cloud storage backend (for example, an S3-compatible bucket). When enabled, the workspace can be restored from the cloud backup on a new machine. Configure the bucket URL, credentials, and sync interval.

Collab

Real-time collaboration settings — connect your workspace to a shared CRDT-based sync server so multiple team members can edit flows simultaneously. Enter the server URL and any authentication tokens required.