Repository navigation
Releases
Plainwire 0.17.0
- Import straight from Thunder Client's own storage: no export, no login. Plainwire: Import from Thunder Client… now lists every folder on this computer where Thunder Client keeps its data (
globalStorage/rangav.vscode-thunder-clientof VS Code, Insiders, Cursor, Windsurf, VSCodium, Code - OSS, Trae, Kiro and Positron, their profiles and remote*-serverfolders, the workspace'sthunder-tests, and a Custom Location set in Thunder's settings), with what each holds ("2 collections, 41 requests, 1 environment, 120 history entries"). Pick one and its collections, folders, environments and tests become.httpfiles. Thunder Client does not need to be installed or signed in. - Once, after startup, when such data exists and a folder is open, Plainwire offers the import in a notification (Import / Don't ask again; setting
plainwire.offerThunderImport). It reads local files only; nothing is sent anywhere. - Every storage layout: per-collection
collections/tc_col_*.json+environments/tc_env_*.json, the legacythunderclient.json/thunderCollection.json/thunderEnvironment.json, the older NeDB databasesthunderclient.db/thunderCollection.db/thunderEnvironment.db(later records replace earlier ones, deleted ones are dropped), request bodies written as arrays of lines (Thunder 2.39+), and requests stored one file each. Backup folders are skipped. - History too, if you want it: Thunder's Activity tab (
thunderActivity.json/.db) imports as one Thunder Client history file, newest first, duplicates removed. - CLI:
plainwire import --thunder [--history]finds and imports that data;plainwire import <folder>reads any Thunder data folder;.dbfiles can be passed directly. The website converter accepts.dbfiles.
Plainwire 0.16.0
From a hand-walk of streams, GraphQL, cURL paste, Copy as Code, OAuth 2 and the tree in a real VS Code window.
- Type messages into an open WebSocket. While a connection is open, a message box under the live view sends what you type at once (Enter sends, Shift+Enter adds a line); it shows up in the list with its reply. Typed messages restart the time limit, so a session stays open while you use it. Before, the only way to send another message was to edit the script and reconnect.
- Send from the sidebar into a new tab keeps the live view. A request sent from the Requests view (or a CodeLens) into a tab that was not open yet lost its "Sending…" state: a WebSocket stayed connected with no messages shown and no Stop button, and a slow request showed the empty response pane until it returned. The send now waits until the tab is ready.
GRAPHQL <url>requests (the JetBrains HTTP Client's keyword) are sent as POST with the{"query", "variables"}JSON body, open with the GraphQL body editor, and work in Copy as Code and the CLI. Before, the literal methodGRAPHQLwent to the server, which answered 400.GRAPHQLis also in the method list and highlighted in.httpfiles.- Secondary buttons (Save, Acquire token now, Use this environment) have a visible outline in themes that make them transparent, such as Dark Modern.
- Real VS Code screenshots for the WebSocket and server-sent events guides.
Plainwire 0.15.0
From a hand-walk of the environment editor, Run all, imports and Save in a real VS Code window.
- A missing
{{host}}tells you which environment has it. Sending a request while no environment (or the wrong one) is selected used to stop at "Variable {{host}} is not defined". Now the message says "It is defined in environment "dev" and "staging", but no environment is selected", with Use dev and send buttons (and Edit environments…). Run all shows the same sentence, and the CLI adds "Run with --env dev". - Environment editor: opens on the active environment (before: the empty Shared tab), has a Use this environment button and a ✓ Active mark, and offers Add to .gitignore in a git repository that has no
.gitignoreyet (before it only showed a hint, sogit add .could commithttp-client.private.env.json). - Run all: clicking a row opens the request with that run's response and checks (the Tests tab when a check failed), not an empty response pane.
- Import from Thunder Client, Postman, OpenAPI or cURL now shows the imported collection in Plainwire's Requests view, expanded and selected, next to the first file.
- Save of a new request asks for its name (the
### titleshown in the Requests view, like naming a request in Thunder Client); leave it empty to show the URL. - History rows read "POST Create user" or "GET /users/1" instead of "POST {{host}}/us…".
- The response summary (status, time, size, checks) wraps between items instead of inside them in a narrow pane.
- Real VS Code screenshots of the environment editor and the Run all report in the README.
Plainwire 0.14.0
- Request and response side by side. The request editor now puts the response next to the request whenever the tab is at least 820 px wide (before: only from 1100 px, so on most laptops the response sat under the request and shrank when the request had scripts or many headers). A Side by side / Stack button switches the layout, and the divider between the two halves can be dragged (double-click resets it). The choice is remembered for every request tab.
- Filter the response. A filter box above the response body: a JSONPath (
$.items[*].id,$..name,$.users[?(@.active)],$.orders[?(@.total > 100)].id,$.list[0:5],$.a['b','c']) shows only the matching values with a count; any other text lists the lines that contain it, highlighted, with line numbers. Works on JSON, HTML, XML and text responses. - + Add as test next to a single filtered value adds
# @assert $.path == valueto the request, so exploring a response becomes a check that runs on every send, in Run all and in the CLI. - New Request puts the cursor in the URL box. "1 check passed" instead of "1 checks passed". The request tabs wrap instead of being cut off when the request half is narrow.
Plainwire 0.13.0: JavaScript scripts
- JavaScript in
.httpfiles, in the JetBrains HTTP Client format.< {% … %}above the request line runs before the request (request.variables.set('sig', …)for this request only;request.environment.get,request.url.tryGetSubstituted(), headers and body).> {% … %}after the request runs on the response:client.test('name', () => client.assert(response.status === 200, '…')),client.global.set('token', response.body.token),client.log,client.exit();response.status,response.body(parsed JSON or text),response.headers.valueOf(name),response.contentType.< ./sign.js/> ./check.jsload the code from a file. Helpers:crypto(MD5/SHA-1/SHA-2 and HMAC, hex or Base64),$random,jsonPath,btoa/atob,console.log. For server-sent events and WebSocket,response.body.onEachMessage(…)replays the received messages. Before, these blocks were kept in the file but never run. REST Client has no scripting (#521); in Thunder Client it is a paid feature. client.globalvalues work as{{name}}in later requests (after request, file and environment variables), are kept per workspace, and are listed and cleared with Plainwire: Show / Clear Script Variables (client.global)…. A request that uses a variable only a handler sets says which request to send first.client.testresults appear with the# @assertchecks: in the Tests tab, Run all, and the CLI reports (JUnit, JSON, Markdown, GitHub annotations). An error in a handler is a failed check; an error in a pre-request script stops the request ("Not sent: …").- Request editor: a Scripts tab to edit both scripts; the response's Tests tab shows the script log.
- Scripts run in a separate Node
vmcontext with a 5 second limit, only in trusted workspaces (Plainwire does not run in Restricted Mode). Settingplainwire.runScripts(default on) skips them. - Postman import keeps scripts that run. Test scripts that are plain checks still become
# @assertlines; any other test script (setting variables, conditions, loops) and every pre-request script is kept whole as a> {% %}/< {% %}block and runs with a Postman-compatiblepmAPI:pm.test,pm.expect(the common chain),pm.response(code,json(),text(),headers,to.have.status/header/body/jsonBody,to.be.ok/json),pm.environment/collectionVariables/globals/variables, and the oldertests["…"],postman.setEnvironmentVariable,responseBody.pm.sendRequest,require()andpm.visualizerare not supported (the import warns). Folder- and collection-level scripts are still skipped with a warning. - CLI:
plainwire run --no-scripts;-vprints every script's log, and a failed request prints its log.
Plainwire 0.12.0: WebSocket requests
- WebSocket requests, in the JetBrains HTTP Client format:
WEBSOCKET wss://host/path(also a barews:///wss://URL, or httpYac'sWSkeyword), headers for the handshake, then the messages. The first message is sent on connect;===separates messages;=== wait-for-serverwaits for one message from the server before the next is sent (repeat it to wait for more). A script that ends with=== wait-for-servercloses the connection (code 1000) once those replies arrived; otherwise it listens until the server closes, you press Stop,# @max-events Nmessages arrived, or the timeout (# @timeout,plainwire.timeoutMs). All of these keep what arrived. {{variables}}, environments, chained requests, OAuth 2 tokens and the cookie jar work for the handshake and every message. A message can be< ./file(sent as binary) or<@ ./file(text with variables). TLS settings (# @insecure) and proxies (CONNECTforwss://) as for HTTPS. Pings are answered, fragmented messages joined; no compression extension.- The response view lists every message with a direction arrow and its time (live while connected), the close code and reason, and a Transcript view. A refused upgrade (e.g.
401) is shown as a normal HTTP response with its body. - Checks:
messages= messages received (messages.length,messages[-1].data.type),events= all messages both ways (eventissent,messageorbinary), and$.xreads the last JSON message received. - CLI:
plainwire runsends WebSocket requests too; the result line reads1 sent, 2 received (done). - Editor:
WEBSOCKETin the method list, a hint in the Body tab, syntax highlighting forWEBSOCKET/WSand===lines. Copy as Code explains that it covers HTTP requests only.
Guide: https://janwan2003.github.io/vscode-api-client/websocket-client-vscode.html
Install: download plainwire-0.12.0.vsix and run Extensions: Install from VSIX… (VS Code, Cursor, Windsurf, VSCodium). CLI: plainwire.mjs (Node 20+) or npm install -g the tgz.
Plainwire 0.11.0: folders and drag and drop
- Folders in the Requests view: the sidebar now shows your workspace's folders, then the
.http/.restfiles in each, then the requests in each file (before: one flat list of file paths). A folder whose only child is a folder shows as one row (api/v2); settingplainwire.collections.compactFolders. Multi-root workspaces get one top-level node per folder. - Drag and drop: drag requests onto a request (reorder within a file, or move to that place in another file) or onto a file (move to its end); several selected requests move together, in order. Drag files and folders onto a folder to move them (a normal rename, so open editors follow). Dragging a file into the editor area opens it.
- Request actions in the context menu: Rename… (
F2, edits the###line only), Duplicate (a copy below, title "(copy)", a free# @namesuch ascreate2so chaining still points at the original), Move Up / Move Down (Alt+↑/↓), Move to File… (any.httpfile or a new one), Delete (asks first;Deletekey). Files and folders: New .http File…, New Folder… (starts withrequests.http;orders/listcreates subfolders), Rename…, Delete (to the trash), Run All Requests in Folder. - Every request edit is made on the file's text: the moved block is copied verbatim (comments,
# @name, checks, scripts) and every other line stays byte for byte, CRLF files stay CRLF, and the edit goes through the editor so Undo works. File variables and# @importlines in a moved block stay in their file (they apply to the whole file). Moving a# @namerequest that its old file still chains to ({{login.response…}}) shows the# @importline to add. - Open request tabs follow their request when it is reordered or moved to another file, and their file when it is renamed or moved.
- Import: nested folders become subfolders. A Postman or Thunder Client folder inside a folder is written to
Collection/Orders/Refunds.httpinstead ofCollection/Orders - Refunds.http. Also in the CLI (plainwire import) and the online converter.
Install: download plainwire-0.11.0.vsix and run Extensions: Install from VSIX… (VS Code, Cursor, Windsurf, VSCodium). CLI: plainwire.mjs (Node 20+) or npm install -g the tgz.
Plainwire 0.10.0: OAuth 2.0 tokens, environment editor
- OAuth 2.0 tokens:
{{$auth.token("id")}}and{{$auth.idToken("id")}}in any URL, header or body. The configuration lives in the environment, in the JetBrains HTTP Client format:"Security": { "Auth": { "id": { "Type": "OAuth2", "Grant Type": …, "Token URL": …, "Client ID": … } } }. A token is fetched before the first request that needs it, reused while it is valid, refreshed with its refresh token 30 s before it expires, and fetched again when the refresh fails. REST Client had no OAuth support (#302). - Grant types: Client Credentials, Password, Authorization Code with optional PKCE (SHA-256 or plain; the sign-in opens in your browser and Plainwire receives the redirect on
http://127.0.0.1/localhost, a free port by default), Device Authorization (the code is shown and copied, polling honoursslow_down), Implicit, and"Type": "Mock"for a fixed token. Keys:Client Credentials(basicdefault,in body,none),Scope,Redirect URL,Custom Request Parameters/Custom Request HeaderswithUse(Everywhere,In Auth Request,In Token Request),Acquire Automatically,Use ID Token,Open Complete URI; any value can use{{variables}}. Checked live against Duende's public IdentityServer demo: Client Credentials, and Authorization Code + PKCE through a real browser login, including a refresh after the token expired. - Object values in env files now merge key by key across
http-client.env.json→http-client.private.env.jsonand$shared→ the selected environment, so the private file can hold just theClient Secret. (Before, a later object replaced the whole value.) - Request editor: the Auth tab has an OAuth 2 option (pick a configuration of the current environment, send the ID token instead, Acquire token now).
- Commands Plainwire: Acquire OAuth 2 Token… (fresh token now) and Plainwire: Clear OAuth 2 Tokens. Tokens stay in memory for the window; they are not written to disk or history. Copy as cURL / Code uses a cached token and never starts a sign-in.
- A JSON schema for
http-client.env.json/http-client.private.env.json: completions and hover text for every auth key and value. - CLI: one token per
plainwire run; browser grants print the sign-in URL (and open a browser in a terminal);-vlogs token activity. - Site: the "Cookies and session logins" guide's main content was rendered inside the page header (missing tags); fixed.
- Environment editor: Plainwire: Edit Environments… (also Edit environments… in the status-bar environment picker and in the Requests view's
…menu) opens a form overhttp-client.env.json: environments as tabs with Shared (all environments) first, and per variable a name, a value and a Secret box. Add, rename and delete variables and environments; Save orCtrl/Cmd+S, with an unsaved-changes marker. - Secret values go to
http-client.private.env.jsonin the same folder (created on first save) and are masked until you click Show. If the workspace's.gitignoredoes not cover that file, the editor says so and adds it in one click. - Nothing you do not edit is lost: values that are not strings (objects such as an OAuth
Securityblock, arrays, numbers, booleans) are shown read-only with Open JSON and written back as they were,$schemaand other keys are kept, existing keys keep their order, and a file whose content does not change is not rewritten. Files are written with 2-space indent and a trailing newline. - Several
http-client.env.jsonfiles in the workspace: pick which folder's pair to edit. With none, the files are created in the first workspace folder. If the files change on disk while the editor is open, it reloads (no unsaved edits) or offers Reload / Overwrite. The active environment is still chosen in the status bar, and it picks up saved changes straight away.
Install: download plainwire-0.10.0.vsix and run Extensions: Install from VSIX… (VS Code, Cursor, Windsurf, VSCodium). CLI: plainwire.mjs (Node 18+) or npm install -g plainwire-cli-0.10.0.tgz. Guide: https://janwan2003.github.io/vscode-api-client/oauth2-http-file-vscode.html
Plainwire 0.9.0: cookies and session logins
- Cookie jar: cookies a response sets are kept and sent with later requests to the same site, like a browser, so a login that sets a session cookie works for the requests after it. Cookies set on a redirect hop are stored before the redirect is followed (login → 302 → dashboard works). RFC 6265 domain/path/Secure/expiry rules; your own
Cookie:header wins by name. In 0.8.0 no cookie was carried between requests. - Per workspace, saved across reloads. Plainwire: Manage Cookies… / Clear Cookies; setting
plainwire.rememberCookies;# @no-cookie-jarper request (same spelling as REST Client and JetBrains). - Response view Cookies tab;
# @assert cookie sessionid exists. - CLI: one jar per
plainwire run,--no-cookie-jarto turn it off. Checked against httpbin.org's cookie endpoints: 5/5 with the jar, 3 passed / 2 failed without.
Guide: https://janwan2003.github.io/vscode-api-client/cookies-session-login-http-file.html
Install: download plainwire-0.9.0.vsix and run Extensions: Install from VSIX… (VS Code, Cursor, Windsurf, VSCodium). CLI: plainwire.mjs (Node 18+) or npm install -g the tarball. Action: uses: janwan2003/vscode-api-client@v0.9.0.
Plainwire 0.8.0: import OpenAPI from a URL
- Import OpenAPI / Swagger from a URL: the Import OpenAPI / Swagger… command now asks From a file… or From a URL…, and
plainwire importacceptshttps://…URLs (redirects followed, proxy and--insecurehonoured). A relative server URL such as/api/v3now resolves against the definition's URL, as the OpenAPI specification says (Swagger 2.0: a missinghostis the host serving the definition), instead of falling back tohttp://localhost. Checked with the public Petstore 3 definition: imported from its URL, two requests then passed against the live server without settingbaseUrl.
Also new today: 0.7.0 (server-sent events, # @timeout, default User-Agent) and 0.6.0 (# @import of another .http file); see CHANGELOG.md.
Install: download plainwire-0.8.0.vsix and run Extensions: Install from VSIX… (VS Code, Cursor, Windsurf, VSCodium). CLI: plainwire.mjs (Node 18+) or npm install -g the tarball. Action: uses: janwan2003/vscode-api-client@v0.8.0.