Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.niteshift.dev/llms.txt

Use this file to discover all available pages before exploring further.

Every Niteshift environment runs a persistent Chromium browser. The agent uses it to verify changes, drive your app, and capture visual artifacts that get posted back to the PR.

​
When the agent uses the browser

The agent uses the browser automatically when you ask it to “use the browser”, “verify the change works”, “open the dashboard and check the new chart”, or “reproduce issue #421”. Explicitly, with a slash command: /browser If you’d like to encourage your agents to use the browser more often, or to consistently take screenshots, we recommend adding that to your repository instructions on the settings page. An example custom instruction to encourage maximum browser usage: 
If a change is testable via a browser (e.g. a UI change to web app) you must use /browser /screenshots and /demo

​
Browser skills

Niteshift exposes a few built-in skills that teach the agent how to use the browser.

​
/browser

The agent will use browser automation to visually verify UI changes, navigate through the relevant flow, and confirm the result works as expected.

​
/screenshots

The agent will take screenshots of its changes and add them to your PR description.

​
/demo

The agent will record a demo walkthrough of its changes and add them to your PR description.

​
/browser-profiler

The agent will use the Chrome profiler to measure your app’s performance.