Automating Syntic Code

Syntic Code is designed to run wherever your work happens — not just in an interactive terminal. The automation surface lets you drive the syntic CLI and Amara from scripts, pipelines, schedulers, and other applications, turning the agent into a programmable building block rather than a tool you sit in front of.

This section covers every mechanism for triggering, extending, and integrating Syntic Code without a human at the keyboard. Whether you want to react to events in your codebase, run recurring maintenance, pipe structured output into another system, or launch a session from a link, the patterns here compose cleanly.

What you can automate

Automation in Syntic Code falls into a few broad categories. Hooks run your own commands at defined points in the agent lifecycle, letting you enforce policy, log activity, or inject context. External events push signals into a live session so Amara can react to things happening outside the terminal. Schedules and goals keep long-running work moving without manual prompting. Programmatic usage exposes the CLI as a headless engine for CI and scripts, and deep links let other apps hand off directly to a Syntic Code session.

Choosing an approach

Reach for hooks when you need deterministic behavior tied to a specific moment. Use programmatic mode (syntic --print) when another system owns the control flow and only wants an answer. Use schedules and goals when the work is ongoing and self-directed. Each page in this section documents the exact configuration, flags, and payload shapes so you can wire Syntic Code into your environment with confidence.