profile sends one GET from this machine and reports its timings. Name an absolute HTTP or HTTPS URL, or pass --instance to profile an Instance at the URL that the Gateway records for it. Gateway profiles are a separate local configuration.
The request always leaves this machine. The command never opens an SSH session and never asks the Gateway to send the request. With --instance, it asks the Gateway only for the URL.
Commands
The command accepts
--json.
orbit profile
Profile one GET to an absolute HTTP or HTTPS URL.url and --instance, the command reads APP_URL from the nearest .env in the working directory or a parent. It starts at ORBIT_HOST_CWD when that variable is set. An interactive terminal asks for a URL when no valid APP_URL exists. --json and --no-interaction fail instead.
The command sends one GET and does not follow redirects. It sends X-REQUEST-ID and X-TOOLBAR-AUTH (guest, first-user, or user), and X-TOOLBAR-USER with --user. TLS uses the system trust store. With --instance, TLS uses the active profile’s pinned Orbit root certificate instead, because an Instance domain presents an Orbit CA certificate. An --instance request also carries X-Orbit-Probe: 1. A development Instance’s site answers it without waking hibernated Processes and does not count it as activity.
A completed response is a success, whatever its HTTP status. When the response has a readable X-Toolbar-Summary header, the result has source baseline+toolbar, instrumented true, and the decoded summary. Otherwise source is baseline and instrumented is false.
Human output is one request line and a timing list. JSON returns the request, timings, response headers, auth mode, request ID, origin caller, source, and instrumented flag.