Getting startedPlatforms and integrationsOverview

Platforms and integrations

Syntic Code is one agent that can reach you in several places. The terminal app is the main one today and the one these docs describe in full. This page lists every surface, what state it is in, and the integrations that connect the agent to the rest of your tools.

Where to run Syntic Code

SurfaceWhat it isStatus
CLIThe syntic command: an interactive terminal app, plus one-shot and background modes for scripts and long jobs.Available
DesktopSyntic Code Desktop, a desktop app with the same agent built in.Guides in progress
VS CodeAn editor extension.Coming soon. Run syntic in the editor’s integrated terminal meanwhile.
Chrome extensionA browser extension.Coming soon

Settings, permission rules, memory files, skills, hooks and MCP servers live in the same .syntic folders whatever surface you use (The .syntic folder). What you set up for the CLI carries over as the other surfaces arrive.

Ways to run the CLI

ModeCommandUse it for
InteractivesynticEveryday work at the keyboard.
One-shotsyntic -p "<task>"Scripts, git hooks, CI jobs (Scripting and CI).
Backgroundsyntic --bg "<task>"Long jobs that keep running after you close the terminal (Background sessions).
Isolatedsyntic -w <name>A session in its own git worktree, next to others on the same repository (Worktrees).

The CLI runs on macOS, Linux and Windows.

Connect your tools

IntegrationWhat it gives the agentPage
MCP serversTools and data from outside systems: trackers, databases, docs, internal APIs.MCP servers
Git hostsPull requests, reviews and CI through the gh and glab command-line tools.Code review, Run in CI pipelines
A local browserOpen pages, click, type and take screenshots in a Chrome or Chromium it starts itself. Off until you turn it on.Browser and computer use
Your screenScreenshots, mouse and keyboard on macOS. Off until you turn it on.Browser and computer use
PluginsBundles of skills, agents, hooks and MCP servers from a marketplace.Plugins
Linkssyntic-cli:// links that open a session with a prompt filled in.Open a session from a link
ChannelsAn MCP server that pushes messages (a chat bridge, a webhook relay) into a running session.Channels

Keep work going when you step away

You want toUse
Start a long job and close the laptop lidsyntic --bg "<task>", then syntic logs <id> or syntic attach <id> later.
See every running job across projectssyntic agents (The agents view).
Run a prompt on a timetable while a session is open/schedule and /loop (Loops and schedules).
Keep going until a condition holds/goal <condition> (Goals).
Run without any session opensyntic -p from your system scheduler or CI.
Pass a note from one session to anotherMessaging between sessions.

Syntic Code always runs on your own machine (or your own CI runner). There are no hosted cloud sessions: the files it edits and the commands it runs stay on the computer where you started it.