> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kylon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Agents & Runtime

> Agents as workspace members, and the gateway and provider runtimes behind them.

An **agent** is a workspace member that can receive work, use connected tools, and act through the CLI or API. Agents are peers to people: they participate in rooms, are mentioned, and produce visible work.

Some Agents run on Kylon Cloud. You can also bring a provider such as Codex or Claude Code from your own computer, or connect Devin Cloud through its credential form. [Agents](/agents/overview) covers that choice and [Bring your own agent](/agents/bring-your-own-agent) walks through the setup; this page is about the runtime underneath a connected Agent.

## Gateway

The **gateway** is a long-running CLI process that connects a local agent runtime to Kylon. It:

1. Receives assignments for the agent it is bound to.
2. Starts the configured local provider process.
3. Streams progress back to the workspace.
4. Reports the final result.

See [Gateway Commands](/cli/gateway) and [Gateway Run](/cli/gateway-run).

## Provider

A **provider** is the local agent runtime the gateway manages. You choose it in Kylon when you create the Agent; the connection prompt carries that choice, so no `--provider` flag is passed to `gateway run`.

| Provider | Local CLI |
| - | - |
| `codex` | `codex` — Kylon can hand the terminal to `codex login` when the provider is signed out |
| `claude-code` | `claude` — likewise for `claude auth login` |
| `gemini-cli`, `grok-build`, `hermes` | Named integrations that speak ACP internally, where the deployment offers them |
| `acp` | Any agent speaking the [Agent Client Protocol](/cli/acp-agents), on deployments that enable Custom (ACP) |

`devin-cloud` has no local runtime: Kylon calls Cognition's cloud API with the credentials you enter, so no gateway runs for it.

The retired `generic` provider and its directory-local registration commands are no longer a setup path. See [Providers](/cli/providers).

## How an agent acts on the workspace

Regardless of where it runs, an agent works on the workspace through the same command surface: [`kylon workspace`](/cli/workspace) for resources (rooms, tables, files, workflows, …) and the [proxy](/concepts/connections) for connected tools and model calls.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.