Settings

Settings separates global preferences from configuration that belongs to the current collection.

Open Settings

Press F4 from any Noodle workspace to open Settings. Alternatively, press Ctrl+P, search for Open Settings, and press Enter. Settings opens on the global Appearance section; use the scope switcher to reach settings for the active collection.

The command palette also lists every application and collection Settings category, so searches such as Keyboard, Proxy, or Certificates open that category directly.

Global settings

Global settings apply wherever you use Noodle. They are stored in ~/.config/noodle/config.yml.

Appearance

Choose a theme and the default stacked or side-by-side layout. See Themes for the available themes.

Behavior

Choose whether undo-all asks for confirmation and select a detected external editor. The command palette uses that editor for Open Collection in Editor and Open Settings in Editor. Noodle detects Zed, Visual Studio Code, Sublime Text, Cursor, Windsurf, and VSCodium when installed.

Collections

Manage registered collection directories and their order. Noodle opens the first valid registered collection when no collection path is supplied, and the collection switcher updates this list as you work.

Keyboard shortcuts

Customize supported shortcuts from the Keyboard section. Fixed navigation and editing keys cannot be reassigned. See Keybindings for every available binding ID and default.

Proxy policy

Choose one of these global modes:

Mode	Behavior
System	Use HTTP_PROXY, HTTPS_PROXY, and NO_PROXY from the environment. This is the default.
Off	Send requests directly.
Custom	Send requests through one configured HTTP or HTTPS proxy.

For a custom proxy, set a credential-free URL such as http://proxy.example:8080. Enable Proxy authentication to enter a username and optional password. Noodle stores both in the OS credential vault; the config file keeps only the URL and auth: true. URLs containing credentials or $VARNAME placeholders are rejected.

The optional bypass list accepts comma-separated *, host names, .domain suffixes, IP addresses, and optional ports. Matching requests are sent directly.

Collection settings

Collection settings apply only to the active collection and are saved in its settings.yml file.

General

Set a display name and description for the collection. You can also set timeline_max_entries, which retains 50 responses per request by default. Lowering the value removes older entries; set it to 0 to disable response history for the collection.

The Cookie jar toggle is enabled by default. When enabled, Noodle captures Set-Cookie headers and sends matching cookies on later requests. Turning it off prevents both sending and capturing jar cookies for the collection. Use the request pane’s Send Cookies control when only one request should omit outgoing jar cookies.

Collection proxy

Choose one of these modes for the collection:

Mode	Behavior
Inherit	Follow the global proxy policy. This is the default.
Off	Send this collection’s requests directly.
Custom	Use a collection-specific HTTP or HTTPS proxy and bypass list.

Collection settings are useful when one API needs a corporate proxy while your other collections use the system setting or direct connections.

TLS and mutual TLS

Collection TLS settings can keep certificate verification enabled or disabled, replace the default roots with a custom PEM CA bundle, and select PEM client certificates by exact host and port. Relative paths resolve from the collection root. A custom CA bundle replaces the default roots, so include every root the collection needs.

For an encrypted private key, enter the passphrase in Settings. Noodle stores it in the OS credential vault and writes only a generated secret_id to settings.yml. Request files may override only tls.verify; --insecure disables verification for one TUI or automation invocation. PFX/PKCS#12 files are not supported; convert them to a PEM certificate chain and private key.

Proxy precedence

Noodle resolves proxy policy in this order:

1. --noproxy forces direct connections for one invocation.
2. A collection off or custom policy overrides the global policy.
3. A global off or custom policy applies when the collection inherits.
4. Otherwise, Noodle uses the system proxy environment variables.

Use --noproxy with the TUI, noodle collection run, or noodle request run when you need to bypass every saved proxy setting temporarily.

settings.yml is strict. Malformed YAML, unknown keys, wrong field types, and invalid proxy or TLS blocks stop collection opening, auditing, and execution until corrected; a missing or empty file still uses defaults.

File references

The Settings workspace edits the same files you can manage directly:

• Configuration documents global config.yml.
• Collection Format documents collection settings.yml.

The command palette’s Open Settings in Editor action opens the application settings directory in the selected external editor.