Customer Command Center for VS Code

Customer Command Center brings account-team operations and opportunity guidance into VS Code over the shared product core. Existing TLC-prefixed commands and settings remain unchanged.

Download VSIX — manual installation

Marketplace → Customer Command Center → Overview → Download VSIX

This link downloads the latest published .vsix file without opening VS Code or installing it. Manual installation remains subject to your organization's policies.

It defaults to SQLite sample business data with real Foundry AI. Only inference uses the network; missing Foundry access produces a labeled offline fallback. Select tlc.aiMode=sample (or TLC_AI_MODE=sample) for completely offline AI. Live mode continues to use its existing delegated Dataverse/MSX access and keeps tokens in the extension host. Installation and sample mode do not grant access to enterprise services.

Extension identity and updates

New builds use CAC.ccc-vscode (publisher: CAC, name: ccc-vscode). The registered publisher is Customer Assistant Center by Girish Pillai; the extension title remains Customer Command Center. This is a new installation, not an update to tlc.tlc-assist-vscode or the former unpublished ccc.ccc-vscode candidate. Disable any older identity before enabling the new one because their commands and views are shared. Keep the old installation and its data until you choose to remove them. New extension-owned storage starts separately; existing tlc.* settings remain in effect.

The extension is distributed under the Customer Command Center Proprietary EULA included as LICENSE.md in the package and referenced by its license metadata. It grants limited internal-business use, not private-repository access or unrestricted redistribution; applicable third-party licenses and mandatory legal rights remain intact. Bundled dependency notices are included in dist/host/THIRD-PARTY-NOTICES.md and dist/webview/THIRD-PARTY-NOTICES.md, with additional attributions in the package-root THIRD-PARTY-NOTICES.md.

Marketplace installations use VS Code's native updates for CAC.ccc-vscode. Updates require increasing compatible versions and permitted global/per-extension update settings, connectivity and organization policy. File-installed VSIX packages have auto-update disabled by default; check the extension's Auto Update toggle once its Marketplace version is available. Publishing a new identity does not automatically install it or migrate older identities.

Install

You need VS Code or VS Code Insiders 1.90.0 or later. The VSIX is self-contained; Node.js, npm, development sources and repository access are not required.

1. Install Customer Command Center from the Marketplace and verify publisher CAC / Customer Assistant Center by Girish Pillai and extension ID CAC.ccc-vscode.
2. For manual installation, use the Download VSIX — manual installation link above. In VS Code or VS Code Insiders, run Extensions: Install from VSIX... in the Command Palette, select the downloaded .vsix file, and review publisher trust.
3. Disable any older pilot/candidate identity before enabling this one. Keep its installation and data; storage is not copied automatically.
4. Run Developer: Reload Window, then TLC: Open Assist, or select the TLC Activity Bar icon. Existing TLC command names are intentional.

The default uses local sample business data with Foundry AI. For sample business data and fully offline AI, set these values in VS Code Settings:

{
  "tlc.mode": "sample",
  "tlc.aiMode": "sample"
}

Foundry inference requires access to the configured Microsoft Foundry project. If access is unavailable, the UI labels its offline fallback rather than silently claiming a model response. Live mode additionally requires an authorized corporate Microsoft identity and delegated MSX/Dataverse permissions. The shipped service configuration targets the existing Microsoft organizational services; a personal Marketplace account does not grant those permissions. For live use, sign in through VS Code's Microsoft authentication and follow your organization's access process.

Features (sample mode)

• Activity Bar container with Connection, Portfolio, and Plays views.
• Workbench webview (editor area) for portfolio work, MCEM stage review, four agent capabilities, and deterministic plays.
• Account curation: add a customer by name or TPID, remove a tracked customer with named confirmation beside Add customer or from the selected account, and restore it through Add customer > Add again. Empty manually added accounts remain available for Discovery.
• Discovery: review all active opportunities for visible accounts by Solution Engineer domain and use Add me or Remove me for the real Deal Team membership. Azure-portal-style customer filter chips support inclusion and exclusion with searchable multi-select choices. Select Account, Stage, or Action to toggle ascending/descending sorting, just as in the desktop and web apps. These filters affect only the Discovery view, not account visibility or membership.
• Action styling: Add/Remove customer, Comments, sorting, and filter controls use the theme's accent/link color; customer and opportunity names remain data text. Removal actions retain their warning color and disabled controls remain muted. The native TLC: Refresh Data, TLC: Add Customer Account, and TLC: Remove Customer Account toolbar commands, plus the inline Remove Customer Account action, use blue light/dark SVG icons. This workspace gives native hover widgets a high-contrast blue-on-dark palette, and TLC webview popups reuse that palette with semibold text. VS Code continues to own the native tooltip font.
• Plays: run named workflows (stale opportunity sweep, overdue milestone triage, governance exceptions, and more) and review typed result cards and operational queues. Live results appear page by page and remain marked incomplete until the run finishes. The initial cohort allows 60 seconds for execution and 15 seconds of UI completion grace; capped or unavailable sources remain visibly partial.

Visible active opportunities where the signed-in user is a current Deal Team member or belongs to a milestone team enter Portfolio, milestones, agents, and Plays. Discovery's On deal team label uses only actual Deal Team membership; a milestone-only opportunity offers Add me even though it remains in Portfolio. Adding an account alone never expands that downstream working set. Remove customer is a reversible TLC-only preference: it clears the account from active Portfolio, Discovery, search, New selectors, and future Plays, without deleting source records or changing Deal Team or milestone-team membership. Saved runs and the official Seller Dashboard are unchanged. Preferences stay local to the current app/profile rather than syncing between Desktop, Web, and VS Code. Native tree and workbench views refresh together.

In live mode, configure TLC_MSX_ACCOUNT_TPID_FIELD with the tenant-verified logical field name to enable TPID search. Name search remains available without it. Account preferences are partitioned by Dataverse user ID and stored under the extension global storage directory; no credential is stored in the preference file.

Data handling

• Sample business records come from bundled sanitized sources and are processed in the local extension host/store. Real Foundry AI can still send your prompt and selected context to the configured Microsoft Foundry service; use tlc.aiMode=sample when you do not want those inference requests.
• Live features access authorized Microsoft services using delegated identity. Content selected for AI processing can be sent to the configured Foundry project. Review your organization's permissions and disclosure/retention rules before selecting real business or meeting content.
• Preferences, saved work and local caches belong to the current app/profile and configured data paths. Service-side data handling and retention are controlled by the relevant Microsoft service and organization, not by extension installation.
• Tokens stay in the extension host/authentication boundary, not the webview. Marketplace installation grants no enterprise-data permissions.

Microsoft service handling is also subject to applicable service terms and the Microsoft Privacy Statement. This notice describes the extension's data flows; do not assume offline AI changes VS Code's own independent network/update behavior.

Support

Use the Q & A tab on the Marketplace listing for non-confidential product questions. Do not post tokens, prompts, customer identifiers, business documents or private configuration. For a sensitive matter, arrange an approved private channel with the publisher before sending details. Enterprise access and service-retention requests should also go through your organization's administrator.

The source repository is private. Installing the VSIX, reading its included EULA and dependency notices, and using Marketplace Q & A do not require source access. Compiled JavaScript and shipped assets remain inspectable; the proprietary EULA does not make the shipped binary content technically secret.

Security

• Delegated-user access only; tokens never enter the webview.
• Default-deny MCP tool policy; read-only first.
• Strict webview Content Security Policy with a per-load nonce.
• Every bridge message is schema-validated on the host.