Answers to the questions that come up most often. For the JSON rule format see RULE_AUTHORING.md, for complete rules see EXAMPLES.md, and for internals see ARCHITECTURE.md.
- Setup (
Synector-Setup-<version>-Windows-x64.exe) installs intoProgram Files, adds a Start Menu shortcut, registersApp Pathsand an uninstaller. Updates are applied by downloading and running the new setup silently. - Portable (
Synector-v<version>-Windows-x64.zip) containsSynector.exeplus the license and attribution files. Extract it anywhere and run the executable; updates replace it in place.
Both forms share the same configuration in %LOCALAPPDATA%\Synector\ and the same daemon.
Synector is distributed through GitHub Releases. Verify the file before running it:
Get-FileHash .\Synector-Setup-<version>-Windows-x64.exe -Algorithm SHA256Compare the result with the matching line in SHA256SUMS.txt from the same release. If the hashes
match and you downloaded from the official release page, the warning is a reputation prompt rather
than a sign of tampering. Do not disable antivirus protection or add exclusions for files whose
hash you have not verified.
Synector starts elevated by default; --no-elevate opts out. Elevation enables:
- kernel ETW process tracing (otherwise Synector falls back to adaptive Toolhelp32 polling);
- input simulation into elevated applications (UIPI bypass);
- memory/priority/affinity tuning of elevated processes;
- silent highest-privilege logon autostart through Task Scheduler.
Without elevation most rules still work, but a rule that targets an elevated game or application, or that relies on ETW, may not fire.
The daemon registers a Task Scheduler autostart entry on first launch. It can be disabled in
Settings. The entry is separate from the installer: uninstalling removes it. First launch always
creates %LOCALAPPDATA%\Synector\ with the configuration files and logs.
The daemon checks GitHub Releases, selects the right asset, downloads it and verifies the SHA-256 digest published by the GitHub API. An installed copy downloads the release's setup and starts it silently; a portable copy replaces its own executable. Progress is shown in the tray and overlay notifications. Auto-install is optional and can be turned off in Settings.
If an update fails, check the log in %LOCALAPPDATA%\Synector\logs\, make sure the app is not
running from a read-only or protected folder, and install the latest release manually. The
configuration directory is preserved either way.
Install the older release over the current one. Configuration is versioned per section and
downgrades are not a supported migration path: a 2.8 build cannot read the 2.9 files. Before
changing versions, keep a copy of %LOCALAPPDATA%\Synector\ and an export of your rules
(--rules-export rules.json), so the rules can be restored or re-entered.
The 2.9 storage format is split into independent section files and older configuration is not
migrated automatically. A 2.8 installation has no --rules-export flag and its PH1: share codes
are rejected by 2.9, so rules have to be re-created in the new version: keep the old app installed
alongside while you copy rule settings across. SYN1: share codes exist only in 2.9 and later.
No. The daemon is the tier that owns rules and triggers; the GUI is only a client. Closing the GUI, or never opening it, leaves automation running. Use the tray menu to pause, open the window or exit the daemon.
- Configuration:
%LOCALAPPDATA%\Synector\(settings.json,rules.json,library.json,runtime.json). SetSYNECTOR_CONFIG_DIRto relocate the whole directory. - Logs:
%LOCALAPPDATA%\Synector\logs\, one file per day, 7-day retention and an 8 MiB cap per file.
The log level comes from SYNECTOR_LOG (off, error, warn, info, debug, trace; default
info). Restart Synector after changing it.
Stop Synector first, then copy the whole %LOCALAPPDATA%\Synector\ directory. For rules alone,
Synector.exe --rules-export rules.json or a SYN1: share code is enough. While the daemon is
running it is the only writer; editing the files underneath it is not supported.
A section that fails to parse is renamed to <name>.corrupt-<timestamp> before defaults replace
it, so the original is not destroyed. To start clean, stop Synector and remove or rename the
section files; to recover, restore a backup over them while the daemon is stopped.
The tray daemon and the GUI are separate tiers of the same executable. Overlay windows are additional borderless processes supervised by the daemon. Seeing several Synector processes is normal when overlays are open. Each tier has a single-instance mutex, so a second daemon or GUI does not start.
Overlays are edited in the Overlay Studio: select an Overlay action in the rule inspector and press OPEN →. The studio arranges elements on a multi-monitor artboard; POSITION ON SCREEN switches the overlay into calibration, which makes it draggable so it can be placed on the intended display. The daemon then renders it in a separate process, so the overlay stays on screen when the GUI is closed.
The action decides what happens at runtime: toggle visibility or flash on screen, optional override
text (tokens such as {ProcessName} are allowed), duration and fade, and "close when process exits"
to bind the overlay to the triggering application. Saved definitions live in library.json.
Record it in Macro Studio: select a Macro action in the inspector and press OPEN →, then F9
starts and stops recording — the low-level hooks are active only while recording. F10 test-runs
the sequence on a background thread, Esc closes the studio. The action then decides playback:
operation Run, Stop or Toggle, repeat count, and an optional preset stored in library.json.
Playback uses hardware scan codes with short holds and humanized timing, so it also registers in
DirectInput games.
Check, in order:
- The rule is enabled and has not hit a lifetime quota.
- The trigger target actually matches (process name, window, folder, hotkey, webhook path).
- Preconditions are satisfied. A false condition prevents the pipeline from starting.
cooldown_secondsor a periodic quota is not skipping the run.--rules-listshows the counter and period.- The rule is not stuck in an active execution, and
stop_on_errordid not halt it after a failed step. - The daemon logs in
%LOCALAPPDATA%\Synector\logs\do not show a permission or target-not-found error.
Process detection uses ETW when elevated and adaptive Toolhelp32 polling otherwise; both feed the same trigger surface, so a missing ETW session alone does not disable process rules.
- Cooldown is a minimum delay between two triggered runs.
- Lifetime quota (
max_executionswithoutquota_period) pauses the rule after the limit.--rules-resetclears the counter and re-enables it. - Periodic quota (
quota_period) keeps the rule enabled and skips executions until the period rolls over.
See RULE_AUTHORING.md#quotas for reset semantics and JSON fields.
An infinite macro has no natural end. The CLI validator only accepts it with a global-hotkey trigger, because every other trigger offers no manual cancellation path. The Rule Builder warns and dims the steps after the infinite action.
Use a webhook trigger and send a request to
http://127.0.0.1:48123/api/v1/trigger/<endpoint_path> (a rule id also works). The server is
local-only. See RULE_AUTHORING.md#webhook-trigger for the
request and response contract, RULE_AUTHORING.md for the JSON format and
EXAMPLES.md for a complete rule.
Global hotkeys are detected by polling GetAsyncKeyState, not by RegisterHotKey, which is what
allows mouse-button combinations and hold/repeat modes. Another application listening for the same
combination will also react, and a target that ignores synthetic input will still not respond. If a
combination does nothing, try another one and check the logs. Hold mode repeats the pipeline while
the key is held; repeat-while-held without hold mode loops until the hotkey is pressed again.
SYN1: codes carry a checksum and are decoded with bounds on code length, decompressed size and
rule count. Imported rules are created disabled by default; review them before enabling. A share
code can contain scripts, webhook actions and other powerful steps, so only import codes from people
you trust. See ARCHITECTURE.md#sharing-and-backup.
Release builds use the Windows GUI subsystem, so PowerShell neither waits for them nor captures their
output or exit code. Prefix commands with cmd /c:
cmd /c "Synector.exe --rules-validate rule.json"The full explanation, including how other tools that spawn and wait for the process behave, is in RULE_AUTHORING.md#console-notes.
Another Synector instance may hold the single-instance mutex; check Task Manager for an existing daemon or GUI. Look for an update-file cleanup failure or a permission error in the log. Starting from a folder that requires higher privileges than the process has can also prevent self-update or overlay processes from starting.
Open the Overlay Studio and start calibration: the overlay becomes draggable and can be moved to
the intended monitor. Check multi-monitor placement and DPI scaling in the overlay definition. The
daemon must be running for overlays to exist. WDA_EXCLUDEFROMCAPTURE keeps an overlay out of
screen capture; it does not hide it on screen.
Synector replays hardware scan codes and holds presses for at least 30–35 ms, which covers most DirectInput games, but some titles and anti-cheat systems ignore or flag synthetic input. Run Synector elevated if the game is elevated (UIPI otherwise blocks input). Relative camera turns use Raw Input-compatible deltas and should be recorded in the same coordinate mode the game expects. Use automation only where the application permits it.
Check that the requested default device exists and is enabled, and that the target process is playing audio. Per-application volume and channel balance depend on the Windows audio session for that process; a stopped or suspended app may not expose one. Audio format changes can temporarily interrupt playback by design.
Polling is adaptive and backs off when no rule uses a trigger, but many independent polling
triggers, a fast interval schedule or trace logging increase load. Process triggers use ETW when
elevated; without elevation they fall back to snapshot polling. Runtime counters and overlay
positions are written coalesced, not on every event.
The local webhook server binds 127.0.0.1:48123, and the port is fixed. If another application
already owns it, the server cannot start and webhook-triggered rules will not fire; the daemon log
records the bind error. Close the conflicting application.
- Bugs and feature requests: GitHub Issues.
Include the Synector version,
winver, whether the app was elevated, reproduction steps and the relevant log lines with secrets removed. - Security problems: follow SECURITY.md and report privately. Do not open a public issue.