code-server¶

Status: Current | Last reviewed: 2026-10-01

code-server is a full VS Code running in your browser, scoped to a catalog's source tree. It's how you author components, themes, and sample payloads — anything that lives as code rather than as form fields. You launch it from any catalog detail page.

Open code-server¶

1. Open the catalog you want to edit.
2. Click Open in code-server.
3. A new tab opens with VS Code already attached to the catalog's workspace.

Sign-in is automatic — TrueServe mints a short-lived session JWT and code-server validates it before letting you in.

What you can do here¶

• Edit components, themes, sample payloads.
• Run the checks listed in the workspace's README.md from the integrated terminal.
• Use the TrueServe Studio extension (pre-installed) for catalog-aware shortcuts, including the Preview panel for rendering components against sample props.
• Use Claude Code from the integrated terminal if your tenant's Claude Code license is enabled.

Allianz producer project files¶

The Allianz producer workspace contains four editable files under components/: PolicySnapshot.tsx, IllustrationRequest.tsx, CommissionStatus.tsx and ServiceReceipt.tsx. Shared card UI, formatting and types are in components/shared/. Use catalog.json for descriptions and sample props, styles.css for styling, and index.tsx for component registration.

Right-click a component file and choose TrueServe: Preview Component. The preview installs editor dependencies if needed and rebuilds after component or helper saves. Click Rebuild after editing styles or registration. Run npm run typecheck for a local check; this catalog uses the surface preview and has no standalone npm run dev.

The workspace also includes package.json, package-lock.json, tsconfig.json, a README and assistant guides. Saving these files updates the editable source. Use Publish when you want a new catalog version.

What you can't¶

• code-server is sandboxed to the catalog workspace. You cannot reach the rest of the platform's source from here.
• Long-running processes survive only as long as the code-server container does. If the platform restarts, restart your npm run dev too.
• code-server is not for editing live agents or workflows. Use the in-app editors for those.

Workspace persistence¶

Files you save in code-server are stored on a tenant-scoped volume that survives restarts. The volume is backed up nightly. If you accidentally delete a file, restore from the catalog's published source archive — every published version archives the source alongside the build artifact, so the worst case is "I lose work since the last publish."

Branching and version control¶

Workspaces with a Git repository support branching, commits and reverts through the integrated Git panel. Imported or demo-seeded workspaces may not have Git history. Publish builds the saved workspace files, including uncommitted changes; it does not check out main.

Note: code-server commits stay inside the workspace volume. They are not pushed to a remote git host unless you explicitly add one.

Multiple authors¶

Two people can have code-server open against the same catalog at the same time. They'll see each other's cursors via the collab gateway, and saved changes propagate live. Treat the catalog like a shared editor — coordinate before sweeping refactors.

See also¶

• Publishing a catalog