Docs/Workflows

Screenshots, inspection, and logs

Capture scopes, image formats, DOM inspection, and console attachments.

Artifacts can attach page images, element details, and selected console messages to a chat draft. Review the attachments and send the message from the composer.

Inspect an element#

Open a page in Artifacts, then choose Inspect. Select an element to view its name/reference, selector, dimensions, and selected computed styles. Picking suppresses the element's normal click action. Escape cancels the picker.
Navigation invalidates the selection. Hiding the viewport or changing threads can also cancel inspection.
Selected-element controls in Artifacts.
Selected-element controls in Artifacts.

Capture scopes#

ScopeCaptured area
Visible areaThe current browser viewport.
Whole pageThe page beyond the current viewport.
Selected elementThe inspected element's bounds.
Open Screenshot to choose scope and format. JPEG supports a quality setting from 0–100; PNG is lossless. Format and quality preferences are retained.
Whole-page capture temporarily expands the virtual viewport, which can affect viewport-dependent layout. Oversized or empty regions may be refused. For an element larger than the viewport, zoom out or capture the whole page.
Screenshot scope, format, and quality controls.
Screenshot scope, format, and quality controls.
These actions capture the project page, not the pi-kit application window. Use an operating-system screenshot to report an issue in the desktop shell itself.

Attach an image or element details#

The selected-element panel has two separate actions:
  • Screenshot: attach an image of the selected region.
  • DOM node: add inspection details as text.
Use both if the request involves appearance and element properties. Capturing an image alone does not add the DOM properties.
Attachments are added to the unsent draft. If navigation or a thread switch makes the result stale, the operation is canceled. Repeat the capture in the intended thread and document.
A selected-element screenshot in the composer attachment queue.
A selected-element screenshot in the composer attachment queue.

Describe the change#

Include the affected element, expected behavior, and a reproduction condition. For example:
The Save label is clipped at this viewport width. Update the button layout without shortening the label, then check the form at narrow and wide widths.
For a layout issue, a viewport image provides surrounding context; an element capture provides more detail. Review screenshots for credentials or private content before sending.

Console messages#

  1. Open Console.
  2. Reproduce the interaction.
  3. Filter by level if needed.
  4. Select entries and choose Attach selected logs.
Entries include message level, time, and source when available. Runtime exceptions are collected as well as console calls. Clear console resets the buffer; navigation resets document context. The buffer is bounded and is not a persistent application log.
Console pane with an example page message.
Console pane with an example page message.

Check a result#

After an edit, repeat the relevant interaction, inspect the console, and capture the resulting page. An accessibility snapshot reports controls and text; a screenshot is needed to inspect rendered layout.
A failed or blank capture is a capture error, not evidence that the page itself is blank. Report the failure and retry with a smaller scope or the current document context.