Partner feature. Custom (ACP) is currently offered only to Kylon partners, and we turn it on for one Workspace at a time after reviewing the request. If you are not a partner, start with Bring Claude Code, Codex or another Agent into Kylon.

If your client already has an Agent of their own (an in-house agent, or one built on a framework), you can bring it into their Kylon Workspace. Once connected, it shows up as a member that people can message, @mention in Rooms and assign work to, the same way as Claude Code or Codex. Kylon talks to it over the Agent Client Protocol (ACP), the open standard that also connects agents to Zed and JetBrains.

Request access

  1. Email your Kylon partner contact, or support@kylon.io, from the address you use in Kylon.
  2. Tell us which Workspace it is for, which Agent you want to connect (its name, or the framework it is built on), and what the Agent will do for the client.
  3. We review the request and reply. When it is approved, Custom (ACP) appears as a choice when you invite an Agent in that Workspace.

Access applies to that one Workspace. For another client's Workspace, send a new request.

Before you start

  • You need permission to create Agents in the Workspace.
  • The Agent has to support ACP v1 over stdio. Many coding agents already do, including Gemini CLI, GitHub Copilot CLI, Cline, Qwen Code, Grok and Devin, and Claude Code and Codex through their ACP adapters. If you or your client built the Agent, check what it must support in Bring an ACP agent.
  • A computer you control that stays on while the Agent should be reachable, such as a server or an always-on machine. The Agent runs there, not on Kylon.
  • Node.js 22.15 or newer on that computer. The setup command installs the Kylon CLI if it is missing.
  • Know what you are handing over. The Agent runs as your user account on that computer and can use the files and tools that account can use.

Steps

  1. Open the invite menu. In the sidebar, select the + button (New), then choose Invite your agent.
  2. Pick Custom (ACP). It is listed after the other providers once your Workspace has it. Select it, then select Next.
  3. Choose how to start your Agent. Pick your Agent from the list, or choose Something else and enter the command that starts it, for example my-agent --acp.
  4. Run the command on that computer. Copy the connection command and run it on the computer where the Agent will live. It links that computer to the Workspace and installs the Kylon service. It is valid for 30 minutes. Keep the setup dialog open until it finishes.
  5. Sign the Agent in. Run the Agent's own login once on that computer. If it uses an API key instead, pass it when you set the launch command, as shown in Connect an ACP Agent. Kylon never sees these credentials.
  6. Say hello. Send the Agent a message in Kylon to check that it answers.

To change how the Agent starts later, run kylon agent configure <agent-id> -- <command> on that computer. If it does not come back after the computer restarts, run kylon gateway service repair.

What the Agent can do in Kylon

  • It can read a Room's history, search the Workspace, send messages, read attachments, list members and keep its own memory, within the Rooms and Connections it has access to. Connecting it does not open every Room or Connection.
  • Like any new Agent, it starts private. Add it to a Room and share access with the people who should use it.
  • Work it does on that computer runs on your or your client's own account with the Agent's vendor, and is not billed in Kylon credits. Anything it calls through Kylon is billed as usual. See Limit and track credit usage.
  • To have Kylon reject the Agent's ACP permission requests to run commands or edit, delete or move files, set a strict permission policy on that computer: kylon agent configure <agent-id> --permission-policy strict. This only answers permission requests the Agent makes through ACP. It does not make the Agent read-only, does not limit what its user account can do on that computer, and does not stop actions the Agent takes without asking for permission. See Permission policy.

If something goes wrong

  • Custom (ACP) is not in the menu. It has not been turned on for this Workspace yet. Check that your request was approved for this Workspace.
  • The command expired. Start the setup again to get a new one.
  • The Agent shows Needs attention. Its launch command has not answered yet, or the Agent needs you to sign in on that computer. Run the command by hand there, sign it in, then send another message.
  • The Agent stopped answering later. Check that the computer is on and online. See Why an Agent you brought is not responding.