Project settings
Share setup, environment variables, and run commands across every task in a project.
On this page
Where settings live#
Each project can carry its own configuration file at the project root. Open Settings > Projects to edit it without touching the file by hand.
Project root
<project>/.videodraft/settings.tomlSettings resolve in layers. A later layer overrides an earlier one. A project with no configuration file behaves exactly as it did before.
| Layer | File | Use it for |
|---|---|---|
| User global | ~/.videodraft/settings.toml | Defaults you want in every project. |
| Project | <project>/.videodraft/settings.toml | Shared settings committed for the whole team. |
| Personal | <project>/.videodraft/settings.local.toml | Your own overrides. Kept out of git. |
Copy local files into new tasks#
A new task starts in a clean folder, so the files git ignores, such as .env.local, are missing. Files to copy brings them across for you.
- Enter one pattern per line. An empty box defaults to .env*.
- A .worktreeinclude file at the repository root overrides the setting.
- ADE copies only the files git ignores. It skips symlinks, binaries, files over 5 MB, and existing destinations.
- The task welcome screen reports how many files were copied.
Reuse local configuration
Copying configuration can save setup work in a new task. Dependency installation and other project setup still follow your project’s own instructions.
Environment variables and run commands#
- Environment variables set in Settings > Projects reach the setup script, the Run tab, and the agent process.
- Variables apply when a chat starts. Restart the chat, or run /restart, after changing them.
- Run commands appear in the Run button dropdown in the right panel and are saved to the same file.
- Each task also gets its own VIDEODRAFT_PORT, so parallel tasks can run servers without colliding.