PRODUCT GUIDE / PRODUKTLEITFADEN
DevTools Bridge
DevTools Bridge connects the supported desktop or editor workflow to a selected browser debugging surface. Use it when a coding task needs to inspect a real page, its behavior or runtime diagnostics. Keep the target and device permissions explicit.
Your first workflow
- 01
Install the current supported development package.
- 02
Follow the bridge setup and choose a browser target.
- 03
Inspect the page through the offered tools.
- 04
Close or disconnect the target when the task is finished.
Available working areas
Browser target selection
Connect to the supported browser or page target offered by your installed tools.
Runtime inspection
Use available page, console and runtime observations to understand a real implementation.
Local tool connection
Set up the required companion or extension through the official instructions.
Deliberate access
Review which page and local capabilities are exposed to the connected development task.
Check the actual result
Observed page state and supported browser diagnostics for a development task.
Review the output against your task before sharing, publishing or relying on it. Retain the project files or records needed to continue.
Access and product scope
Requires compatible installed tools and an explicitly connected target. Follow the current official setup guide.
A bridge is access to a selected development target, not unrestricted access to all browser sessions or another user’s device.
If the next step does not work
I reach sign-in or access is denied.
Sign in with the intended Vigthoria account and reopen this product. Check the selected project, owner or team role and the current product entitlement in User Hub.
The task is queued or a required feature is unavailable.
Inspect the actual job and service state. Check whether the chosen route needs a provider connection, device support, signing setup or an enabled account feature. Keep a saved copy before retrying a completed action.
I need product support.
Include the product, action, time, visible error and relevant job or project identifier. Use a minimal example and keep passwords, secret keys and confidential source material out of the public form.