ConfigurationOverview

Configure Syntic Code

Most people change three things in their first week: the theme, a few permission rules, and a SYNTIC.md for each project. This section covers those and everything else you can tune. Each setting lives in a JSON file at one of a few levels, so personal preferences, team rules and organization policy stay apart.

Settings

PageCovers
Settings filesWhere settings live, which file wins, /config and syntic config, the .syntic folders.
Settings referenceEvery key, its type and default, and whether policy can set it.
Example settingsComplete files for personal use, a team project, CI and an organization.
Memory (SYNTIC.md)Project instructions, rules files, imports and auto memory.
Environment variablesEvery SYNTIC_* variable and the standard ones Syntic Code honors.

Permissions and sandboxing

PageCovers
OverviewThe layers that keep you in control.
Permission rulesAllow, ask and deny patterns, and the approval prompt.
Permission modesDefault, auto-edit, plan, auto, bypass and don’t-ask.
Folder trustWhat a folder may do before and after you trust it.
Commands that reach outsidePushes, deploys and other changes beyond your machine.
Shell sandboxRunning commands inside the operating system’s sandbox.

Model and responses

PageCovers
Models and reasoningChoosing models, effort, thinking, fallbacks and compaction.
Fast modeA quick swap to a lighter model.
The advisorA second opinion from another model on hard decisions.
Output stylesHow replies are written, and your own styles.

Interface

PageCovers
Terminal setupNew lines, notifications and terminal-specific setup.
Full-screen modeThe full-screen renderer, scrolling and the mouse.
AccessibilityScreen readers, reduced motion and color-blind themes.
ThemesColors and custom themes.
Status lineA footer line from your own script.
Keyboard shortcutsDefault keys and how to change them.

For administrators

Settings an organization enforces for every user are covered under Administration, starting with Managed settings.