Files & configurations
Each project has a file tree that the sandbox materializes for every generation and run. It has two layers:
| Source | What it is | Writable via API? |
|---|---|---|
project | Files stored in TestVibe: your .feature sources, the AI-generated specs, your custom configs. | Partly — see the allowlist below. |
template | The Playwright scaffolding every project starts from (playwright.config.js, helpers, Configurations/Default.config.js). | No — read-only fallback. |
Reads check stored content first and fall back to the template, so you can inspect the stored file or inherited template. Dispatch may add runtime settings or generated bundle overlays.
File kinds
Files are classified by path: feature (Gherkin under Features/), spec (generated tests), config (under Configurations/), and supporting files.
The write allowlist
write_file is deliberately narrow. A write is accepted only if:
- the path is under
Features/orConfigurations/, - it contains no
..segments, - the content has at most 262,144 UTF-16 code units (the server labels this “256 KB”).
Generated JavaScript under Features/ is writable. A stored file can override a template configuration under an allowed root; other paths are rejected with 400 invalid_request.
Writing a new configuration? Read Configurations/Default.config.js first and use it as the reference shape; the guide walks through a Mobile config end to end.
Written files take effect on the next run or generation — there's no restart or publish step.