> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Claude Code

> Bring your CLAUDE.md, skills, and MCP servers from Claude Code into Gloo Code, and learn the day-to-day equivalents.

Claude Code users keep most of their setup. Your `CLAUDE.md` files and your skills work in Gloo Code as they are. You only convert your MCP servers, which takes a few minutes.

## What carries over automatically

| You have | What Gloo Code does |
| - | - |
| `CLAUDE.md` in your project | Loads it, from the current folder up to the repository root. If a folder has both `AGENTS.md` and `CLAUDE.md`, both load, and identical content is not repeated |
| `CLAUDE.md` in a subfolder | Attached when the agent reads a file in that folder |
| `~/.claude/CLAUDE.md` (your personal instructions) | Loads it for every project |
| `.claude/skills/<name>/SKILL.md` | Discovered in your project (after you trust the folder) |
| `~/.claude/skills/<name>/SKILL.md` | Discovered for every project |

Type `/skills` inside Gloo Code to see the skills it found. Each skill is also available as `/<skill-name>`, and the agent can use a skill on its own when the task matches its description.

> [!NOTE]
>
> `AGENTS.md` and `CLAUDE.md` load either way. Project config, skills, commands, and MCP servers from the folder apply after you trust it. If the folder has its own config (a `gloocode.json`, or a `.gloocode`, `.claude`, or `.agents` folder), Gloo Code asks once, and you can use `/trust` whenever you like.

## Do once

**1. Install and sign in**

Follow [Installation & Setup](/gloocode/installation). Sign-in happens in your browser, and your organization needs a Gloo Code subscription with a seat for you.

**2. Open your project and start a session**

Run `gloocode` in the folder you normally use Claude Code in, and trust the folder when asked.

**3. Optional: tidy your instructions with /init**

If you'd like one tool-neutral file, run `/init`. Gloo Code reads your existing `CLAUDE.md` and other rule files and drafts an `AGENTS.md` you can review. Keeping `CLAUDE.md` as it is works fine too.

**4. If CLAUDE.md pulls in other files with @**

List those files under `instructions` in a `gloocode.json` at your project root, and Gloo Code loads them as instructions.

```json gloocode.json theme={null}
{
  "instructions": ["./docs/conventions.md", "./.claude/rules/*.md"]
}
```

**5. Convert your MCP servers**

Copy each entry from `.mcp.json` into the `mcp` section of `gloocode.json`. The recipe is on [Move your MCP servers](/gloocode/migrate/mcp-servers#from-claude-code).

**6. Bring over custom slash commands**

Copy your command files into `.gloocode/commands/`. Each Markdown file becomes a command named after the file, and `$ARGUMENTS`, `$1`, and `$2` placeholders in the body work as you'd expect.

```bash theme={null}
mkdir -p .gloocode/commands
cp .claude/commands/*.md .gloocode/commands/
```

Optional frontmatter keys are `description`, `agent`, `model`, and `subtask`.

## Day to day

| In Claude Code | In Gloo Code |
| - | - |
| Shift+Tab to move into plan mode | **Tab** (or **Shift+Tab**) switches between the **build** and **plan** agents. The plan agent reads and proposes without editing. In the desktop app, press **⌘.** |
| Choose a model | Gloo Code picks the model for you. To choose, use `/models`, press **Ctrl+X** then **M**, or start with `-m` or `--model gloo/<key>`. **F2** cycles through recently used models. `gloocode models --verbose` lists what's available |
| Esc to interrupt | **Esc** |
| Esc twice, or `/rewind` | `/undo` and `/redo` |
| `/compact` | `/compact`. Gloo Code also compacts automatically when needed |
| `--continue`, `--resume` | `gloocode --continue`, `gloocode --session <id>`, or `/sessions` inside the app |
| `/init` | `/init` builds or updates an `AGENTS.md` |
| `@file` to mention a file | `@file`. A line range works too, as in `@file#10-20` |
| `!` for a shell command | `!` switches to shell mode |
| `/` for commands | `/` lists every command. Press **Ctrl+P** for the command palette |
| `--dangerously-skip-permissions` | `--unleashed` allows every prompt that no deny rule blocks, for that run. See the warning below |
| `claude -p "task"` | `gloocode run "task"`. Add `--format json` for a stream of JSON events, one per line. Piped stdin is added to your message |

> [!WARNING]
>
> `--unleashed` lets the agent change or delete files and run commands without asking. Use it only in a scratch folder, a container, or a throwaway checkout. You are responsible for what it runs.

Handy to know: **Ctrl+X** is Gloo Code's leader key, used for chords such as **Ctrl+X** then **N** for a new session, **L** for sessions, **A** for agents, **M** for models, **U** to undo, and **R** to redo. **Shift+Enter** adds a new line, and keybindings can be changed in `tui.json`.

## How work flows

You describe a task, and the **build** agent coordinates it. It hands work to subagents such as `code`, `explore`, `review`, and `qa`, which can run in parallel, and shows each as a card in the session so you can follow along. `/review` and `/qa` run those subagents on demand.

## Next steps

> **[Move your MCP servers](/gloocode/migrate/mcp-servers)**
>
> Convert `.mcp.json` into Gloo Code's format.

> **[Migration checklist](/gloocode/migrate/checklist)**
>
> A copy-and-paste checklist for your first day.

> **[Launch Gloo Code](/gloocode/launch)**
>
> Start the terminal UI and run your first task.

> **[Billing & Plans](/studio/billing#choosing-a-gloo-code-tier)**
>
> Tiers, seats, and your monthly allowance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.