Forge Connections

Terminal keeps a list of public Forge API endpoints. Open Settings and choose Add Connection.

Enter the API base URL

Use a browser-reachable Forge origin without an API suffix:

https://forge.example.com

Terminal normalizes the URL to its origin. Binary Connect RPC paths and the canonical realtime path are derived from that origin. The URL must work from both the user’s browser and the Terminal server process.

Test the connection

The connection editor calls aurum.forge.v1.ForgeService/GetHealth with a binary Protobuf payload. A successful response confirms the API process is reachable; GetDoctor also checks upstream control-plane availability.

Select a server

The active server controls all Terminal loaders, browser requests, direct links, and WebSocket connections. Project IDs and resource keys are scoped to that selected Forge environment.

Terminal requires at least one configured server. Removing a connection does not delete projects or data from Forge.

Remote access

Do not register localhost unless the browser and Terminal process can both reach the intended Forge on their own localhost. For a remote Forge, configure its explicit public hostname and TLS route.

The SSH target used by aurum push is separate; see Remote Targets.