Glossary

Short definitions for the terms used throughout the docs. Each one links to the page where the concept is explained in detail.

Active environment

The single environment whose variables are substituted into {{placeholders}} when a request is sent. Picked from the URL bar's environment picker. See Environments.

Attachment

A file stored in the workspace's data directory, referenced by ID from a multipart file field, a binary body, or a network TLS setting. See Data and storage.

Auth mode

The way credentials are attached to a request: No auth, Bearer, Basic, API key, or OAuth 2.0. Configured on the Auth tab. See Authentication.

Body mode

One of None, Raw, URL-encoded, Multipart, or Binary. Configured on the Body tab. See Request bodies.

Collection

The top-level container in a workspace. Holds folders and saved requests. Created and deleted through the sidebar.

Cookie jar

A named, persistent store of cookies used by requests with Use cookie jar enabled. Default jar is default. See Cookies and network.

Drizzle

The TypeScript ORM used by the API. Schema lives in apps/api/src/db/schema.ts; generated SQL migrations are in apps/api/drizzle/. See Architecture.

Eden Treaty

The end-to-end type inference layer between the SvelteKit app and the Elysia API. Lets the web app import App from @rewind/api/app and get typed client code without bundling the server. See Architecture.

Environment

A named bundle of variables. One environment is active at a time. See Environments.

Execution ID

A client-generated ID that the runner or the request area uses to identify an in-flight request, so the same client can cancel it later with DELETE /api/v1/executions/:id. The request area assigns one per Send.

Folder

A container inside a collection (or another folder) that holds requests and other folders.

Header row

A (key, value, enabled) triple in a request's Headers or Params table. See Query params and headers.

History

A list of every request that has been sent, in reverse chronological order. Lives at the bottom of the sidebar. See Viewing and filtering history.

History entry

A row in the history list. Contains the original request, the response, the duration, the size, the createdAt timestamp, and (on failure) an error: { category, message } object. See Viewing and filtering history.

Key-value pair

The shape of a header, a query parameter, an environment variable, or a form field. The wire shape is { key, value, enabled, secret?, description? }.

Local server

The Bun + Elysia process that listens on 127.0.0.1:8000 by default. It is the only thing the web app talks to.

Method badge

The small color-coded label that shows the HTTP method (GET, POST, PUT, etc.) on tabs, in the request panel, in the sidebar, and in the history list. Each method has its own token; the badge is implemented by the MethodBadge component in apps/web/src/lib/components/method-badge.svelte. See Workspace overview → Request area.

omit flags

Two opt-in flags on the workspace export: includeSecrets and includeResponseBodies. Both require explicit confirmation. See Exporting and backups.

OpenAPI

An API description format. Rewind's importer accepts 3.x documents. See Importing OpenAPI.

Postman Collection v2.1

A JSON schema for collections of HTTP requests. Rewind can import and export this format. See Importing Postman.

.rewind archive

A gzipped tar file holding the entire workspace, including attachments and (optionally) response bodies. See Exporting and backups.

Request draft

The in-memory, possibly-unsaved representation of a request in the request area. Saving it produces a saved request. Drafts can be opened without ever being saved.

Revision

A monotonically-increasing counter on every saved request. The server rejects saves that don't match the revision the client opened, which is how save conflicts are detected. See Saving and tabs.

Runner

The collection runner. A UI dialog and a CLI binary that executes every saved request in a collection in order. See Running a collection.

Saved request

A request that's been written to the database. Has a stable ID and a revision counter. Lives inside exactly one collection, optionally inside a folder.

Secret

A value marked with the secret flag in an environment variable, an auth field, or a header. Masked in the UI, in history, and in normal exports. See Variables.

Storage state

The status of a history entry's response body. One of stored, omitted_limit, or missing. Controls what the response panel shows. See Viewing and filtering history.

Tab

A request open in the request area. Tabs are independent — each has its own draft, its own save state, and its own dirty dot.

Variable

A (key, value, enabled, secret) tuple inside an environment. Referenced from request fields as {{key}}. Resolved server-side at send time. See Variables.

Web app

The SvelteKit application at http://localhost:5173. It is the only UI; there is no separate desktop app.

Workspace

The whole local Rewind installation. One workspace per data directory. The .rewind archive is a complete workspace export.