feat: add cookie support for requests and responses

.github/workflows/release.yml

@@ -25,7 +25,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           # Full history is required — semantic-release needs to walk back
           # to the previous tag to find all commits in this release.
@@ -37,7 +37,7 @@ jobs:
           persist-credentials: false
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: "22"
           cache: "npm"

.github/workflows/validate-pr-title.yml

@@ -21,7 +21,7 @@ jobs:
 
     steps:
       - name: Validate PR title
-        uses: amannn/action-semantic-pull-request@v5
+        uses: amannn/action-semantic-pull-request@v6
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:

.vscodeignore

@@ -0,0 +1,24 @@
+# Source files
+src/
+scripts/
+
+# Dependencies (bundled by Vite, not needed at runtime)
+node_modules/
+
+# Config and tooling
+.github/
+.vscode/
+.claude/
+docs/
+tsconfig.json
+tailwind.config.js
+postcss.config.js
+.releaserc.js
+.gitignore
+
+# Build artifacts not needed in extension
+**/*.vsix
+**/*.map
+
+# Dev docs
+CLAUDE.md

CHANGELOG.md

@@ -56,6 +56,7 @@ The following features are being considered for future releases:
 - [ ] Response diff / compare
 - [ ] Mock server / request stubs
 - [ ] Team sync / shared collections
+- [x] Cookie support — send cookies with requests, view Set-Cookie response cookies
 
 ---
 
@@ -76,6 +77,17 @@ The following features are being considered for future releases:
   - Inherits from parent folders
 - cURL export updated to include Basic Auth and API Key in generated commands
 
+#### Cookie Support
+
+- **Request Cookies** — Add name/value cookie pairs in the new "Cookies" tab on any request
+  - Cookies are serialized as `Cookie: name=value; name2=value2` header when sending
+  - Supports `{{variable}}` interpolation for cookie names and values
+  - Enable/disable individual cookies with checkboxes
+  - Saved with the request, so cookies persist between sessions
+- **Response Cookies** — Set-Cookie headers from responses are parsed and displayed in a "Cookies" tab on the response panel
+  - Shows name, value, Path, HttpOnly, and Secure attributes
+  - Badge on the Cookies tab shows the number of cookies received
+
 ---
 
 ## [0.2.0] - 2026-03-07

CLAUDE.md

@@ -64,7 +64,7 @@ Three independent React apps are built separately by Vite as IIFE bundles and lo
 
 Each webview communicates with the extension host exclusively via `vscode.postMessage` / `webview.onDidReceiveMessage`. There is no shared module between the extension host and webview code at runtime — types in `src/webview/types/internal.types.ts` are shared at the TypeScript level only.
 
-The webview alias `@` maps to `src/` (configured in `scripts/build.ts`).
+The webview alias `@` maps to `src/` (configured in `scripts/build.mts`).
 
 ### Request webview state
 
@@ -76,7 +76,31 @@ The webview alias `@` maps to `src/` (configured in `scripts/build.ts`).
 
 ### Build system
 
-`scripts/build.ts` runs four parallel Vite builds: one CJS build for the extension host and three IIFE builds for the webviews. The `@vitejs/plugin-react` uses the classic JSX runtime (`React.createElement`). Node built-ins and `vscode` are externalized from the extension build.
+`scripts/build.mts` runs four parallel Vite builds: one CJS build for the extension host and three IIFE builds for the webviews. The `@vitejs/plugin-react` uses the classic JSX runtime (`React.createElement`). Node built-ins and `vscode` are externalized from the extension build.
+
+## CHANGELOG.md Maintenance
+
+The `CHANGELOG.md` file has a fixed structure that must be preserved:
+
+```
+## Future Roadmap        ← always the very first section
+- [ ] pending item
+- [x] completed item     ← mark done when implemented, never remove
+
+---                      ← separator
+
+## x.y.z (date)         ← newest release entry goes here, just below the separator
+...
+
+## older releases
+...
+```
+
+Rules:
+- **Future Roadmap is always first** — it must remain at the top of the file above all release entries.
+- **Mark items done, never delete them** — when a roadmap item is implemented, change `- [ ]` to `- [x]`. Do not remove the line.
+- **New release entries go just below the roadmap** — insert a new `## x.y.z` section immediately after the `---` separator, above previous releases.
+- **Adding new roadmap items** — append to the `## Future Roadmap` list as `- [ ] description`.
 
 ## Publishing