Overview
When running in cloud mode, OpenSteer creates remote browser sessions that you can monitor and control. Each session has a unique ID and optional viewing URL.Methods
getCloudSessionId()
null if not in cloud mode or session not started.
Session ID string (e.g.,
'sess_abc123...') or null if:- Cloud mode is not enabled
launch()has not been called yet- Session has been closed
getCloudSessionUrl()
null if not available.
Session URL string (e.g.,
'https://app.opensteer.com/session/sess_abc123') or null if:- Cloud mode is not enabled
launch()has not been called yet- Session has been closed
- Server did not provide a viewing URL
Session Lifecycle
1. Before Launch
Before callinglaunch(), both methods return null:
2. After Launch
Afterlaunch(), session details are available:
3. During Execution
Session remains active while performing actions:4. After Close
After closing, session details are cleared:Examples
Basic Session Info
Logging Session Details
Conditional Cloud Mode
Session URL in Test Reports
Sharing Session Links
Session Monitoring
Session Announcement
By default, OpenSteer announces session details to stderr on launch:announce option:
Notes
- Session IDs are unique per launch
- Session URLs may not be available depending on cloud configuration
- Both methods return
nullin local (non-cloud) mode - Session details are cleared immediately after
close() - You can safely call these methods before
launch()- they returnnull - Session URLs allow team members to observe automation in real-time
- Sessions are automatically closed and cleaned up when the connection ends