Skip to main content
QLane runs where work happens. The agent doesn’t care where the request came from — you get the same kind of session, with the same kind of report, no matter how you kicked it off.

​
On every pull request

The default. With PR testing enabled, every PR opened or updated triggers a session against the configured environment. The result lands as a GitHub review. No setup beyond connecting the GitHub App and enabling PR testing on the project.

​
From GitHub

  • Mention @qlane on any issue or PR comment. Example: @qlane verify the signup flow on staging. The agent runs and replies with the result in-thread.
  • Assign QLane as a reviewer on a PR to trigger a fresh run.
  • Use the GitHub Action — uses: qlane/qa-action@v1 in your workflow to fire sessions from CI on any event.

​
From Linear

  • Mention @qlane on a Linear issue: @qlane reproduce ENG-247 on staging. The agent runs and threads its activity inline, like any other Linear agent session.
  • Assign the QLane bot to delegate via Linear’s Agent Sessions.
  • Findings come back as comments with severity and a deep link to the full run.
Set up under Settings → Integrations → Linear.

​
From Jira

  • Mention @qlane on a Jira ticket to trigger a session.
  • Assignment triggers a session — assign the QLane user to a ticket and the agent picks it up.
  • Findings post back as comments on the ticket with severity tags.
Set up under Settings → Integrations → Jira.

​
From Slack

  • Slash command: /qlane test staging in any channel where the bot is invited. The agent picks up the project bound to that channel and reports back in-thread with bugs, screenshots, and a dashboard link.
  • Mention @qlane in a thread to chat with the agent or kick off a one-off session.
Set up under Settings → Integrations → Slack.

​
From Claude Code

  • /qlane:test runs a QA pass against localhost from inside your editor — perfect for “I want to know if this works before I push.”
  • /qlane:fix PR 247 loads the bug, repro steps, and screenshot for a failing PR straight into your Claude Code session.
Install from the Claude Code marketplace; sign in once with your QLane account.

​
From the browser extension

See a bug while you’re using the app? Click the extension. The agent reproduces it cold, captures evidence, and files a structured report — with the path you took already mapped. Available for Chrome and Arc. Sign in once with your QLane account.

​
On a schedule

For URL environments, you can run a session on a cron-like cadence. Useful for:
  • Smoke-testing production every few hours.
  • Catching environment drift between releases.
  • Validating long-running flows that need real data accumulation.
Set the cadence on the environment under Triggers → Schedule.

​
Manually from the dashboard

Every environment has a Run now button. Pick a commit/branch/PR and the test cases to run, and the agent starts. Use this for ad-hoc validation when none of the integrations fit.

​
What all triggers have in common

  • One session per trigger. No matter the surface, you get one auditable session with its own dashboard URL.
  • The same agent. Browser, evidence, severity, repro steps — every trigger produces evidence-grade output.
  • The same credit cost. Whichever surface fires the run, the session costs the same against your plan.