Core, Editor and Tray
Understand what executes your automations and what closing a window does.
AlphaCore owns the active project, service connections, plugins and automation execution. The Editor is a client that presents and changes that state; Tray provides access to Core without an Editor.
Everyday use
| Action | Result |
|---|---|
| Close the Editor | Core and applied automations keep running. Resolve the Editor's pending changes when prompted. |
| Reopen the Editor | Connect to the existing Core and read its current state. |
| Close Editor and Core | Request a coordinated shutdown, with save, discard and cancel choices when needed. |
| Exit from Tray | Shut down Core after the selected save policy. |
| Pause execution | Keep Core available while controlling automation execution. |
One Core owns the runtime for a Windows user, including when an isolated data directory is used. Several approved native clients may connect to that Core; they do not each run their own copy of the project.
Versions and access
Core and the main Editor have separate versions. Tray follows Core, and plugins retain their own version lines. Compatibility is checked through the relevant API contracts; identical version numbers are not required for every component.
A new client requests access through pairing. Review its requested permissions in Tray. See Client connection and access.
Editor without Core
The Editor can open with automatic Core startup disabled or in its editor-only mode. Appearance, language, hotkeys and layout remain available. Opening and saving project files for offline editing is not supported in that mode.
Use Core Settings for Core status, clients, saved-service reconnection, updates and diagnostics.
Closing with unsaved changes
Save project applies pending supported edits and writes the file. Keep in Core leaves the applied project running, with Core autosave still active.