Pluro Accessibility Copilot

Current release candidate: 1.4.0 (2026-09-02).

Pluro Accessibility Copilot is a VS Code extension for finding, understanding and addressing accessibility issues while developers work. It combines local scanning and diagnostics with a read-only view of findings supplied by MyPluro.

One MyPluro connection

The extension has one public connection flow:

1. Generate a MyPluro IDE Extension Key in MyPluro.
2. In VS Code, open Pluro Findings and choose Connect to MyPluro.
3. Paste the key into the masked prompt. It is stored in VS Code Secret Storage.
4. Choose one of the domains returned by MyPluro.
5. Confirm the active-domain indicator and refresh the findings.

The production API base is https://my.pluro.ai/dashboard/api. The extension validates the key, requests the domains authorized for it, and reads findings only for the selected domain. There is no second public credential or device-identification step.

An authenticated key alone does not authorize an arbitrary site. The server-returned domain list is authoritative. Supported local PRO actions are available only for the selected authorized domain.

An authorized domain unlocks PRO generally. Only AI Smart Fix PRO and Explain with AI PRO additionally require a language model available through VS Code and the provider's user consent and quota. GitHub Copilot is not required: any model exposed through vscode.lm, including a provider extension or a BYOK model configured in VS Code, can be used. If no model is available, run Chat: Manage Language Models, configure one, and retry. Deterministic Quick Fixes and manual remediation guidance remain available. Pluro never requests or stores model-provider API keys.

Available functionality

• Local accessibility scanning and VS Code diagnostics
• Issue navigation and local remediation guidance
• Read-only MyPluro findings grouped as All, WCAG, BITV, Behavior and Custom
• Persistent active-domain indication, domain switching, refresh and disconnect
• Optional suggested mapping from a remote finding to local source code
• Local finding workflow state without writing status back to MyPluro

Remote findings remain visible even when they cannot be mapped to a local file.

Not included in this release candidate

The UI does not advertise unsupported cloud workflows. Version 1.4.0 does not provide cloud Monitor writes or synchronization, Chrome operations beyond displaying imported Behavior findings, organization custom-rule retrieval, hosted AI, team/history/SLA workflows, uploads, or remote status write-back.

Advanced scanner diagnostics, health checks, performance inspection and test tools remain available in the Command Palette for maintainers. They are advanced tools rather than part of the everyday scan-and-review workflow.

Authorization and failure behavior

• 401 or 403: disconnect immediately, clear the stored IDE key and connection state, clear protected cached findings and mappings, and require reconnection.
• Revoked key: handled identically to 401/403, including after VS Code restarts.
• Selected domain removed or no longer returned: clear that selection and its protected cache, keep a still-valid key, and require selection of another server-authorized domain.
• Network error, 429, or 5xx: never broaden access; a reduced redacted cache may be shown explicitly as stale/offline.
• Disconnect: clear the IDE key, selected-domain state and IDE findings cache.

Security and privacy

Never paste credentials into chat, tickets, logs, screenshots or documentation. Support needs only extension/VS Code versions, operating system, timestamp, the affected screen or command, redacted error text and reproduction steps.

The extension uses GET-only MyPluro IDE endpoints for this integration. It does not send local source files through the findings API and does not write finding status back to MyPluro.

When the user explicitly invokes an AI action, the relevant source snippet and issue description are sent by VS Code to the language model selected or configured in VS Code. Provider consent, processing and quota are controlled by VS Code and that provider, not by Pluro.

Release status

The implementation and automated contract tests target 1.4.0. Publication remains blocked until a clean-profile, live production test succeeds against https://my.pluro.ai/dashboard/api, including authentication, domain selection, all origins, WCAG criteria, pagination, revocation, restart, disconnect, mapping, quick-fix execution, keyboard and screen-reader access, and offline behavior.

Marketplace: Pluro Accessibility Copilot