Cognitum One Developer Console for VS Code

This extension brings Cognitum One, FreeTokens, and the local Meta Proxy into Visual Studio Code without copying its bearer token into workspace settings.

Features

• Shows the authenticated proxy plane and health in the status bar.
• Provides a product-led developer console aligned with the Cognitum One website, with dedicated Overview, FreeTokens, Build, Agents & Pods, Services, Usage, Account, and Proxy Settings sections.
• Promotes available FreeTokens capacity, active grants, connection, rewards, usage, and expiry in the primary workflow.
• Displays routing reason, usage pressure, workload policy, and credential source from GET /status.
• On first start, offers Cognitum One Authorization Code + S256 PKCE sign-in through the installed meta-proxy CLI and https://auth.cognitum.one/oauth/authorize.
• Shows a redacted user administration panel with local logout, OAuth expiry, and aggregate FreeTokens grant totals.
• Shows live Cognitum One API, Meta-LLM, and HarnessaaS availability plus discovered model tiers.
• Mirrors the website Studio's five reviewed capability planes and opens all 11 authenticated customer service workspaces.
• Provides a complete website-source-reviewed All Capabilities catalog: Comms channels/commands/mentions, 29 Meta-LLM operations, 8 MCP tools and 14 resources, 99 Seed device routes, 66 RuView sensing routes, API integration, platform services, durable support, owned marketplace, live analytics, and billing administration.
• Opens a new terminal with ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN set for that terminal only.
• Opens the local proxy-config.toml.
• Connects FreeTokens through a 60-second single-use browser claim, with an explicit direct browser sign-in fallback for older proxy versions.

Development

cd vscode-extension
npm install
npm test

Press F5 in VS Code with vscode-extension open to launch an Extension Development Host. Run npm run package to create a VSIX.

CI runs the same clean-install, strict compile, unit-test, and VSIX packaging sequence whenever extension files change.

On Linux with Xvfb, npm run capture opens an isolated Extension Development Host for visual verification. The nine tracked section captures use deterministic service fixtures; raw XWD files remain excluded from Git and the VSIX.

Security model

The extension reads ~/.ruflo/proxy-token (or $RUFLO_STATE_DIR/proxy-token) only when it calls the proxy or creates a configured terminal. It does not persist the token in workspace settings, global settings, logs, or the clipboard.

Non-loopback proxy origins are disabled by default. Enabling one also requires HTTPS. Cognitum One and FreeTokens authentication stays in the system browser and Meta Proxy process; the extension does not scrape browser tokens or receive OAuth credentials. Account and FreeTokens administration requires the exact local proxy token, not a scoped worktree capability. All settings that could redirect a credential or browser handoff are machine-scoped, so a cloned workspace cannot override them through .vscode/settings.json.