Public snapshot updated on 2026-04-14 for VLCode Lite
1.33.7and VL4.1.
This guide is the fastest way to understand what the current VLC runtime looks like, how to launch it locally, and what each major panel is for.
- Node.js 18+
- a local VLC checkout
- a supported login or local model/provider setup for the AI and platform-connected flows in your environment
git clone https://github.com/VisualLogic-AI/VL-Code.git
cd VL-Code
npm install
npm run devOpen http://127.0.0.1:4000.
The matching public language and sample assets live here:
Recommended first imports:
VL_CourseScheduler_WithCaseJsonMap.zipVL_HabitCheckin_WithCaseJsonMap.zipVL_MediaShelf_WithCaseJsonMap.zipVL_ShoppingList_WithCaseJsonMap.zipVL_VoteMini_WithCaseJsonMap.zip
- Start the shell and confirm the workspace opens on port
4000. - Import one of the public sample packs from
VisualLogic.ai-VL. - Open
Codemode to inspect the file tree and source. - Switch to
Flowto see workflow orchestration and runtime structure. - Switch to
Mapto inspect references and project-level metadata. - Open
Visual,Logic, andDatato inspect the embedded editor panels. - Use the AI assistant and detail log together when generating or adjusting files.
The main editing view for VL source files, with the project tree on the left and the current file open in the center.
The host-native workflow and orchestration view. This is where users can understand execution structure, node relationships, and runtime progress at a glance.
The structural overview mode for apps, sections, services, components, and their relationships.
The AI assistant is the main operator-facing panel, while the detail log carries the verbose workflow and tool trace.
These panels run inside the embedded VxEditor layer and are what make VLC feel like both a code IDE and a graphical editor.
Canvas-style editing for layout, object placement, and immediate structural inspection.
Visual event and handler inspection for interaction logic and action flow.
Database-oriented inspection for schema, tables, and field settings.
Service-side logic inspection for backend behavior and handler wiring.
Theme token and styling inspection for visual system tuning.
VLC currently behaves as a two-layer shell:
- Host layer: file tree, code editor, map, flow, AI assistant, detail log
- Embedded layer: visual stage, logic editor, data browser, object tree, properties
That split is intentional. Users can move between source-first work and panel-first work without leaving the same runtime shell.
- The current public shell starts on port
4000. - Compile, preview, and deploy actions require VisualLogic platform access in addition to the local IDE.
- The
2026-04-14screenshots in this guide come from the current host shell. - Several embedded panel screenshots are taken from the latest stable regression artifacts (
2026-04-03) so the public gallery shows fully populated panel states while the headless capture path for bridge-backed views is still being hardened.








