Start projects from your repositories
Browse GitHub or GitLab repositories and prepare a remote project. Connect a Git identity and check the workspace’s Network settings for custom GitLab hosts. Account authorization and installed credentials stay separate from network reachability.
Account verification and installed credentials do not establish a workspace route. The restricted gateway reaches approved public hosts on ports 80/443. Private addresses and other ports are unavailable through this gateway.
How it works
Choose your Git provider
Select GitHub, GitLab or both during setup or in Git Accounts. The controller API supports custom HTTPS hosts and ports, with exact administrator authorization for private destinations. This selection does not create a workspace network route.
Connect the account deliberately
Import a supported local profile or connect an account in the console. GitLab PATs can be imported; copying a short-lived OAuth token does not transfer its refresh state.
Resolve Git access before launch
Reuse a saved account choice or automatically select the only eligible account. Choose explicitly when several match. The launch check verifies identity and credential revisions; workspace reachability requires its own policy and route.
Check the custom server’s network path
For a public custom GitLab host on port 443, allow its hostname in Project Network settings. The restricted workspace gateway supports only public ports 80/443. Private destinations and other ports, such as 8443, remain unavailable through that gateway.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Watch the workflow
Loading the recorded terminal…
Release videos
- devctrl 0.19.0: Delete an empty project group chapter at 0:00 on YouTube
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.