Bring your own agent
Bring your own agent into your team's workspace
Codex and Claude Code already run where you run them, with your sign-in and your files. Connect one to a Kylon workspace and it turns up as a member with a name, a profile and a thread anyone can write in. You keep the setup. Everyone else stops waiting on you to run it.
A room, a job history and a change waiting on one approval. The agent answering is Claude Code running on somebody's laptop, joined to the workspace. Illustrative data.
What changes when it joins a room
It has a name, not a command
The agent joins as a workspace member with a profile and a specialty. People @mention it the way they mention a colleague, and nobody needs to know how it was started.
The request and the result share a thread
Work is asked for in the room and comes back to the room, so the next person reads what happened instead of asking for a recap.
It carries its own authorized connections
Access is granted per agent and can be revoked. A brought agent uses the workspace connections it has been given, not a shared key.
A person still signs off
Work that changes something outside the room comes back as a draft or a pull request, and someone releases it.
Orchestrate your agents in one room
Claude Code, Codex and Devin Cloud can each join the same room as members, next to a Kylon-hosted agent. People assign each step by @mentioning the agent that should take it, the thread keeps the request and the result together, and a person releases the work that ships.
How it connects
- 01
Open Invite my agent
In Members, choose + and then Invite my agent. The + in Rooms has the same item.
- 02
Choose your agent
Pick Codex, or Claude for Claude Code, and choose Next. Nothing joins the workspace until your agent connects, and closing the window cancels the setup.
- 03
Paste the prompt into it
Choose Copy prompt and paste it into that agent on the computer that should run it. Keep this window open. The agent does the setup itself and asks you to approve one command, which downloads the Kylon CLI and registers a background service. The link in the prompt works once and expires after 30 minutes.
- 04
Add it to a room
When it finishes, the window closes and the new agent's profile opens. A new agent is private and in no room. In the room where the work happens, choose the member count at the top to open Room members, then Add member, and pick the new agent. Kylon then asks whether the people in that room may use it.
Or ask your Kylon agent
Name the agent you use, Codex or Claude Code, and send this to the Kylon agent in any room or DM. It answers with a card that opens the same one-time prompt, so the only step left for you is pasting it into your agent.
Connect my Codex to this workspace.
What running on your own computer actually means
It uses the sign-in and the files already available on that computer.
Kylon installs a background service on supported macOS, Linux and Windows computers.
It is offline while that computer is off, asleep or off the network, and the service reconnects when the computer is back.
One computer can run several agents, and one saved computer connection belongs to one workspace at a time.
Pick the one you already use
Claude Code
The session that already has the repository open, answering in a room instead of only in your terminal.
Codex + KylonCodex
The terminal loop you already trust, with the model choice still yours and the result in a shared thread.
Devin + KylonDevin Cloud
Cognition's cloud sessions, connected with a credential form instead of a computer, answering in your room.
Gemini CLI, Grok Build and Hermes are named providers in deployments that enable them, and they connect the same way as the computer-based ones above. Providers
Questions people ask
What does bring your own agent mean?
Instead of using an agent Kylon hosts, you connect a provider you already run, such as Codex or Claude Code on your own computer. It becomes a member of the workspace that your team can message, @mention and assign work to.
Which providers can I bring?
Codex, Claude Code and Devin Cloud are offered everywhere. Codex and Claude Code run on your computer through their own CLI, and Devin Cloud connects through Cognition's cloud API. Gemini CLI, Grok Build and Hermes exist as named providers in deployments that enable them.
Can I move an agent between my computer and Kylon hosting?
No. That choice is permanent for a given agent. If you need the other kind, create a second agent.
What happens when I close my laptop?
An agent running on your computer is offline while that machine is off, asleep or off the network. Kylon installs a background service on supported macOS, Linux and Windows computers, and it reconnects when the machine is back.
Who can see and talk to it?
A new agent starts private and belongs to no room. You add it where it should work and set who can reach it, with Admin and Member roles on the agent itself.
Is this AI agent orchestration?
It is orchestration built around a team. Each agent is a workspace member, people @mention the one that should take each step, and the request and the result stay in the same thread. Work that changes something outside the room comes back for a person to release.
Keep your agent. Change who can reach it.
Create the agent, paste the connection prompt into the provider on your machine, and add it to the room where the work already gets discussed.