Explore Products

Owlvex Beta for VS Code

Scan and fix code issues before you commit.

Owlvex runs inside VS Code so developers can scan changed code, review evidence, preview fixes, and verify results before changes leave their machine.

Catch security, quality, and behaviour changes while the code is still fresh.

Install Owlvex Choose a Plan
Scan changed files, selected files, or workspace
Preview fixes before applying code
Use maps and project checks when configured
Beta software improving with user feedback
Install

Start from VS Code.

Install Owlvex from the VS Code Marketplace, or use the public GitHub download page if you need the packaged extension file.

Marketplace

Open the Visual Studio Marketplace listing and install Owlvex into VS Code.

Open Marketplace

Search in VS Code

Open Extensions in VS Code, search for Owlvex, then choose Install.

See Workflow

GitHub download

Use the public GitHub page for release notes, manual download, and installation guidance.

Open GitHub
What Owlvex Helps With

A practical review loop before code is committed.

Owlvex is built for the moment when a developer still understands the change and can fix it quickly.

Code issues

Review risky patterns, unsafe flows, and implementation issues before they become review churn.

Security findings

Surface security-relevant issues with evidence, context, and clear remediation direction.

Maps

Use design, TDD, and code maps to help Owlvex understand expected behaviour and important boundaries.

Project checks

Run your own checks when configured and include pass/fail results in reports.

Workflow

Scan. Review. Preview. Verify.

1

Scan changed code

Run Owlvex on changed files, selected files, open editors, or the workspace.

Focus review on the code the developer is actually moving toward commit.

2

Review evidence

See what is wrong, why it matters, and which evidence supports the result.

Developers should know whether they are looking at a confirmed issue, guidance, or something that needs review.

3

Preview fixes

Open the proposed diff before any source file is changed.

The developer keeps control of what is accepted, rejected, or regenerated.

4

Verify again

After a fix is kept, Owlvex checks the changed file again and reports what remains.

The goal is not a patch. The goal is a clean, understood result before commit.

Plans

Start in the extension. Upgrade online when you are ready.

Free and Trial are no-card paths started from the VS Code extension. Developer is the self-serve paid licence for daily use.

Free

Starter access for validating the local workflow and confirming Owlvex fits your development process.

  • Register from the VS Code extension
  • No card required
  • Upgrade when the workflow proves useful
Start in VS Code
Trial
7 days

Evaluation access for teams testing scan quality, reports, fix preview, and evidence-backed workflows.

  • Full beta evaluation workflow
  • No card required
  • Event codes can be reviewed by support
Start Trial in VS Code
Self-serve
Developer
GBP 19.99 / month

Individual paid licence for daily scan, report, maps, project checks, and fix-preview workflows.

  • One user licence
  • Secure hosted checkout
  • Licence code sent by email after purchase
Buy Developer Licence

Card details are handled by the secure checkout provider. CooperBox activates paid access only after a verified payment event, then emails the licence code to the purchase email.

Activation

From purchase to active VS Code licence.

1. Buy Developer

Use the Developer button to complete secure checkout. Free and Trial remain no-card flows inside the extension.

2. Receive licence

Owlvex emails your Developer licence code after payment is verified. A redirect alone does not activate access.

3. Activate in VS Code

Enter or refresh the licence in the Owlvex extension, then continue scanning and fixing before commit.

Data Boundary

Owlvex is local-first by design.

Local deterministic scanning

The deterministic scanner runs in your environment. Owlvex backend services handle licence and product metadata, not source-code analysis.

Your AI provider

If AI assistance is enabled, code goes directly to your selected model provider or local model endpoint, not through Owlvex as a relay.

Your project checks

Project checks are configured by the user and report pass/fail outcomes. They do not block scans by themselves.

Common Questions

Simple setup, clear boundaries.

Do Free and Trial need a card?

No. Start Free or Trial inside the VS Code extension. Use Developer when you are ready for paid daily use.

How do I install it?

Open VS Code Extensions and search for Owlvex, or use the Marketplace and GitHub links on this page.

How does paid activation work?

After verified payment, CooperBox emails a licence code to the purchase email. Enter it in the extension.

Where does my code go?

Local scanning runs in your environment. AI review goes to your selected model provider or local endpoint.

Beta Status

Built for feedback. Useful today, still improving.

Owlvex is beta software. We are improving scan quality, report clarity, fix previews, and workflow fit with real developer feedback.

Install Owlvex Choose a Plan Contact Support