Skip to content

VS Code vs Desktop

Nouto runs on two platforms with a shared UI and core feature set. Both support HTTP requests, GraphQL over HTTP, GraphQL subscriptions, WebSockets, SSE, gRPC, collections, environments, authentication, scripts, assertions, the mock server, benchmarks, and code generation. The differences are in storage and operating system integration.

Runs as a webview panel inside your editor. You access it from the activity bar without leaving VS Code.

HTTP client: Node.js via axios

Storage location: VS Code global extension storage by default

Storage modes: Global and workspace .nouto/collections/. See Storage Modes.

File watching: In workspace mode, Nouto watches collection files for external changes and reloads automatically.

Best for developers who want API testing integrated into their editor workflow, with collection files stored alongside their code.

A standalone application built with Tauri 2.0 and a Rust backend.

HTTP client: Rust via reqwest, with native gzip, brotli, deflate, and zstd decompression

Storage location: App data directory by default, or .nouto/ in an opened project folder

Projects: Desktop projects use the same per request .nouto/collections/ layout as VS Code workspace storage.

Deep links: Supports the nouto:// URL scheme for OAuth callbacks and external launches. See Deep Links.

Auto-update: Built-in update checker. See Auto-Update.

Best for developers who want a dedicated, lightweight API client that works outside of VS Code, or who need the desktop app’s native HTTP capabilities.

The JSON Explorer also ships on its own as the Nouto JSON Explorer VS Code extension. It runs the same viewer engine as the two clients above (tree and table views, search, query and JSONPath filtering, compare, type generation) but has no request, collection, or environment features.

Best for developers who want a fast JSON viewer in VS Code without installing the full REST client.

Feature VS Code Desktop
Global storage Yes Yes
Project .nouto/ storage Yes Yes
File watching for project files Yes Yes
Deep links (nouto://) No Yes
Auto-update No Yes
Native compression (brotli, zstd) No Yes

This table compares the two full REST clients. The standalone JSON Explorer extension is not a REST client and shares only the JSON viewing engine.