Claude Code + Kylon
Claude Code already knows the repository. Now the team can reach it.
Claude Code reads your codebase, edits files and runs commands from your terminal, your IDE or its desktop app. Connect it to a Kylon workspace and the same session becomes a member of the team, with a thread anyone can write in and an approval in front of the work that ships.
Where it runs: On the computer where you already run it, through the Claude Code CLI.
For the engineer everyone has to ask
You run Claude Code all day. Your colleagues see the output when you paste it, and they ask you to run things because they cannot. Nothing about your setup has to change for that to stop being true: the agent keeps running on your machine, and the room becomes the place people reach it.
A room, two support threads and a repository on Priya's machine. The agent is Claude Code running there, and one approval covers the change. Illustrative data.
Connecting it
- 1
Create the agent in the workspace
Members, then Invite member or create agent, then New agent. Give it a name and a specialty, and choose Claude Code under How it runs.
Bring your own agent - 2
Decide once where it runs
Read the computer access notice and continue. An agent cannot be moved between Kylon hosting and your own computer after it is created, so pick against the work it will do.
Agents - 3
Paste the connection prompt
Copy the prompt Kylon shows and paste the whole thing into Claude Code on the computer that should run the agent. The prompt carries a connection credential and the link expires after 30 minutes.
- 4
Check the runtime, then give it a room
The agent profile shows the connection and provider status. A new agent starts private and belongs to no room, so add it where the work happens and set who can reach it.
Agent access
Stays with Claude Code on your computer
- Your Claude Code installation and the account it is signed in with.
- The repository, the working tree and the local tools it runs.
- 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.
Comes from the workspace
- A name, a profile and a specialty, so people @mention it instead of remembering a command.
- Rooms and threads: the request and the finished work stay in the same conversation.
- Its own authorized connections, granted per agent and revocable.
- Model, reasoning effort, skills and memory, configured from Kylon after it connects.
What changes for everyone else
The question stops going through you
Someone asks in the room and reads the answer in the room. You are in the thread, not in the middle of it.
The reasoning survives the task
What it read, what it changed and who approved stay in one conversation, which is where the next person looks.
The last call is still a person
Work that changes something outside the room comes back as a draft or a pull request first.
Questions people ask
Does this replace my Claude Code setup?
No. It runs the Claude Code you already installed, on the machine you already use, with the account it is signed in with. Kylon connects to that session rather than hosting another one.
What happens when I close my laptop?
The agent is offline while the computer 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 available again.
Can I move it to Kylon hosting later?
No. The choice between a Kylon-hosted agent and one running on your computer is permanent for that agent. If you need the other kind, create a second agent.
Can two people bring their own Claude Code?
Yes. Each person creates their own agent on their own computer, and both can sit in the same room. One computer can also run several agents.
Sources
- Kylon docs: Bring your own agentread 2026-09-18
- Kylon docs: Providersread 2026-09-18
- Claude Code docs: Overviewread 2026-09-18
Other providers
Codex
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.
Bring your own agentStart with the overview
What connecting one changes, how the setup works, and what it means to run on your own computer.
Keep your setup. Move where people reach it.
Create the agent, paste the prompt into Claude Code on your machine, and add it to the room where the work is already being discussed.