Setup
Getting Syntic Code onto one machine takes a single command. Getting it onto every developer’s machine in a way you can support, secure, and update is a different problem, and this section addresses it. The pages here cover installing the CLI at scale, deciding how developers prove their identity to api.syntic.ai, and pinning settings so that some choices are made once, centrally, rather than by each person.
From a personal install to a managed fleet
A managed rollout differs from a personal one in three ways. First, installation must be repeatable and unattended, so it can run from an imaging script or a device management tool. Second, authentication has to fit your existing identity story rather than asking every developer to paste a key. Third, certain settings, such as which model tier is allowed or which tools are forbidden, need to be enforced from a server so that individuals cannot quietly change them.
What each page covers
- Advanced Setup walks through scripted, non-interactive installation and the environment variables that shape a headless deployment.
- Authentication explains the ways
synticcan obtain credentials for the Syntic model, from API keys to organization-managed sign-in. - Server-Managed Settings shows how to distribute a settings file that takes precedence over anything a user configures locally.
- Managed MCP Configuration describes pushing a curated set of MCP servers to every install so developers share the same tools.
- Auto Mode covers running the agent without interactive prompts for pipelines and batch work.
Work through the pages in order for a first rollout. Once the fleet is stable, the later pages become the levers you use to tighten or expand what your developers can do.