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

# Migrate from another terminal

> Bring your hosts, profiles, and habits over from iTerm2, Warp, Windows Terminal, and friends.

If you're switching to Rumus from another terminal, this page covers the practical migration: what carries over automatically, what you'll set up by hand, and the muscle-memory differences worth knowing about.

<Note>
  Rumus does not yet ship a one-click importer. The steps below are manual but quick — most users finish in 10–15 minutes.
</Note>

## What carries over for free

Anything that lives outside the terminal app keeps working as-is:

* **Shell config** — `.zshrc`, `.bashrc`, `.profile`, PowerShell profiles, fish config: untouched.
* **SSH config** — `~/.ssh/config` and `~/.ssh/*` keys still work for ad-hoc `ssh hostname` commands. Rumus does not require you to migrate them into the vault, although doing so unlocks the SSH host manager and encrypted sync.
* **Tools you already installed** — Homebrew, asdf, pyenv, Docker, kubectl, etc. all behave the same; Rumus just runs your shell.

## From iTerm2 (macOS)

| iTerm2 concept     | Rumus equivalent                                                                                                     |
| ------------------ | -------------------------------------------------------------------------------------------------------------------- |
| Profile            | [Profile](/docs/getting-started/core-concepts#profile) (Settings → Profiles)                                              |
| Window arrangement | A [Workspace](/docs/getting-started/core-concepts#workspace) — terminals laid out as cards on a canvas, persisted by name |
| Split panes        | Multiple terminal cards on the same workspace canvas                                                                 |
| Hotkey window      | Configurable in Settings → Keyboard                                                                                  |
| Triggers           | Rules & skills for the AI agent (different in spirit, similar in result)                                             |

**Migrate profiles**: iTerm2 stores profile JSON in `~/Library/Application Support/iTerm2/DynamicProfiles/`. There's no automated import — recreate the few you actually use under **Settings → Profiles**.

**Migrate SSH hosts**: if you used iTerm2's "open in profile" pattern with `ssh user@host`, the same hosts will work as new entries in the Rumus host manager.

## From Warp (macOS / Linux / Windows)

Warp users will feel at home — the AI sidebar, command suggestions, and workflows have direct analogues:

| Warp concept      | Rumus equivalent                                                              |
| ----------------- | ----------------------------------------------------------------------------- |
| AI Command Search | AI sidebar (right side of the title bar)                                      |
| Workflows         | Skills (Settings → AI → Rules & Skills)                                       |
| Notebooks         | Markdown cards inside a [Workspace](/docs/getting-started/core-concepts#workspace) |
| Drive sync        | Cloud sync for profiles, encrypted vault sync for hosts                       |
| Blocks            | Native command decorations via shell integration                              |

**Sign-in**: like Warp, you can sign in to a Rumus account to enable cross-device sync. It's optional — local terminal features work signed out.

## From Windows Terminal

| Windows Terminal concept  | Rumus equivalent              |
| ------------------------- | ----------------------------- |
| Profile (`settings.json`) | Profile (Settings → Profiles) |
| Color scheme              | Theme (Settings → Appearance) |
| Key bindings              | Settings → Keyboard           |
| Quake mode                | Hotkey window (configurable)  |

PowerShell, cmd, WSL distros, and Git Bash all show up as profile options if they're installed on the system. WSL distributions are detected automatically.

## From plain SSH (`~/.ssh/config`)

You can keep using `ssh hostname` from any tab — Rumus does not interfere with `~/.ssh/config`. To benefit from the encrypted vault, host groups, real-time monitoring, and one-click SFTP, recreate the ones you use most under **Settings → Hosts**.

A reasonable middle ground: leave one-off targets in `~/.ssh/config`, and put production / frequently-used hosts in the Rumus vault.

## Keyboard shortcuts

Rumus ships sensible defaults for opening tabs, switching tabs, opening settings, and so on. The full list — and remapping for every action — lives in **Settings → Keyboard**.

If you have a specific iTerm2 / Warp / Windows Terminal shortcut you rely on, you can reproduce it there.

## What's different on purpose

A few behaviors may surprise you coming from a traditional terminal:

* **The vault is opt-in but encouraged.** Storing credentials there is what lets sync, jump-host chains, and command approval work safely.
* **The AI agent can take actions.** By default, destructive commands prompt for approval before running. Whitelist trusted patterns under **Settings → AI → Command Approval**.
* **Workspaces are optional.** Tabs at the top of the window are always there. Workspaces are a separate kind of tab that hold a canvas full of terminals — open one only when a project benefits from a persistent multi-terminal layout. Day-to-day work in plain terminal tabs is unchanged.

## Rolling back

If you decide Rumus isn't for you, your old terminal is unaffected — Rumus does not modify your shell, SSH config, or system PATH. Uninstall steps live in [Installation](/docs/getting-started/installation#uninstall).

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/docs/getting-started/quickstart">
    A guided first session with onboarding, hosts, and AI.
  </Card>

  <Card title="Core concepts" icon="diagram-project" href="/docs/getting-started/core-concepts">
    The vocabulary used throughout the rest of the docs.
  </Card>
</CardGroup>