SDKHosting

Hosting programs

Syntic Code runs on the machine where you start it. A program that uses the agent runs syntic on a machine you control: a developer’s laptop, a CI runner, a server, or a container. This page covers what that needs.

Syntic Code does not provide hosted or self-hosted run environments. Sessions are not run in Syntic’s cloud, and there is no managed runner to rent.

What a host needs

  • The syntic binary on the PATH, installed by the method in Install.
  • Network access to the Syntic platform. Model requests go only to api.syntic.ai and app.syntic.ai over HTTPS. See Network configuration.
  • A sign-in credential that the host can read. A host with no browser signs in with a refresh token kept as a secret. See Sign in without a browser.
  • The repository checked out in the working folder the run starts in.

Sign in on a server

Store the refresh token in your CI or server secret store, not in the repository. Set it as SYNTIC_OAUTH_REFRESH_TOKEN for the run; syntic setup-token stores a token for a host that will run many jobs. Syntic Code strips the credential variables from the environment of every command, hook and MCP server it starts, so a tool the agent runs cannot read them.

Working folders

A run works inside the folder it starts in. File tools are limited to the working folders, and a symlink that points outside them is refused. A folder must be trusted before project settings, hooks and MCP servers load. In an untrusted folder, a run starts in a restricted state. See Folder trust.

Containers and throwaway hosts

On a disposable host, such as a container that is destroyed after each job, the bypass switch --dangerously-skip-permissions can replace a permission setup you have already reviewed. Deny rules still apply. Do not use it on a host that outlives the job.

syntic -p "update the changelog for this release" --permission-mode acceptEdits --output-format json

Several runs at once

Each run has its own session id, which is printed in the JSON result. Use --session-id to name a session you will resume later with --resume, and --no-session-persistence for a run that must leave nothing on disk.

Corporate networks

Route Syntic Code through a proxy, and add internal certificate authorities, with the settings in Network configuration.

⚠️

Do not run a program that uses the agent on a shared host with other users’ credentials in its environment. Give each job its own sign-in.