Projects
Turn local folders into Orbit projects.
Add a folder, let Orbit analyze it, then run and inspect the project from the same workspace.
Dashboard
Scan running state before opening a project.
The dashboard lists every project with status, framework, package manager, branch state, domain, and row actions for browser, logs, metrics, start, and stop.
- Use All Projects for the full list.
- Use Running when you only need active projects.
- Double-click a row to open the project detail view.
- Use row actions for browser, logs, metrics, start, and stop without opening the detail view.
Use the table when you need a workspace-level decision: which app is running, which command owns it, and which action can be taken from the row.
Add project
Point Orbit at the project folder.
The add dialog analyzes the path, detects framework, package manager, dev command, and suggested domain, then warns when the layout is ambiguous or dependencies are missing.
- Open Add Project from the toolbar.
- Browse for the folder or paste the path.
- Review the detected framework, manager, command, and domain.
- Let Orbit install missing dependencies when the project needs them.
Review the detected framework, manager, command, and local domain before saving. A wrong value here becomes the runtime contract for the project.
Project detail
The selected project owns its runtime context.
Project detail shows the project domain, HTTPS state, framework, package manager, detected port, uptime, runtime actions, and the tabs that hold the rest of the workflow.
- Start, stop, or restart from the action row.
- Open the domain from the title area to use the proxied project URL.
- Use Details for resolved metadata and the project path.
- Use Env and Terminal when the fix belongs inside the project folder.
Start here when a single app needs attention. The header shows domain, HTTPS state, status, detected port, and direct actions.
Environment
Edit variables beside the runtime that reads them.
The Env tab keeps project-specific configuration attached to the selected app, so local values can be reviewed without switching to another tool.
- Open the project detail view.
- Switch to Env when the fix is configuration.
- Edit the value and save before restarting the project.
Use Env when the fix is configuration, not code. Orbit keeps project variables editable beside the runtime that reads them.
Terminal
Run commands from the project root.
The Terminal tab opens in the selected folder, keeping package manager, framework, and database commands aligned with the project Orbit detected.
- Open Terminal when a fix needs a local command.
- Run package manager or framework commands from the detected root.
- Return to Logs or Requests to confirm the result.
Use Terminal when the next step is a package manager, framework, or database command inside the project folder.