Inspect an element with Atom

Inspect an element with Atom

Atom is an optional browser-extension tool for examining an element in an existing application tab. StatePort’s Node setup, source help and saved-case workflow do not depend on it. Start with Install and connect for your agent task.

Choose the right job

Use Atom for a selected element’s layout, styles, properties and available source context. Use Capture to retain a reusable browser/API case. Inspecting an element does not save a Card or produce reproduction evidence.

These instructions apply when the Atom extension is installed in the browser. A source-linked workflow additionally needs its separately configured IDE helper and project dev plugin; a visible element does not prove that connection is ready.

Inspect explicitly

Choose the intended application tab and inspect the element you want to understand. Review the properties and source connection actually reported. After a local edit, explicitly inspect again; the previous observation is not an automatic verification of the change.

Capture and Atom cannot own the same tab at once. Finish or detach one workflow before switching. Do not grant access to unrelated tabs merely to inspect an element.

Source and limitations

Basic inspection and linked source have different prerequisites. If linked source is unavailable, say so rather than inventing a component/file reference. The StateAtom project maintains its own integration details.

For a same-case before/after check with StatePort, use your first task and inspect the actual browser or saved-run evidence.

Prepare a diagnostic for another developer

Use only a diagnostic operation offered by the installed integration. Review any local output before sending it. Do not send page text, form values, tokens, cookies, browser profiles or private project material merely to explain a missing source connection. See safe diagnostics.