ConnexCS Connect
ConnexCS Connect brings your ConnexCS platform resources directly into VS Code. Browse, edit, and manage ScriptForge scripts, Templates, Query Builders, Button Builders, Domains, Environment Variables, Key-Value Stores, and more from your editor.
Features
- Virtual Filesystem (
connexcs://) — browse project files in the ConnexCS tree on desktop and the managed Explorer in the browser IDE
- ScriptForge Editor — edit
.js scripts with Run, Run with Vars, live console output, and endpoint URL copy
- Template Editor — edit
.html templates with live preview
- Form Renderers — visual editors for Button Builder, Domain, Environment Variables, and Key-Value Store configs
- Project Switching — switch between ConnexCS projects from the command palette
- Desktop Agent Tools — let Claude Code, Codex, and VS Code agents manage remote project files through MCP
- Multiple Auth Methods — OAuth2 (browser) and API token
Authentication
Sign in via the command palette (Ctrl+Shift+P):
| Command |
Description |
ConnexCS: Sign In |
OAuth2 browser sign-in (recommended) |
ConnexCS: Sign In with API Token |
Paste a Bearer token |
ConnexCS: Connect Claude Code and Codex |
Configure installed desktop agents with the bundled MCP server |
Desktop AI Agents
On desktop VS Code, ConnexCS Connect registers its bundled MCP server with VS Code automatically. Run ConnexCS: Connect Claude Code and Codex to add the same server to installed Claude Code or Codex clients. Credentials stay in a permission-restricted extension storage file and are removed on sign-out.
Desktop VS Code, Remote SSH, Dev Containers, and Codespaces default to tree-only mode, which leaves the user's workspace untouched. The ConnexCS view provides independent controls for MCP agent tools and an optional virtual workspace root. Enabling the virtual root appends one connexcs:/ root after all existing project roots; disabling it removes only that virtual root. No disk mirror is created.
The local MCP server and both desktop mode controls are intentionally unavailable in VS Code Web and the ConnexCS browser IDE. The browser IDE keeps its existing managed connexcs:/ workspace behavior and uses ConnexCS Assistant directly.
Requirements
- VS Code 1.80+ (VS Code 1.102+ for automatic native MCP discovery)
- A ConnexCS account
- Node.js 18+ when connecting external desktop agents to the bundled MCP server
Monorepo Development
This extension now lives inside the connexcs/cx-code repository as the
packages/cx-connect workspace package.
npm install
npm run build:prod --workspace packages/cx-connect
The custom VS Code Web image builds this extension from local source and bakes
it in as a builtin extension.
Publishing
npm run package --workspace packages/cx-connect
npm run publish:vscode --workspace packages/cx-connect
npm run publish:ovsx --workspace packages/cx-connect
These commands are package-scoped, but they run from the monorepo root.
Known Limitations
- Console log streaming — currently requires session cookie authentication (Bearer token support pending backend update)
Extension Settings
Desktop MCP configuration is available through connexcs.mcp.enabled, connexcs.mcp.mode, and connexcs.mcp.remoteUrl. The auto mode uses a configured remote Streamable HTTP server and otherwise falls back to the bundled local stdio server. The virtual-root preference is extension state rather than a web-visible setting.