Creative

Creative is the current GWC document and design workspace. It uses your selected connected PC, alongside Taichu's desktop-backed New Session. It is not an independent cloud Creative session.

What Creative can do now

The current selected-PC control supports exactly five kinds of session metadata work: create, list, read/open, rename and model selection. Creating a session stores its intended brief and output kind; renaming or choosing a model changes saved metadata after a confirmed readback. This is not a document-generation or artifact-download command.

Document and output generation is not currently available from the remote selected-PC consumer. It remains unavailable until a matching, reviewed desktop/runtime generation operation is supported. A saved session name, output kind, model choice or browser example is not proof of a finished PDF, PPTX, DOCX, XLSX, design image or downloadable file. There is no cloud fallback.

Open GWC Connect Open Creative

Get started with your selected PC

Select the connected desktop: Open GWC Connect and choose the specific registered, online, active PC that owns your work. GWC Studio is the core desktop; GWC for VS Code is the alternate desktop form. Cloud sign-in alone or a different online PC is not an eligible workspace.
Open Creative: Creative is the current product name instead of separate Work and Design entry surfaces. The selected PC, account and current device/lease authority must agree. No separate cloud Creative runtime is created if the PC is unavailable.
Work with saved session metadata: The current remote Web and Mobile consumer can create a session from a brief and output kind, list sessions, open/read an exact saved session, rename it and change its saved model selection. Verify the saved name/model readback before treating an edit as confirmed.
Keep your draft if the outcome is uncertain: An interrupted or unknown create, rename or model result may already have reached the original PC. Keep the original request identity and your unsaved draft; do not automatically resend it, choose a different PC as fallback or assume an unknown outcome means no change.

The GWC Web interface can open without a local installation, but PC-backed work requires the selected desktop. For setup and permissions, see the GWC Studio guide.

Briefs, output kinds and saved model choices

Give the purpose, audience, constraints, source context and desired shape in the original brief. Creative's current output kinds are Design, Résumé, Invoice, Pitch deck, Report and Proposal. They describe intended work, not an instruction to start rendering or charge for a generated output.

Use a model ID to save a pinned selection, or leave the field empty to inherit the selected PC's default. Check the saved readback rather than assuming a submitted rename or model change succeeded. Model selection alone never triggers generation.

The Design canvas retains its component identity for legacy or example visual work. It is not a separate cloud Design product. A browser preview can demonstrate a canvas or keep an imported JSON draft locally without executing an agent on your PC or publishing an output.

Earlier Work and Design sessions

Work and Design were earlier labels for document-task and visual brief surfaces. They are now covered by Creative, while old work/design activity identities are still recognized when reading saved history. A historic cloud record is not automatically copied or migrated onto the selected PC.

Open Legacy cloud history (read-only) explicitly to inspect earlier records in the selected account. This separate path may read saved content but will not create, regenerate, edit, migrate or silently fall back to the cloud. Saved links need their correct session/activity identity; other-account or invalid links are refused.

Historical document formats (reference, not current instructions)

Earlier Web Work/Design document tools tied each format button to a particular template. The button, not the wording, determined the document shape: a request for a birthday card in the PDF path still used the résumé template. The following examples help identify earlier saved work; they do notdescribe a currently working PC-generation or download button.

PDF — A résumé

Name, title, contact details, summary, experience, education and skills, laid out on US Letter. The earlier PDF-only browser preview showed this kind of document.

Earlier example brief: Prepare a résumé for Maria Chen, a senior product designer with eight years of UX research and design-system experience.

PPTX — A pitch deck

A widescreen deck with title, bullet, two-column, statistics and closing layouts. Historical templates often aimed for 8–12 slides, not a guaranteed count.

Earlier example brief: Outline a seed pitch for Lumen, a B2B product for generating sales proposals.

DOCX — A business proposal

A Word proposal with a cover page, section headings, a deliverables table, a totals row and numbered footers.

Earlier example brief: Draft a three-month website redesign proposal from Acme Consulting to Northwind Traders.

XLSX — A data report

A multi-sheet workbook with frozen headers, filters, alternating row shading and a bordered totals row.

Earlier example brief: Organize a quarterly sales report by region, units and revenue.

Aesthetic System and Style Era (older documents)

In historical document templates, Aesthetic Systemselected accent colour for headings, table fills and section markers; Style Era selected sans, serif or mono fonts. Only a picker the user touched was transmitted. Leaving both untouched used an older default blue accent and sans font. These notes explain past document appearance, not a current selected-PC generation step.

Limits in those earlier templates

Earlier prompts and attached text shared a 16,000-character input budget.
Decks generally targeted 8–12 slides; final length was not guaranteed.
Historical slide decks did not automatically generate images for placeholders.
The earlier browser preview supported PDFs; other formats required a produced file.
In that workflow a revision could regenerate the whole document rather than edit a durable version. It could incur another usage charge; this is not a current price or execution promise. Review current pricing for any separately enabled paid operation.

Missing sessions, uncertain saves and legacy outputs

Verify the selected connected PC, current account and saved response. An unavailable desktop, older lease or uncertain request does not mean the session was deleted or the mutation was safe to repeat. Retain your original brief, draft and request identity; do not switch to another PC or cloud session as an automatic fallback.

If the data is from the previous Web Work/Design workflow, look in the separate read-only legacy history, not the PC session list. Contact GWC Support for an unavailable saved record rather than deleting local data or assuming a historical filename is a current downloadable artifact.