Practicus AI App Studio provides a user-friendly, structured view of a Practicus AI app inside VS Code.

Features

App Overview dashboard
- A single “home base” that summarizes the app and provides global actions like opening OpenCode, refreshing the App Map, and sandbox deploy actions.
App Map (left-side tree)
- A structured inventory of the app’s key elements (APIs, Agents, UI Pages, Schemas) so users can understand “what exists” without browsing folders.
Details panels
- Click an API/Agent/Page/Schema to open a rich details view with:
  - A short summary
  - Machine-derived structure (schemas, relationships, referenced files)
  - Actions like Explain, Visualize, Open code, and Make changes (OpenCode)
Explain & Visualize
- Generate human-friendly explanations and flow visualizations (Mermaid-ready) to help users quickly grasp what’s happening.
OpenCode handoff
- A first-class “Make changes” action that opens the OpenCode UI for guided edits.

Requirements

A Practicus AI worker environment.

Extension Settings

This extension contributes the following settings:

practicusAppStudio.backend.mode: Backend connection mode. Options: mock (use mock data), local (connect to k8s worker pod), production (auto-detect from env). Default is mock.
practicusAppStudio.backend.localInstanceId: Worker instance ID for local development mode (required when mode is local).
practicusAppStudio.backend.refreshToken: Refresh token (PRT_API_TOKEN) for authentication. Leave empty to skip auth in local mode.
practicusAppStudio.opencode.openCommand: VS Code command id used to open the OpenCode UI. Leave empty to auto-detect.
practicusAppStudio.mode: UI mode (biz or power). Default is biz.
practicusAppStudio.debug.enableDetailedLogging: Enable detailed logging for debugging. When enabled, logs input/output of backend requests and detailed execution traces. Default is false.

Debugging

If you encounter issues with the extension (e.g., empty tree view, errors in webviews, or backend connection problems), you can enable detailed logging to help diagnose the problem:

Open VS Code Settings (Cmd+, on macOS, Ctrl+, on Windows/Linux)
Search for "Practicus App Studio"
Enable "Debug: Enable Detailed Logging"
Open the Output panel (View → Output)
Select "Practicus App Studio" from the dropdown

With detailed logging enabled, you will see:

All function entry/exit points with [ENTER] and [EXIT] markers
Backend request/response payloads
Tree building operations with item counts
Full error stack traces with additional context
Manifest loading details (source, counts, etc.)

Example log output:

[2026-02-05T10:30:15.123Z] [backendClient] [ENTER] getWorkspaceManifest()
[2026-02-05T10:30:15.124Z] [backendClient] [DEBUG] Backend mode
  {"mode":"mock"}
[2026-02-05T10:30:15.125Z] [backendClient] Using mock manifest {"mode":"mock","generated":"2026-02-05T10:30:15.125Z","toolsCount":8,"integrationsCount":3,"agentsCount":2}
[2026-02-05T10:30:15.126Z] [backendClient] [EXIT] getWorkspaceManifest() returned {"source":"mock"}

This makes it much easier to:

Identify where errors occur (see the [section] marker)
Understand the data flow through the extension
Diagnose empty tree issues (check tool/integration counts)
Debug backend connection problems (see full request/response data)

Known Issues

If multiple OpenCode commands are detected, the extension will prompt you to choose one and store it in workspace settings.
Some features may show placeholder behavior when practicusAppStudio.backend.useMockData is enabled.
In remote/container scenarios, ensure the configured backend URL is reachable from the extension host environment.