It is light: requests run in a small native process that starts on your first send and stops when idle, and views load only what you open.
Install
From the Visual Studio Marketplace. In VS Code, open the Extensions view (Ctrl+Shift+X, or Shift+Cmd+X on a Mac), search for Swastik Codes and click Install. You can also open the Marketplace page, or run:
code --install-extension swastik-codes.swastik-codesVS Code installs the build for your computer (Windows x64, macOS on Apple silicon or Intel, Linux x64) and updates it for you. It needs VS Code 1.90 or later. In VS Code Remote and WSL, install it in the remote window. The extension includes swc, so nothing else needs to be installed.
Without the Marketplace. Download the file for your computer and choose ⋯ → Install from VSIX… in the Extensions view:
A listing on Open VSX, for VSCodium, Cursor and other editors, is coming soon; until then they can install the .vsix file.
Sign in
Open Swastik Codes in the Activity Bar and choose Sign In. Paste an API key: in the web app, click your avatar, then Account settings → API keys. The key is stored in your system keychain and is only sent to the server it belongs to. You can send requests without signing in; signing in adds your collections and environments.
Send requests
- Open a request from Collections, or choose New Request (
Ctrl+Alt+N,Cmd+Alt+Non a Mac). - Edit params, headers, body (JSON, XML, text, URL-encoded, form data, a file or GraphQL), auth, pre-request scripts and tests.
- Press
Ctrl+Enterto send andCtrl+Sto save the request to its collection. - Paste a
curlcommand into the URL box to turn it into a request. - The response shows status, time and size, pretty JSON, headers, cookies, test results, console output and timings. Open in Editor shows the whole body in an editor tab.
- Copy as cURL and Generate Code in Python, JavaScript, Go, Java, C# and more.
Requests are sent from your computer, so localhost, your local network and VPN hosts work.
The request tab fits wherever you put it: request and response side by side when it is wide, one above the other when it is narrow or tall. Drag the divider to resize. The sidebar views can be moved to either side bar or the bottom panel.
Run collections as tests
Choose Run as Tests on a collection or folder. Each request is a test in the Test Explorer, and each pm.test assertion is listed under its request, so a failure shows which check broke. Run with Options adds iterations, a delay between requests, stop on first failure and a CSV or JSON data file. See the collection runner.
Keep a collection in sync with your code
Project Sync reads the open folder and finds its API routes: methods, paths, path variables, query parameters, request body fields and which routes need a login. It supports Express, NestJS, Fastify, Koa, Hono, Next.js, FastAPI, Flask, Django, Spring, ASP.NET, Gin, Echo, Fiber, Chi, Laravel, Rails, Sinatra, Actix and Axum, among others.
- Choose Scan and Link Project and pick a workspace and a collection (new or existing).
- After changing routes, choose Sync now, or turn on Sync on save.
- Preview changes shows what a sync would add, update or remove first.
Your edits, tests and examples in the collection are kept. The link is saved in a .swc.json file you can commit, so your team syncs the same collection. It works like GitHub sync and the swc CLI, from the editor.
Environments and secrets
The status bar shows the environment used for {{variables}}; click it to switch. For tokens and passwords, choose Set a value on this computer only: the value is kept in your system keychain, never uploaded, and overrides the shared value for you. Values your scripts set with pm.environment.set() are kept the same way. See environments and variables.
Everything else
Right-click a collection for a security check, a comparison of two environments, flaky test detection, test coverage, a load test, a local mock server and export to Postman or OpenAPI. Import Postman, OpenAPI, HAR and Insomnia files, and start the local bridge so the web app can reach localhost through your computer.
Privacy
In VS Code's Restricted Mode, requests cannot read files from the folder and the project is not scanned. In trusted folders, request bodies can only read files inside the folder. History stays on your computer, without response bodies and with credentials removed.