GWC Studio

Explore the Studio interface with example Taichu and Creative panels in your browser. Older Work/Design preview modes are compatibility examples within Creative, not separate products. The preview does not run agents, connect to your selected desktop, execute Creative generation or publish downloadable artifacts. A Design canvas example can import local JSON; that import remains in your browser.

The Windows release targets Windows 10 or later, 64-bit. Use the installer listed on the Download page. Check that release's supported-platform, backup and recovery notes first.

The planned Windows prerelease is unsigned: it is not code signed. When a download is offered, compare the entire SHA-256 with the value published for that exact installer. In Windows PowerShell, use Get-FileHash -Algorithm SHA256 -LiteralPath followed by your installer path in quotes. A matching hash checks file integrity; it is not a code signature, publisher authentication or a safety certification.

SmartScreen may show an unknown-publisher warning. Stop if the checksum is missing or different, the source is uncertain, or your device policy blocks installation. Do not disable Windows protection or bypass an organization's policy.

For an offered release, use the same Windows account that will run Studio. The per-user installation destination is %LOCALAPPDATA%\GWC Studio. Review the installer's optional Add to PATH and file-association choices and that release's instructions. These choices do not guarantee a system-wide install, a change to your default apps or automatic PATH cleanup on uninstall.

On first run, Studio opens a GWC Studio Setup wizard tab in the main work area. Follow its instructions; an error or incomplete connection is not a completed setup. The persistent left navigation remains available beside your work.

GWC Studio is the core desktop application. Sign in, finish its runtime setup, then choose the registered desktop that holds the session you intend to open. The separate GWC for VS Code extension can serve as an alternate desktop form when its own supported release is available.

New Session and Creative depend on the selected connected desktop. An account sign-in or a different online PC is not proof that the chosen session can run. Device, account, permissions and current desktop authority are checked separately. If offline, stop and verify the selected PC; there is no independent cloud session or automatic fallback to another machine.

Studio's main navigation provides the following GWC surfaces. New Session and Creative are the current entry names, not separate Work and Design creation tabs. These surfaces use the main work area while developer tools remain in their sidebar. Follow setup, sign-in, selected-device and unavailable-state messages rather than assuming that a session or generation has started.

1. New Session: Open the desktop conversation workspace and a new Taichu session on your PC.
2. Creative: Open Creative for selected-PC session briefs, saved names, model choices and eligible desktop canvas views. This is not a separate cloud Work/Design session.
3. Artifacts: Review artifacts already available to the active desktop workspace; their presence does not establish a new generation/download capability.
4. Agent-to-Agent: Open the supported collaboration and rooms view when available.

1. Use New Session with the plus icon for another Taichu session on your selected connected desktop. Creative has its own saved-session controls on that selected PC; it does not start another independent cloud Work or Design session.
2. Choose a session in Open panels to return to it. Use these entries to switch between ongoing tasks; use the + when you want a separate session.
3. Expand VSCodium tools for Explorer, Search and the other developer tools. The layout controls show or fold the primary sidebar, Terminal and bottom panel, and secondary sidebar.

The Design canvas component may still appear for supported visual work or older saved activity. If the layout offers Hide canvas / Show canvas, or Design request / Canvas tabs in a narrow pane, those controls change presentation rather than creating a cloud session. Preserve your local draft before changing views. Floating-window actions require the desktop application; browser previews do not execute tools or generate files.

Creative is the current product name for document and design work. The selected-PC remote controls currently support creating, listing, reading, renaming and choosing the saved model for Creative sessions. Verify the saved name and model readback. A submitted brief, model choice or session title is not proof of generated output.

Generation and remote file downloads are unavailable until matching desktop/runtime operations are supported.The existing Design canvas component keeps its identity for supported presentation and older saved work, but it does not create an independent cloud Design session. Use the Creative guide for current capabilities, historical format examples and limits.

Legacy Web Work/Design content stays under explicitly labelled read-only cloud history. Those records are not automatically moved to your PC. If a create, rename or model command has an unknown outcome, keep the original draft and request identity and do not resubmit automatically.

Expand VSCodium tools below the first divider to see the five default developer tools. Remote Explorer is a conditional sixth entry between Run and Debug and Extensions, only when an installed remote extension contributes the appropriate remote views; it is not present by default.

• Explorer: Workspace files and folders.
• Search: File and text search.
• Source Control: Version-control changes.
• Run and Debug: Run configurations and debugging controls.
• Remote Explorer: Conditional remote-environment view supplied by an installed extension.
• Extensions: Extension management.

These tools stay docked in the sidebar while Taichu or another GWC surface remains in the main area. Open panels lists the sessions currently open in the workspace. Recents follows Open panels and lets you return to earlier sessions.

Remote Explorer, phone-to-PC Connect, local MCP tools and external Taichu Remote Connect are separate capabilities. Installing Studio or signing in does not grant external LLM clients access to your folders. Taichu Remote Connect remains disabled by default and requires its own release, device pairing and explicit folder permissions.

Recents can contain Taichu and Creative work, including older Work/Design activity identities. Select only the session owned by your current profile and connected desktop; old cloud Creative records belong to the separate read-only legacy history, not automatic PC migration. If you see a sign-in prompt, use the footer. For a missing session check the shown GWC account, selected PC and Windows user profile.

An empty or unavailable list is not proof that a transcript was deleted. Contact GWC Support before deleting local data or starting over. Do not assume every local session, file or extension setting carries over between products.

The footer shows Sign In or your account name, with a Settings gear. Use Sign In to follow the sign-in flow, and check the displayed account before account-related work. The account row and gear open GWC Settings, with Profile, Accounts and the editor's Manage entries.

The normal Studio layout keeps these controls in GWC Settings. If the settings bridge is unavailable, fallback editor controls may appear; that is not a reason to delete your profile. Account sign-in is separate from a model provider's authentication and permissions.

Studio does not update itself. When a new installer is actually available on the Download page, read its version-specific upgrade and recovery notes and compare its full SHA-256. Back up important work, save open files, close Studio and run the checked installer for the same Windows account. Reopen Studio afterward; do not assume a background updater has installed a newer version.

These instructions do not make Studio available for download. Do not substitute a historical installer or assume an in-place downgrade is a supported recovery method.

Close Studio and use Windows Settings > Apps > GWC Studio > Uninstall for application removal. The app list may be called Installed apps or Apps & features. Uninstalling the application is not a GWC account-deletion request; user-data cleanup is a separate action.

Back up important work first and follow the release's data-retention and recovery notes. Do not assume every local session, third-party extension setting or provider history is retained or synchronized. Ask support about the specific data you need to keep before uninstalling or removing profile or native-agent folders.

Studio Help links lead to GWC Support. Finish incomplete setup, save your work and restart Studio once. A local Taichu connection error, an account-access error and a model-provider error are different problems. Keep the exact message; a restart is not a guaranteed repair or permission to resend a task.

Send support the Studio version, Windows version, redacted error and steps that led to it. Never include passwords, keys, private transcripts or unredacted logs. Do not delete user data or disable Windows protection as a troubleshooting shortcut.

GWC Studio is the core desktop. GWC for VS Code is the alternate form through the separately released GWC Connect extension for your existing editor. Studio includes GWC Connect, but the embedded extension and Marketplace package have independent release identities. Their navigation and settings layouts may differ. Both forms use your chosen local PC for Taichu and Creative rather than creating independent cloud sessions.

GWC for VS Code is available from the Visual Studio Marketplace. Install it there or search for "GWC Connect" in the VS Code Extensions view.

GWC for VS Code release details

Taichu and provider processing

Taichu brings your models, tools, and instructions together. Its runtime and local tools run on your machine; when you use cloud models, the request and included context are sent to your chosen provider.

Studio's editor telemetry is configured off. That is not a promise of zero network activity and does not control every third-party extension or model provider. Provider availability, account access, API keys, billing and terms are independent; installing Studio does not establish access through another client's subscription.

Use GWC Web in your browser and check the separate Mobile guide and Download page for supported features and release availability. Sharing a GWC account does not guarantee migration of all local data.