Session behavior and secrets
Working alongside the app
Section titled “Working alongside the app”The app and kurlo mcp can have the same workspace open. They take turns writing it, so neither reads the other’s half-written save. The app learns about files changed outside it from the operating system (FSEvents on macOS, ReadDirectoryChangesW on Windows, inotify on Linux) and reloads them within about a second, with a short notice; where that is unavailable it checks the folder once a second instead. If the app saves before it has reloaded, for example because you were typing in a request at that moment, it writes your edits and then puts back every file changed outside it that your edits did not touch. Only when both changed the same file does the app’s version win.
The same protection covers files changed by an editor or by git pull in a terminal.
Checking a call the way a browser would
Section titled “Checking a call the way a browser would”An API call that works from the assistant can still be refused in the browser, where CORS applies. run_request and send_request take browserOrigin, the origin of the page that would make the call, such as https://app.example.com. Kurlo then sends it with browser emulation: browser headers and Origin, the CORS preflight when the method or headers need one, and the CORS error a browser would raise, in the result’s error. Add browserCredentials: true for a call made with credentials: 'include', which a wildcard Access-Control-Allow-Origin does not satisfy.
A saved request that already has browser emulation turned on, by itself or through its collection, is sent with those settings even without browserOrigin.
Variables carry across calls
Section titled “Variables carry across calls”A value a script sets with pm.environment.set or pm.collectionVariables.set is kept for the rest of the session, per environment. An assistant can run your login request once, and the token it stores is used by every request after it, just as in a collection run. Each result lists the variables the call changed in variablesChanged. These values live only in the server’s memory. They are not written back to the workspace, and they are gone when the assistant restarts the server.
When a request uses a {{variable}} that no environment, call override or script has set, the result lists it in unresolvedVariables. The request is still sent with the placeholder as written, so a 401 next to unresolvedVariables: ["token"] tells the assistant to run the login request first or pass the value in variables.
Cookies and OAuth 2.0 tokens are kept for the session too. OAuth works the same way as in kurlo run: Client Credentials and Password grants are fetched, and browser grants use their refresh token.
Secrets
Section titled “Secrets”Environment variables marked secret are used when requests are sent, but they are masked as [secret] in everything returned to the assistant. That covers the resolved URL, response headers and body, test messages and script logs. A server that echoes your token back does not hand it to the model. list_environments shows only the names of secret variables, and get_request never includes credentials. The write tools never store a secret either: see Secrets stay out.