Status Output Reference

agentsync status verifies every AgentSync-managed target and reports drift. It iterates all enabled agents and their targets from your agentsync.toml, validates each one according to its configured sync type, and reports the result.

Human output

Human-friendly output uses colors and statuses:

• ✔ OK — symlink exists and points to the expected source.
• ✗ Incorrect link — symlink exists but points somewhere else.
• ! Missing — destination does not exist.
• · Exists but not a symlink — a regular file or directory exists at the destination.

JSON schema (status --json)

Each entry reports additive machine-readable fields:

Field	Type	Meaning
destination	string	Path in the project where the managed target lives
sync_type	string	The configured sync mode for that target
destination_kind	string	Whether the destination currently resolves to a symlink, directory, file, or is missing
exists	boolean	Whether the destination path exists
is_symlink	boolean	Whether the destination itself is a symlink
points_to	string | null	The symlink target (if any)
expected_source	string | null	The resolved expected source path for single-link targets when the source exists
issues	array	Structured drift reasons
managed_children	array | null	Child-level detail for symlink-contents targets

Behavior per sync type

symlink

Checks the destination path itself as the managed symlink and compares it against the expected source.

symlink-contents

Checks the destination as a managed directory container plus the expected child symlinks inside it. A valid empty source such as .agents/commands/ with zero eligible files is still reported as OK; the destination is not treated as missing solely because it currently has 0 managed entries expected.

nested-glob

Emits a single target-level entry. The destination is the configured template (for example packages/{relative_path}/CLAUDE.md) and expected_source is the search root resolved from the project root. Individual expanded matches are not emitted as separate entries; run agentsync apply or inspect the filesystem to see per-match symlinks.

module-map

Emits one entry per mapping. Each entry’s destination is the mapping destination directory joined with the resolved output filename (see the Sync Types guide for filename resolution priority).

Exit codes

• 0 — no problems detected.
• 1 — one or more issues found (suitable to fail CI builds).

CI example

agentsync status --json > status.json

The status array is written to status.json; diagnostic events go to stderr. On Windows, status is also a practical post-setup verification step — see the Windows Symlink Setup guide.