Skip to main content
Collections are identified by absolute path. Requests are identified by path within the collection (for example users/get-user.yml). Every tool is marked as read-only or destructive, so clients that ask for approval can prompt before writes.

Read

Run

Write

What the assistant sees

Do not point the assistant at production responses or cookies you would not paste into a chat.

How writes behave

  • .bru files change only where edited. A .yml request is rewritten in full (as the Bruno app does), so YAML comments in request files are lost. .yml environments and workspace.yml keep their comments.
  • Secret values are never written to files. A secret variable is saved by name only. The value is passed per run through variables.
  • Writes stay inside the collection. Paths outside it, or inside environments/, .git, or node_modules, are refused.
  • A batch is checked in full before anything is written, so one bad item means no changes. A disk error partway through is not rolled back. The result lists what was written.

Limitations

  • Runs locally over stdio. The collection must be on the same machine, and requests are sent from that machine. There is no hosted or shared team server.
  • Requests run through the Bruno CLI, not the app. Bruno global environments, app-only cookies, and auth flows that need a browser window are not available.
  • Each execute_request call is a separate run, so variables set by scripts (bru.setVar) do not carry to the next call. Run dependent requests together with run_collection.
  • write_request edits HTTP and GraphQL requests only. gRPC and WebSocket requests can be read and run, not edited.
  • Environments can be edited but not created.

Example prompts

  • “List the requests in the payments collection that use POST.”
  • “Run the orders folder against staging and summarize the failures.”
  • “Add Bruno requests for the endpoints in src/routes that the collection does not cover.”
  • “Add a test to Create order that checks the total is price times quantity.”
  • “Set baseUrl in the staging environment to https://api.example.com.”

Resources