Your guided expert for Anypoint Platform:
a keyless, branded panel that turns a plain-language Anypoint goal into a
guided, safe flow — using your IDE's own model.
What it does
- Branded panel. A PVA logo in the activity bar opens a "What can PVA do for
you?" welcome with a capability menu (Networking · Access Management ·
Lifecycle · Troubleshoot · Set up platform).
- Keyless guided preview (always on). Every request first renders a
deterministic card — route, the inputs PVA will ask for, pre-checks, warnings,
and which tool runs it. No model required.
- Full autopilot (when a model is available). If a
vscode.lm provider
(e.g. GitHub Copilot) is signed in, PVA plans the request, loads the matched
skill, and follows the guided flow (ask → validate → pre-check → dry-run →
confirm → execute), surfacing approvals for destructive/deploy actions.
PVA holds no LLM key — it uses your IDE's own model to do the reasoning.
Get started
- Install the extension.
- Click the PVA logo in the activity bar.
- Describe an Anypoint goal in plain language, or pick a capability from the
menu.
Settings
| Setting |
Default |
Description |
pva.corePath |
"" |
Absolute path to the pva-core package directory (auto-resolved when empty). |
pva.channel |
"" |
Skill registry channel (local:…, github:org/pva-registry). |
pva.model |
{ "vendor": "copilot" } |
Selector for vscode.lm.selectChatModels. |
pva.autoSyncRegistry |
true |
Sync the skill registry on engine start. |
pva.maxTurns |
20 |
Max autopilot turns before PVA pauses and offers to continue. |
pva.requestTimeoutMs |
30000 |
Timeout (ms) for a single engine request (0 disables). |
Commands
- PVA: Open Panel
- PVA: New Chat
- PVA: Sync Skill Registry
- PVA: Select Language Model
- PVA: Export Chat to Markdown
- PVA: Validate Anypoint Config
Publishing
PVA is published to two registries so it installs in both VS Code and forks
like Cursor (which install from Open VSX, not the MS Marketplace):
- VS Marketplace via
vsce
- Open VSX via
ovsx
Automated (recommended)
A tag-triggered GitHub Actions workflow (.github/workflows/release.yml)
runs the tests, packages the VSIX, and publishes to both registries:
# bump "version" in pva-vscode/package.json first, then:
git tag v1.1.12
git push origin v1.1.12
The workflow needs two repository secrets (each publish step is skipped if its
token is absent):
VSCE_PAT — an Azure DevOps Personal Access Token with Marketplace publish rights.OVSX_PAT — an Open VSX access token.
Manual fallback
cd apps/pva-vscode
npm run package # builds pva-vscode-<version>.vsix
npm run publish:vsce # VS Marketplace (uses VSCE_PAT)
npm run publish:ovsx # Open VSX (uses OVSX_PAT)
License
Apache-2.0 — see LICENSE.
