Persona

Use the Web Console to control the running desktop app from a browser. Its appearance and connection preferences belong to that browser.

ConnectCopy Anchor Link

1. In the desktop app, open Settings → Plugin API, enable the API, and create a key.
2. Open persona-console.laplace.live.
3. Enter the desktop host, API port, and key, then connect. On the same computer, use 127.0.0.1; the default port is 25034.

For another computer on the network, enable Allow Access on Local Network in the desktop app. An HTTPS console cannot connect to a remote unencrypted ws:// endpoint: serve the console over HTTP, or use a TLS proxy and enable Use TLS (wss://). The built-in Persona API does not terminate TLS. See Plugin API for server settings and key management.

Browser PreferencesCopy Anchor Link

Under Settings → Web Console, Language and Theme affect this browser only. They do not change the desktop app’s appearance. Connect Automatically reuses a complete saved connection when the console opens.

On the connection screen, Save API Key controls whether the key is stored in browser local storage. With it off, the current connection keeps the key in memory; enter it again after reloading. An explicit disconnect does not immediately reconnect, and a revoked key must be replaced.

The General and Performance sections change settings in the connected desktop app. The console’s section expansion states and panel width remain browser-local.

What You Can ControlCopy Anchor Link

The console mirrors scenes, layers, model controls, tracking, effects, and saved automations. Select a layer to edit its supported properties. Avatar shortcuts are grouped by model, with each group independently collapsible. A section bar atop each detail page jumps to any section on the page.

• Outliner: Matching the desktop app, Stage is a fixed row at the bottom of Layers; click it to open scene properties and clear the layer selection. Under object-pin-depth, a pinned 2D image, video, or webpage supports Depth adjustments in the host model's stack (older hosts omit the depth slider and row pin marker; Webpage sections no longer include a front/behind layer control).
• Text Layers: Depend on the object-text capability reported by the host (falls back to legacy text-objects). The Inventory's Text tab and the system font picker (which calls fonts.list to query desktop host fonts, never browser fonts) appear only on hosts supporting text layers. Keystrokes and slider adjustments in the Text section commit through object.setContent, treated by the desktop as in-place edits with one undo step per typing pause.
• Video Layers: Requires host to report the object-video-sound capability (falls back to legacy video-sound). Selecting a video layer reveals Loop, Mute, and Volume controls, written in place via object.setContent (older hosts swap the scene for each edit, flushing undo history, so the section is hidden). Because the web console lacks a direct transport relay to the desktop stage's live media element, transport controls (play, pause, and scrubbing) are omitted, leaving the saved paused state untouched.
• Chroma Key: Requires the host to advertise the object-chroma-key capability. Selecting an image, video, or webpage layer displays the Chroma Key section (toggle, key color, similarity, smoothness, and spill reduction). Older hosts omit this section to prevent edits from being discarded.
• Whole-Model Movement: On hosts reporting model-movement, selecting a Live2D model reveals horizontal, vertical, and depth movement sliders (range −50 to 50). Hosts with model-movement-pivot additionally expose Depth Pivot settings with "Pick on Stage" support, scaling the model around a selected anchor as you lean in or out.
• Privacy: When Stream Mode is active on the desktop app, webpage URLs are automatically masked to origin plus /*** (the full URL can still be copied via the copy button, and the input field allows direct paste replacement).
• Local Assets: Model and asset files belong to the desktop computer. The Inventory lists registered assets; registering a path requires an allowed plugin folder. It is not a browser file-upload workflow.

Automation authoring, shortcut recording, API key management, native file dialogs, stage gizmos, and application updates stay in the desktop app.