Framework plugins

The framework plugins put AegisRunner inside your dev server. Add one line to your Vite, Nuxt or Next config, run your normal dev command, and an AI scan of your localhost app is one keypress away — no deploy, no staging URL, no second terminal.

They’re all built on the same primitive, so pick whichever fits your stack:

How it works

Every plugin does the same four things — they only differ in how they hook the dev server:

1. Learn the port your dev server bound to.
2. Open a tunnel — an outbound-only connection from your machine to AegisRunner’s cloud scanner (no inbound port opened), giving a temporary <id>.tunnel.aegisrunner.com URL pointed at your local port.
3. Scan on demand — press a (or set scanOn: ‘startup’) and it triggers a full crawl + test generation against that URL, streaming progress into your dev log.
4. Clean up — closes the tunnel when the dev server stops.

The tunnel client, scan trigger and live-progress stream are all reused from @aegisrunner/cli, so the AI generation stays in the cloud — only the tunnel client runs on your machine. See Testing behind a firewall for how the tunnel is secured.

Vite

Covers the whole Vite ecosystem — Vue, React, Svelte and more.

npm install -D @aegisrunner/vite

// vite.config.js
import { defineConfig } from 'vite'
import aegis from '@aegisrunner/vite'

export default defineConfig({
  plugins: [ aegis({ scanOn: 'manual' }) ],   // 'manual' (press a) | 'startup'
})

Nuxt

A Nuxt module, plus a native DevTools tab showing live tunnel + scan status and a one-click Scan now.

npm install -D @aegisrunner/nuxt

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@aegisrunner/nuxt'],
  aegis: { scanOn: 'manual' },
})

Next.js

Next has no dev-server plugin hook, so you wrap your config. It opens the tunnel to your dev port in the dev phase only (a pure pass-through in next build / production).

npm install -D @aegisrunner/next

// next.config.mjs
import withAegisRunner from '@aegisrunner/next'

const nextConfig = { /* your config */ }
export default withAegisRunner(nextConfig, { scanOn: 'manual' })

Any framework — aegis dev

The universal wrapper. It spawns your dev command, opens the tunnel, and gives you an interactive scan — no config change at all.

npm install -g @aegisrunner/cli
aegis dev --port 3000 -- npm run dev

While it runs: [a] scan · [o] open results · [q] quit.

Configure it

All plugins take the same options (and aegis dev the matching flags). Set your token in the environment:

export AEGIS_TOKEN=aegis_xxxxxxxx   # a project CI trigger token
npm run dev

Monorepos

Running several dev servers at once (e.g. turbo dev fanning out apps into one terminal)? Each app opens its own tunnel, and every log line is tagged with a label — by default the package name — so you can tell them apart:

[aegis·web]   tunnel open → https://ab12.tunnel.aegisrunner.com
[aegis·admin] tunnel open → https://cd34.tunnel.aegisrunner.com

Override it with the label option (or aegis dev —label).

Gate your pushes — aegis hooks

Want a scan (or your test suite) to run before code leaves your machine? Install an opt-in pre-push git hook that blocks git push on failure:

aegis hooks install     # gate = aegis run --wait  (uninstall: aegis hooks uninstall)

Nothing is installed until you run it, and an existing pre-push hook is backed up rather than clobbered.

Requirements

• A project CI trigger token — create one under Manage → CI/CD (Pro or Business plan).
• Node 18+. The plugins are dev-only and never run in a production build.

Related

• Test a localhost app — the overview.
• Testing behind a firewall — the tunnel, allowlist and self-hosted runner.
• CI/CD Integration — the same token, from your pipeline.