LXLEONARDX

LEONARDX / WORKSPACE

LeonardX Web IDE

Edit files in an owned project workspace.

Workspace editor · authenticated

Edit project files in a protected workspace.

The Web IDE loads files from the selected project after server-side ownership checks. It supports file creation, editing, and saving; its console is a safe preview, not a shell or deployment runner.

Project file editor
Changes save to the authenticated project record.

The file API validates relative paths and caps workspaces at 250 files, 256 KB per file, and 2 MB total. It does not expose files to another user’s account.

Preview console
No shell, generated-code execution, or deployment.

Supported commands are help, ls, cat <path>, and clear. Other input is rejected by the preview console.

Open a real workspace

From your signed-in dashboard, open a project and choose Open IDE. The route requires that project’s real ID and session; the preview below uses no customer workspace.

/ide/[workspaceId]·GET/PATCH /api/workspaces/[id]/files
Integration StudioSimulation · no request sent

Follow the integration, one step at a time.

Explore real LeonardX contracts with sample code and a simulated terminal. This walkthrough never uses credentials, contacts endpoints, or changes account data.

Source-backed examples

Walkthrough scenario

The existing workspace editor uses the authenticated project-files route.

Open a real workspace

The dynamic IDE route receives a workspace ID; the server checks ownership before returning project files.

workspace-link.tsx1 / 2
<Link href={`/ide/${encodeURIComponent(workspaceId)}`}>  Open workspace</Link>

Execution preview

Synchronized to the highlighted code

Illustrative navigation · no workspace loaded
leo · idesimulated

[SIMULATION] Navigation not performed

Route: /ide/[workspaceId]

Workspace files are loaded only after server-side ownership checks

What is live? The examples describe existing API, SDK, CLI, and webhook behavior. This preview itself is local UI only and does not report a real execution.

Open and save files: step 1 of 2. Open a real workspace