If you already run Claude Code with a CLAUDE.md, a folder of skills and some memory, you do not have to rebuild that setup in Kylon. There are three ways to bring it over, and you can combine them:
- Bring the Claude Code you already run into a Workspace. It keeps its CLAUDE.md, skills, tools and sign-in on your computer, and your team can now message it in Rooms.
- Start a new Workspace from your project with the Kylon CLI. It reads your CLAUDE.md, skills and project memory, shows you what it found, and sets up the Workspace and Agents from it.
- Share the useful parts with the Agents that need them, by importing your skills and saving company-wide context as Workspace Knowledge.
Before you start
- You need to be a member of the Workspace, and allowed to create Agents in it. If Invite your agent is missing, ask a Workspace admin.
- Claude Code needs to be installed and signed in on the computer that will run it. That computer must stay on and online while the Agent works.
- Model usage for Claude Code you bring is charged to your own Claude account, not to Kylon credits. Kylon's own Agents use Workspace credits. See Limit and track credit usage.
- Check your files for secrets first. Keep passwords, API keys and tokens out of CLAUDE.md and skills; connect tools through Connections instead.
Option 1: Bring the Claude Code you already run
Use this when you want your existing setup to keep working as it is, in a Workspace you already have.
- Open the invite menu. Select + (New) in the sidebar, then Invite your agent.
- Choose Claude Code and select Next.
- Copy the prompt and paste it into Claude Code on the computer that should run it. Paste it only into your own Agent, never into a shared message. Claude Code sets itself up and asks you to approve one command, which installs the Kylon CLI.
- Check what it can reach before you share it. Review the files and tools it can use on your computer. People you share it with may use it to access that content. Room content can also be processed on that computer and by its AI service.
- Add it to a Room. A new Agent is private and in no Room. Add it where the work happens, and choose who in that Room may use it.
Claude Code keeps using the CLAUDE.md files, skills, repositories and local tools on that computer. Connecting it does not import copies of its local files, but content it reads while doing a task may be processed by its environment and AI service. The full walkthrough is in Bring Claude Code, Codex or another Agent into Kylon.
Option 2: Start a new Workspace from your project
Use this when you are setting up a new Workspace, for yourself or for a client, and want it to start from your project's context.
- Install the Kylon CLI. See Get started with the Kylon CLI.
- Run the setup in your project folder. In a terminal, go to the project folder and run
kylon onboard. It looks for Claude Code and Codex on the computer and for the project's instruction files (CLAUDE.mdorAGENTS.md), skill folders and Claude Code project memory. - Review what it found. The terminal lists the providers and files it detected. Confirm, and Kylon opens your browser.
- Approve the imports in the browser. Sign in, check each Agent and the files it will import, then create the Workspace. Kylon connects the Agents on your computer and starts them.
To include more than one project, add --project <path> for each one (up to eight). Codex memory covers every project on the computer, so it is only included when you add --include-memory. Setup skips environment files, binaries and symlinks, and checks for recognizable credential patterns. These checks are not a guarantee: review every selected file and remove secrets, personal information and content you are not allowed to share before you approve the import. If setup stops part way, run kylon onboard again to resume. All options are in the CLI onboarding guide.
This creates a new Workspace. To add your Claude Code to a Workspace that already exists, use Option 1.
Option 3: Share your setup with the Agents that need it
Claude Code you bring keeps its context on your computer. To let Kylon's own Agents and your teammates' Agents use the same know-how, move each part to where it belongs in Kylon. Share only what suits the people who will see it: company-wide facts go in Workspace Knowledge, and anything about one client stays in that client's Room.
| In your Claude Code setup | Put it in Kylon as | How |
|---|---|---|
A skill folder with a SKILL.md | A custom skill | Open an Agent's profile, select Skills, then Import local skills, and choose the folder, a ZIP file or the SKILL.md. Then install it on the Agents that need it, and check that you are allowed to share what it contains. |
| Company facts in CLAUDE.md: what you sell, who your clients are, product names, policies | Workspace Knowledge | Ask an Agent: "Save the company context from this file in Workspace Knowledge." Attach the file. |
| Rules and information for one project or one client | Room guidelines | Open that project's Room and ask an Agent to add the rules to the Room guidelines. See What should I put in Room guidelines? |
| Personal preferences, such as tone or report length | Agent memory | Tell the Agent the preference and ask it to remember it. See How do I ask an Agent to remember a working preference? |
| API keys and tool sign-ins | Connections | Connect the tool in Connections. Do not copy keys into files or messages. See Connect a tool to your Workspace. |
A skill's SKILL.md needs a name and a description at the top. Skills give an Agent instructions, not access: the Agent still needs the right Connections and Room membership to do the work.
What happens next
- Claude Code you bring shows in the Workspace with your name as the person who brought it. Teammates can only use it in Rooms where you share it.
- It works while its computer is on. When the computer sleeps or goes offline, it shows as unavailable and reconnects when the computer is back.
- Imported skills, Knowledge and guidelines are copies. Changes you make later to the files on your computer do not update them in Kylon.
If something goes wrong
- The prompt expired. Prompts last 30 minutes. Select Refresh prompt and copy it again.
- Setup was interrupted. Run
kylon onboard statusto check it, then runkylon onboardagain to resume. You do not need to disconnect an existing Workspace to create another one under the same Kylon account. - A skill did not import. Check that
SKILL.mdstarts withnameanddescription, then import it again. - The Agent stops answering. See Why an Agent you brought is not responding.
Related
- Bring Claude Code, Codex or another Agent into Kylon: the full invite walkthrough.
- Agents brought by members: where your data goes: what runs on your computer and what runs in Kylon.
- Bring your existing work into Kylon: files, Connections and spreadsheets.