Settings

These are the choices you make about your Tharas. They are deliberately not engineering knobs, and you should never need an environment variable to change one.

What you can set#

SettingDefaultWhat it means
Projects directoryA folder on your DesktopWhere Tharas creates new projects. The Desktop default is there so you can find them without being told where to look.
Share usage dataOnAnonymous data about which parts of Tharas work. Never your code, your file paths, what you asked for, or your keys.

The same settings, everywhere#

Settings are available from the command line and from the workspace — in a browser, in the desktop app and on a phone — and they mean the same thing on each. That is a rule in this codebase rather than a coincidence.

There is no setting that makes a build wait for you, and none that ships unverified work: what fails its checks is fixed by the next round, never shipped broken.

FeaturesPlanning and checksYou say what you want. Tharas writes a specification and a task list, builds each task and checks the work by actually running it — then it goes live. There is no approval step, and work that fails its checks is fixed by the next round, never shipped broken.FeaturesLocal-first and privateTharas runs where your code already is. What leaves the machine is an entitlement check and a small set of typed measurements — never a file, never a prompt, never a path.SurfacesThe workspaceThe screen most people use. A conversation, a live preview beside it, and every goal this project has had — with the whole engine one button away when you want it.