GWC Connect

GWC Connect brings Taichu, Work, Design, sessions, artifacts, settings, and connected-device workflows to Visual Studio Code.

This package runs in a local VS Code desktop window and uses local file-system folders.

This platform-specific extension includes a sealed Taichu runtime for its declared operating system and architecture. Runtime assets come from the extension package and are verified against its integrity manifest before use. Attaching to an existing daemon requires that daemon to present the checked packaged identity.

Open GWC: Taichu from the Command Palette to start. GWC account and provider configuration remain in the extension's Settings surfaces.

Choose Classic, Dark, Light or Warm in GWC Settings → General → Theme (or during setup). The selection applies to the Connect sidebar, settings and native VS Code surfaces, plus open Taichu, Work, Design and mirrored session panels without resetting their content. Dark and Light use neutral buttons; Warm uses oak surfaces and walnut buttons. gwc.taichu.theme normally follows the workbench; an explicit value lets you give those session panels a separate palette. Selecting a theme in GWC Settings restores the shared selection.

For linked Autopilot advice, use /session create in the subject conversation, then /autopilot <goal> from that owner conversation. Activate Observer advisors after the run starts. Their findings are reviewed at planning boundaries and recorded as taken, rejected or deferred in the advice feed. Advice does not grant execution permission; Taichu's existing approval gates still apply. Use /autopilot stop to stop new work and let admitted work settle. Reloading or restarting requires fresh session membership and does not automatically resume a run.

The packaged component and dependency notices are indexed in THIRD-PARTY-NOTICES.md.