Advanced setup

A personal install of Syntic Code runs an interactive command that asks a few questions and stores its answers in your home directory. That flow is convenient for one person but wrong for a fleet, where installation has to be silent, deterministic, and driven by configuration you control. This page describes how to install and configure syntic without any prompts so the process fits into imaging scripts, device management tools, and CI runners.

Unattended installation

Install the CLI through your platform’s package manager or by fetching the release archive and placing the syntic binary on the system path. Pin an explicit version rather than tracking the latest release so every machine in a rollout ends up identical and upgrades are a deliberate step. A minimal script fetches the pinned version, verifies its checksum, installs it to a shared location such as /usr/local/bin, and confirms the binary runs:

SYNTIC_VERSION="1.8.0"
curl -fsSL "https://downloads.syntic.ai/cli/${SYNTIC_VERSION}/syntic-linux-x64" -o /usr/local/bin/syntic
chmod +x /usr/local/bin/syntic
syntic --version

Run this from your provisioning system rather than by hand, and log the output so failed installs are visible in your fleet dashboard.

Configuring a headless install

Because there is no interactive session, every setting a first run would normally ask for must be supplied in advance. Provide credentials and defaults through environment variables and a pre-placed settings file rather than the setup wizard:

export SYNTIC_API_KEY="…"
export SYNTIC_BASE_URL="https://api.syntic.ai"

Write a user or system settings.json before the first launch so the agent starts with your chosen model tier and permission rules already in place. Combined with server-managed settings, this means a freshly imaged machine is ready the moment a developer opens a terminal, with no onboarding steps and no chance to skip a required option.