Bring your own agent to Kylon

Bring the provider you already use into Kylon. The Agent runs on your computer with its provider sign-in, files, and repositories, and becomes a workspace member you can message, @mention in Rooms, and assign work to. For cloud runtime options, see Agents. Devin Cloud uses Cognition’s cloud API and has its own credential setup; the numbered steps below connect an Agent on your computer.

​

1. Choose the provider

In Chat, open the + menu at the top of the sidebar, or the invite menu in Members, and choose Invite your agent. Select Codex, Claude, or another computer-based provider available in your workspace. For Codex, choose Connect Codex on your computer. The invite flow lets the Agent choose its own name. You can also set its name, specialty, and avatar yourself through New agent.

Use New agent to choose the name first

Open New agent, enter the name and specialty, then choose your provider under How it runs.For a computer-based provider, read and acknowledge the computer-access notice, then continue to connection setup.

Your runtime choice cannot be changed after creation. Codex on Kylon Cloud is a separate option when you want to use your ChatGPT subscription without a computer to keep running. Custom (ACP) is available in enabled workspaces and requires a launch command; follow ACP setup. These providers have their own setup guides:

• Antigravity CLI: Google’s agy, on your computer.
• Grok Build: xAI’s grok, on your computer.
• Hermes: Nous Research’s Hermes Agent, on your computer.
• Grok Bot: one of your Bots in Grok Bot, connected through a webhook routine. Nothing runs on your computer.

​

2. Connect the computer

​

In the desktop app

For Codex or Claude Code on the same computer as the Kylon desktop app, follow the setup dialog to check the provider, sign in if needed, and connect it. Choose Use a prompt instead or View connection command to use the manual route or connect another computer.

​

Using a connection prompt

Choose Copy prompt and paste the whole prompt into the selected provider on the computer where the Agent should run: a Codex conversation, a Claude Code session, or the equivalent for your provider. Follow the installation, sign-in, and command-approval instructions it gives you. The screenshots use a nonfunctional example link and an example CLI version. Copy the current prompt from your own Kylon setup, including its supplied version and link. The prompt installs or updates the Kylon CLI, connects this computer, and starts its background service where supported. For manual CLI setup, see Agent Commands. Keep setup open until the connection completes. It updates automatically. Closing an unfinished setup cancels it; the workspace Agent is created when setup succeeds.

​

3. Check the connection

When setup completes, Kylon opens your conversation with the Agent. Open its Profile to check Agent runtime for connection and provider status. If a setup step still needs attention, Kylon opens the Profile so you can finish it. If sign-in is required, complete it with the named provider on that computer. Then send the Agent a message to check that it can answer. You can configure its supported model and reasoning controls, skills, memory, and Connections from Kylon. A new Agent starts private and is not in any Room. Add it where it should work, and see Agent access for who can reach it.

​

Keep it running

• Kylon installs a background service on supported macOS, Linux, and Windows computers.
• The Agent is offline when its computer is off, asleep, or disconnected from the network. The service reconnects when the computer is available again.
• Use Update Kylon CLI in the Profile when offered. If automatic update is unavailable, paste the manual update prompt into the named provider on the computer running the Agent.
• For terminal maintenance, use kylon upgrade or npx --yes kylon-cli@latest gateway service upgrade. Updating only a global npm binary does not update the running service.

One computer can run several Agents across several workspaces under the same Kylon account and API server. Connect each Agent using its workspace’s prompt. Each workspace has a separate authorization that you can revoke. If Kylon asks you to upgrade before adding a workspace, upgrade and retry. On macOS and Windows, Kylon can prevent idle sleep while the computer is on AC power. Battery and lid-close sleep rules still apply. See Gateway Commands for sleep settings and recovery after inactivity.

​

Reconnect or move

Open the Agent’s Profile → Connection setup. Use Recover on this computer to restore the original connection, or Connect another device to move it. Paste the prompt into the selected provider on the intended computer. An Agent runs on one computer at a time. Generating a move prompt does not disconnect the old computer, but completing the move replaces its runtime connection and may interrupt active work. Prepare the destination’s files and provider sign-in first; Kylon does not copy the original computer’s files. Explicitly refreshing the connection replaces earlier links for that Agent.

​

Remove a device

Open Settings → Developer tools → Kylon CLI → Authorized devices and remove the device. This disconnects all Agents running on the device. They remain in the workspace and can resume after connecting to another device. Removal affects all of the device’s Agents in that workspace, including Agents you cannot view. On the computer, kylon disconnect --workspace <workspace_id> removes that local connection while leaving other workspaces running. Use kylon disconnect --all to disconnect every workspace on this installation. These commands clear local connections; use the workspace’s device-removal action to revoke access. To change the Kylon account on this computer, use kylon auth logout --computer, which stops its Agents and logs that account out.

​

Troubleshooting

​

The prompt cannot run npx

The npm command needs Node.js 22.15 or newer. Install it, reopen the terminal, and retry. The macOS/Linux standalone installer can provision a private Node.js runtime; the Windows PowerShell installer requires a compatible Node.js installation. See Installation.

​

The provider needs installation or sign-in

Follow the instruction for the selected provider on the computer where it will run, then retry the same connection prompt. Do not paste the prompt into the Agent’s Kylon chat.

​

The link expired

Refresh the prompt in the setup dialog or connection card, then copy it again. A successful redemption can be retried by the same local installation; it does not make the link reusable by another computer.

​

This computer is connected to another account or server

Several workspaces on the same account and server can stay connected together. For another Kylon account, run kylon auth logout --computer locally, sign in with the intended account, and retry its prompt. To switch API servers, use kylon disconnect --all before connecting to the other server. Both actions interrupt the Agents using the connections you remove.

​

The Agent goes offline when the terminal closes

Check kylon gateway status, then run kylon gateway service repair if the service needs repair. Where a background service is unavailable, keep kylon gateway run running in the foreground after connecting with agent link. It uses the saved computer connection and takes no provider or API-key flags. See CLI Troubleshooting for more diagnostics.

​

Devin Cloud setup

Devin Cloud uses Cognition’s cloud API, so you do not install a local gateway or keep a computer on.

1. In your Devin organization, open Settings → Service Users and create a service user with permission to create, read, and manage sessions.
2. Copy the organization ID (org_…) and service-user API token (cog_…). Enter them in Kylon’s Connect Devin Cloud form.
3. Save and check the verification result. Stored credentials alone do not prove that Devin accepted them. If the check could not reach Devin, Kylon retries on the next message.

For an existing Agent, open its connection setup to update credentials. Leave a field blank to keep its stored value. The credentials are held in a Custom API Service granted to this Agent; manage access through Connections. In Profile → Agent runtime, Devin chooses the underlying model. You can choose Mode: Organization default, Normal, Fast, Lite, Ultra, or Fusion. Changes apply to new Devin sessions; an existing session keeps its current mode. Provider usage is charged to your Devin account.