Project settings

Share setup, environment variables and run commands across every task in a code project.

On this page

Where settings live Copy local files into new tasks Environment variables and run commands

Where settings live#

Open Settings > Project settings to edit a project’s configuration. It is saved in a file at the project root, which you can also edit by hand.

Project root

<project>/.videodraft/settings.toml

Settings stack in layers. A later layer overrides an earlier one. A project without a file keeps the defaults.

Layer	File	Use it for
Your defaults	~/.videodraft/settings.toml	Settings you want in every project.
Project	<project>/.videodraft/settings.toml	Shared settings, committed for the team.
Personal	<project>/.videodraft/settings.local.toml	Your own overrides. Kept out of Git.

Copy local files into new tasks#

A new isolated task starts from a clean copy of the repository, so files Git ignores, such as .env.local, are missing. Files to copy brings them across.

Enter one pattern per line. An empty box copies .env* files.
A .worktreeinclude file at the repository root takes priority over this setting.
ADE copies only files Git ignores. It skips symlinks, binary files, files over 5 MB and files that already exist.
The task’s welcome screen shows how many files were copied.

Copying is not setup

Installing dependencies and other setup still follow your project’s own instructions or setup script.

Environment variables and run commands#

Environment variables set here reach the setup script, the Run tab and the agent.
Variables load when a chat starts. Run /restart after changing them.
Run commands appear in the Run button’s menu in the right panel.
Each task gets its own VIDEODRAFT_PORT, so tasks can run servers at the same time.