doctl harness-runtime port-forward
Generated on 6 Oct 2026
from doctl version
v1.178.0
Usage
doctl harness-runtime port-forward <session> [<local-port>:]<remote-port> [...] [flags]Description
Opens a local TCP tunnel to a port inside the session’s sandbox, kubectl-style: connect to localhost:<local-port> and traffic flows over an authenticated connection to the sandbox port. Nothing inside the sandbox is exposed publicly.
A paused session is resumed automatically before the tunnel opens, same as doctl harness-runtime launch. A bare port forwards the same port on both ends; 0:<remote-port> lets the OS pick a free local port (printed on the ready line). Remote ports must be between 1024 and 65535. The process runs in the foreground; press Ctrl-C to stop.
Example
doctl harness-runtime port-forward sess_abc123 3000 8080:8000Flags
| Option | Description |
|---|---|
--address |
Local bind address Default: 127.0.0.1 |
--help, -h |
Help for this command |
Related Commands
| Command | Description |
|---|---|
| doctl harness-runtime | Managed Agents Runtime Services (M.A.R.S) |
Global Flags
| Option | Description |
|---|---|
--access-token, -t |
API V2 access token |
--api-url, -u |
Override default API endpoint |
--config, -c |
Specify a custom config file Default: |
--context |
Specify a custom authentication context name |
--http-retry-max |
Set maximum number of retries for requests that fail with a 429 or 500-level error
Default: 5 |
--http-retry-wait-max |
Set the minimum number of seconds to wait before retrying a failed request
Default: 30 |
--http-retry-wait-min |
Set the maximum number of seconds to wait before retrying a failed request
Default: 1 |
--interactive |
Enable interactive behavior. Defaults to true if the terminal supports it (default false)
Default: false |
--output, -o |
Desired output format [text|json] Default: text |
--trace |
Show a log of network activity while performing a command Default: false |
--verbose, -v |
Enable verbose output Default: false |