Getting started
NOBLE is a single native binary that turns your terminal into a workspace: real shells in tabs and splits, your git projects, live system sensors and your AI quota. This page gets you from zero to your first session.
Install
Windows (x86_64)
In PowerShell, no admin rights needed. It installs into your user folder and adds it to your PATH:
$dir = "$env:LOCALAPPDATA\Programs\noble" Invoke-WebRequest https://github.com/MertSoylu/noble/releases/latest/download/noble-windows-x86_64.zip -OutFile "$env:TEMP\noble.zip" Expand-Archive "$env:TEMP\noble.zip" $dir -Force $path = [Environment]::GetEnvironmentVariable("Path", "User") if ($path -notlike "*$dir*") { [Environment]::SetEnvironmentVariable("Path", "$path;$dir", "User") }
Or download the .zip and put noble.exe anywhere on your PATH. On Windows on ARM, use the ARM64 .zip the same way.
Linux (x86_64 and ARM64)
The Linux binaries are static, so they run on any distribution:
curl -fsSL https://github.com/MertSoylu/noble/releases/latest/download/noble-linux-x86_64.tar.gz | tar -xz noble install -Dm755 noble ~/.local/bin/noble
curl -fsSL https://github.com/MertSoylu/noble/releases/latest/download/noble-linux-aarch64.tar.gz | tar -xz noble install -Dm755 noble ~/.local/bin/noble
macOS (Apple Silicon and Intel)
The binaries are not notarized. Installed with curl they run right away; a file downloaded with a browser needs xattr -d com.apple.quarantine noble once. Make sure ~/.local/bin is on your PATH.
curl -fsSL https://github.com/MertSoylu/noble/releases/latest/download/noble-macos-aarch64.tar.gz | tar -xz noble mkdir -p ~/.local/bin && mv noble ~/.local/bin/
curl -fsSL https://github.com/MertSoylu/noble/releases/latest/download/noble-macos-x86_64.tar.gz | tar -xz noble mkdir -p ~/.local/bin && mv noble ~/.local/bin/
For the alt+ shortcuts turn on Option as Meta in your terminal (Terminal.app: Settings → Profiles → Keyboard; iTerm2: Profiles → Keys → Left Option key → Esc+). The prefix ctrl+a works without it.
With Cargo (Rust 1.95+)
$ cargo install nobleOr skip the compile with cargo-binstall, which downloads the same prebuilt archive for Windows, Linux or macOS:
$ cargo binstall nobleFrom source
$ git clone https://github.com/MertSoylu/noble && cd noble $ cargo install --path .
.sha256 file next to it.First launch
Run noble. A short boot sequence shows what NOBLE found (skip it with any key, or turn it off with boot_animation = false). On the very first launch a welcome card lists the projects it found, the four keys worth knowing and a choice of prefix key, so it doesn’t clash with your shell:
- ⏎ opens a terminal in the selected project
- c x start Claude Code or Codex right there
- alt+p (ctrl+a : inside a terminal) opens the command palette: every action, project, tab and theme is in there
- ? shows every shortcut;
ctrl+clickopens links
Everything else is on screen and clickable. See Keys and mouse for the full reference.
Running Claude Code, Codex, GitHub Copilot, OpenCode, Antigravity CLI or Cursor CLI in NOBLE? Their status on the tabs and on Home, resume after a restart and command blocks are on the AI agents page.
Terminal requirements
Any truecolor terminal with a regular monospace font works; no Nerd Font needed. Windows Terminal, WezTerm, Kitty, Alacritty, GNOME Terminal, Konsole and iTerm2 are all fine. Cascadia Code and Cascadia Mono render every glyph NOBLE uses (box drawing, block elements, braille).
Copy and paste use the system clipboard (Windows, macOS, X11 and Wayland). Without one, for example over SSH, copied text is sent to your terminal with OSC 52, links are copied instead of opened, and files and the config open in a terminal editor ($EDITOR, else nano or vim).
Programs in a pane
Programs in a pane can use the usual terminal queries, so AI CLIs and editors behave as they do in a modern terminal:
- Synchronized output (
CSI ? 2026): a frame drawn inside a block is shown whole, never half-written (held back for at most 150 ms). - Colors: OSC 4, 10, 11 and 12 report the pane's real palette (Windows Terminal schemes included), and
COLORFGBGis set, so a light or dark theme is picked correctly. - Color scheme notices (mode 2031) when a theme change flips light and dark, and focus reports (mode 1004,
CSI I/CSI O). - XTVERSION (
CSI > q) answersNOBLE <version>; DECRQM (CSI ? Ps $ p) reports the modes NOBLE knows. - Kitty keyboard protocol (
CSI > u): a program that asks for it, as Claude Code does, gets Shift+Enter, Ctrl+Enter and Esc in the protocol's own form. - win32-input-mode (Windows): console programs such as PowerShell and Codex get Esc, Shift+Enter, Ctrl+Enter, Ctrl+Tab and Ctrl+Backspace with their modifiers.
A Windows Terminal profile
To open NOBLE in its own tab from the Windows Terminal dropdown, add this profile:
{ "name": "NOBLE", "commandline": "noble.exe", "icon": "⌂", "font": { "face": "Cascadia Mono" } }Command line
noble [folder] [--config <path>] [--no-boot] folder open a shell tab in that folder (for example: noble .) --paths print config and data locations --version print version noble update download and install the latest release noble update --check only report whether there is one noble doctor [--config <path>] print a report for bug reports (opens no terminal)
Updating
NOBLE checks GitHub for a new release once a day and shows it at the bottom right. Click update there, or run noble update. It downloads the prebuilt binary for your platform, checks it against the release's SHA-256 checksum and replaces the installed one; restart NOBLE afterwards. Turn the check off with check_updates = false or in Settings. All archives are also on the releases page.
Troubleshooting
Run noble doctor and paste its output into a bug report. It prints the version, OS, outer terminal and truecolor support, the shells found and whether NOBLE's shell integration applies to them, the agent status hooks of each agent (Claude Code, Codex, GitHub Copilot, OpenCode, Antigravity CLI, Cursor CLI), AI provider detection (never a token), the config and data paths, whether config.toml parses, and the GitHub CLI state. It opens no terminal and changes nothing; --config <path> checks another config file.