Core and client connection
Resolve missing Core, pairing, permission and compatibility problems.
AlphaCheck the Editor-to-Core connection separately from integration health. An offline Twitch or OBS connection does not mean the Editor has lost Core.
Core is unavailable
Check the Core tray and the Editor's automatic Core startup preference. Use File → Run Core to start or reuse Core when needed. A second Core cannot be used to bypass the Windows-user runtime owner.
If a remembered project is missing or invalid, Core can remain available without a project. Open a valid project through the Editor; do not assume the whole runtime failed.
Access is pending or denied
Review the request in the Core tray. Grant only the client's intended permissions. A discovery file identifies where Core is listening; it is not a credential.
The request lists the client's claimed name and publisher alongside its requested scopes. Review these before deciding whether to approve the client.
A client with an expired or revoked credential needs valid access again. New features can require additional scopes; refreshing a session never silently expands the existing grant.
One session disconnected
Disconnecting a session is temporary if the credential remains approved. Revoking the credential removes its authority and associated sessions. Use Core Settings → Clients and access to choose the intended action.
The upper table lists approved clients; the lower table lists active sessions. This example contains only the documentation Editor. Client and session IDs identify different records; neither is an access secret.
Versions or state changed
Use compatible Core/Editor packages. After Core restarts or a project switches, clients must obtain fresh state. Keep drafts for review rather than sending a stale change to a different project.
Include Core and Editor versions and the safe error code in a bug report. Never attach access secrets or discovery/credential files.