Plex Agent for VS Code

Run Plex Agent — a standalone, local coding agent — directly inside VS Code. The extension launches the bundled Plex Agent server on a loopback port and opens the agent's React UI in a dedicated editor panel bound to your current workspace folder.

Features

Local coding assistant — plan, execute, and review file edits through the agent timeline.
Workspace-bound — the agent operates on the workspace folder you have open.
Live context — the panel follows the active file, language, and color theme.
Self-contained — ships with a pre-built agent server + UI bundle; no repository clone or build step required.
Zero configuration — works out of the box on http://127.0.0.1:3001.

Requirements

VS Code ^1.85.0 or newer.
No Node.js installation needed — the agent runtime is bundled inside the extension.

Getting started

Install the extension (from the Marketplace or a .vsix).
Open a workspace folder.
Run Plex Agent: Open Local Agent from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).

The agent panel opens beside your editor and attaches to the open workspace.

Configuration

Setting	Default	Description
`plexAgent.port`	`3001`	Loopback port used by the local Plex Agent server.
`plexAgent.serverRoot`	(bundled runtime)	Optional path to a locally built Plex Agent repository. When set, the extension launches that build instead of the bundled runtime.

Development

From the repository root:

pnpm install
pnpm package:vscode          # builds the UI + server bundle and produces the VSIX
code --install-extension dist-vscode/plex-agent-vscode-0.1.0.vsix

Layout inside packages/agent-vscode (after pnpm package:vscode):

packages/agent-vscode/
├── extension.js                  # extension host code (spawns server + renders webview)
├── package.json                  # extension manifest
├── packages/                     # bundled runtime (generated, gitignored)
│   ├── agent-server/dist/index.cjs   # esbuild bundle (all dependencies inlined)
│   └── agent-ui/dist/                # Vite build of the agent UI
└── .vscodeignore                 # what vsce excludes from the VSIX

Set plexAgent.serverRoot to the repository root during development to launch a live pnpm build output instead of the bundled runtime.

Publishing to the Marketplace

The publisher id plex-agent must be registered on the Visual Studio Marketplace. Create a Personal Access Token with the Marketplace → Manage scope.

Manually — one command

A dedicated script takes the publisher id and PAT as input, repackages (and updates the manifest publisher if it differs), validates, and uploads:

node scripts/publish-vscode.mjs --publisher <id> --pat <PAT> --publish
# optional: --ovsx <PAT> to also publish to Open VSX

Without --publish it runs a safe dry run (rebuilds + validates + prints the exact command). Environment fallbacks: PLEX_VSC_PUBLISHER, PLEX_VSC_PAT / VSCE_PAT, OVSX_PAT. The PAT is never echoed or persisted.

Manually — raw vsce

pnpm package:vscode
node_modules/.bin/vsce login plex-agent
node_modules/.bin/vsce publish --packagePath dist-vscode/plex-agent-vscode-<version>.vsix

Via GitHub Actions

Tag a release with vscode-v* (e.g. vscode-v0.1.0) and add repository secrets:

VSCE_PAT — Marketplace token (required).
OVSX_PAT — Open VSX token (optional; also publishes to open-vsx.org).

Bump version in packages/agent-vscode/package.json for every release — the Marketplace rejects duplicate versions.

License

MIT