Skip to main content
Cookies are used to store user information, session data, and provide personalized content. Bruno allows you to add, send, view, and delete request cookies. After executing the request, you can easily inspect the cookies by clicking on the Cookies icon.
  • Domain: Specifies the domain where the cookie is valid.
  • Path (optional): Specifies the URL path where the cookie will be sent.
  • Key: The name/identifier of the cookie.
  • Value: The data that the cookie will store.
  • Expiration: The expiration date and time for the cookie.
  • Secure: Ensures the cookie is only sent over HTTPS.
  • HTTP Only: Restricts access to the cookie from JavaScript.

​
Configuring Cookies in Bruno

  1. Go to cookies section (bottom-right corner).
  1. Click on Add Cookie button.
  1. Add the cookie attributes and select Secure or HTTP Only according to your preference.
  1. Click on Save button.
  2. You can enable Raw Edit mode to quickly customize and make direct changes to your cookies.
You can update and delete cookie(s) by clicking the icons next to it.
  1. Click on (pencil icon) to update cookie.
  2. Click on delete icon (red colour) to delete cookie.
We restrict editing of values like Domain, Path, and Key once a cookie is created due to security concerns.
To manage cookies programmatically, see the Cookie Management section in the JavaScript API Reference.

​
Cookies in Collection Runs

When you run a collection via the Collection Runner or the Bruno CLI, Bruno automatically saves and forwards cookies between requests. This includes cookies set by responses with any status code - 2XX, 4XX, and 5XX responses all have their Set-Cookie headers processed. To disable automatic cookie handling in the CLI, pass the --disable-cookies flag:
In the desktop app, you can toggle cookie storage off in Preferences → General → Store Cookies automatically.