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.
Review before shipOffTurn it on to look at work before Tharas ships it. Off by default — the product is autonomous, and a checkpoint is something you ask for.
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 three, everywhere#

Settings are available from the command line, the dashboard and Telegram, and they mean the same thing on each. That is a rule in this codebase rather than a coincidence.

Review before ship can only make the ship gate stricter. There is no setting anywhere that ships unverified work.

FeaturesPlanning and approvalYou give Tharas an objective. It comes back with a specification, a task graph and an honest statement of what it cannot do — and then it holds gates on the way out, so nothing reaches your remote that has not been proven minutes earlier.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 local dashboardServed locally, from the machine the engine is already running on. It is where the onboarding wizard lives and where a long run is worth watching.