A delicious REST client that lives in your terminal.

Noodle is an HTTP client. As a TUI application, it can be used over SSH and enables efficient keyboard-centric workflows. Your requests are stored locally as simple YAML files, easy to read, easy to version control.

Website · Changelog · Roadmap · Quick Start · Docs

Some notable features include:

• 📁 One YAML file per request, git-friendly, no lock-in
• 🗂️ Folder organization with inheritable headers and auth
• 🌐 Environments with $var substitution
• ✏️ Built-in environment editor
• ⌨️ Inline editing of every field directly in the terminal
• 🔐 Multiple auth types (bearer, basic, API key) and body types (JSON, form data, multipart, binary)
• 📜 Response history with timeline per request
• ↔️ Layout switcher (stacked / side-by-side)
• 🎨 Theme picker with 30+ built-in themes
• 🛠️ Customizable keybindings
• 📦 Import from OpenAPI 3.0 and Postman collections
• 📋 Copy response body to clipboard

curl -LsSf https://noodlerest.dev/install.sh | sh

brew tap wilfredinni/noodle
brew trust wilfredinni/noodle
brew install noodle

Installs to ~/.local/bin/noodle (curl) or your Homebrew prefix. The curl installer verifies the release SHA-256 checksum before replacing an existing binary. Make sure the install directory is in your PATH.

noodle update

Non-Homebrew installs download and verify the latest release before replacing the binary. Checks are cached for one hour; use noodle update --force to check immediately. Homebrew installs run brew upgrade noodle instead.

Teach your AI coding agent to create, organize, audit, import, and convert noodle collections. Supports OpenCode, Claude Code, Cursor, Copilot, and 70+ other agents.

npx skills add wilfredinni/noodle --skill noodle-use -g

Example prompts:

• "Scaffold a noodle collection for the Stripe API with auth and a few endpoints"
• "Audit my collection for security issues and REST best practices"
• "Convert this Insomnia export to a noodle collection"
• "Change the expand layout keybinding to Alt+I"
• "Set Catppuccin as my theme"
• "How many requests are in the Stripe API collection?"
• "What's the average response time for the login request on my Stripe collection?"
• "Order the folders on the Stripe collection from Z to A"
• "Set up basic auth on the Posts folder for $basic_user and $basic_password"

See the public roadmap for upcoming features and improvements.

Import requests from OpenAPI 3.0 specs or Postman collections:

noodle import ./specs/api.yaml

noodle without a subcommand remains the interactive TUI. Use the automation commands in scripts and agent workflows; collection paths are filesystem paths and request IDs are collection-relative paths without .yml.

Open a collection explicitly with a positional path or --collection:

noodle .
noodle --collection ./collections --env development

Without either option, noodle uses the first existing collection registered in ~/.config/noodle/config.yml, then falls back to the current directory. A directory with request YAML but no collection markers opens in read-only browse mode; an empty directory opens in read-only empty mode. Initialize either mode from the command palette before editing or sending requests.

Every automation command accepts --json, which emits exactly one { status, data, errors } envelope. Successful commands exit 0; invalid input and failed runs exit nonzero. Run commands use --env when supplied, otherwise the environment named in the collection's settings.yml.

Request IDs must be safe relative paths (for example users/list): no .yml suffix, traversal, empty path segments, or hidden segments. For example:

noodle collection create demo
noodle request create users/list --url https://api.example.com/users --collection ./demo
noodle environment set base_url https://api.example.com --env development --collection ./demo
noodle collection run ./demo --json

By default an imported collection is written beneath ./collections. Use --output to set its parent directory:

noodle import ./specs/api.yaml --output ./my-collection

bun install
bun run dev -- --collection ./collections --env development
bun test
bun run lint
bun run typecheck
bunx prettier --check ./src ./tests

Git hooks are installed automatically by bun install. The pre-commit hook formats and lints staged source and test files; the pre-push hook runs the typecheck and full test suite. Hooks can be bypassed for an exceptional commit or push with Git's --no-verify option, while CI remains the required check.