Current functionality is provided through ArcRelay Suite. Standalone distribution is still being validated; no separate download is promised.
Automate: local automations
Automations follow a linear when → only if → do model without requiring a cloud service.
- Triggers: application foreground/start/exit events; lock, unlock, sleep and resume; scheduled times; device connection changes; completed file sends or receives; hotkeys or manual runs. Available choices depend on the platform.
- Conditions: time ranges, running applications and connected devices. Multiple conditions must all match.
- Steps: quick-action references, Shell, delays and notifications. Steps run in order and stop on failure.
- Control: automatic or ask-before-run mode, activity history, per-step outcomes and cancellation. Dangerous quick actions still require confirmation on an unlocked desktop.
For example, at a weekday time and while a selected device is connected, open your chosen applications and show a start-of-work notification. A completed file receipt can also trigger an explicitly configured follow-up.
Restarting does not silently replay interrupted runs or bypass pending confirmations. The frozen legacy ArcFlow system is not the entry point for new automation features.
Notifications and local tool integration
Notification settings independently cover pairing requests, file tasks, print failures, automation confirmations, input permissions and other events. Defaults notify only while the application is inactive and hide content previews. The notification center retains messages and read status rather than relying only on a transient OS alert.
The local MCP interface lets authorized tools send notifications and query messages and read status, so a local task can report completion or ask for attention. It listens only on the local machine and requires an access token. This is notification integration, not an unrestricted computer-control API exposed to the LAN.
Boundaries
Steps run in order and stop on failure. Dangerous actions retain local confirmation; interrupted runs are not replayed after restart, and triggers vary by platform.