Workspace & storage format

A workspace is a regular folder. Its on-disk structure is the tree: there is no separate collection wrapper, so you can organise, move, and version requests with ordinary files and git.

Flat-file layout

Impostor saves each request as an individual <slug>.request.yaml file. The file name is automatically slugified from the request’s display name to ensure compatibility across file systems.

You can freely nest requests inside standard folders. Any folder can contain an optional settings.yaml file, which defines folder-scoped variables and authentication settings that are inherited by all child requests.

Environments and secrets

Environments are stored as YAML files within the hidden .env directory. Local-only data, such as your run history, is kept in the .impostor directory and is automatically ignored by git.

Secrets are never written to disk. Instead, Impostor stores them securely in your OS keychain, using placeholder references within the YAML files.

Collaboration

Because the workspace is just a directory of text files, you can use standard git workflows to review diffs, create branches, and share your workspace with your team, entirely avoiding complex proprietary sync servers.