VoidLAB

Checking session…

Illustrated handbook

VoidLAB operator manual

Read the illustrated operator handbook for the current VoidLAB release: workspace anatomy, unified console behavior, inline stdin flow, tool pages, commands, and deploy-ready habits.

System overview

VoidLAB Operator Handbook

VoidLAB is a modern browser-based coding workspace built around an editor, a multi-file project model, a unified execution console, and focused tool pages for publishing, collaboration, AI guidance, and profile management.

Editor model

Multi-file local workspace

Runtime model

Judge0-backed execution + preview

Browser-based IDE with multi-file workspace and live execution

Unified console with Output, Terminal, and Ports tabs

Inline stdin capture for interactive Judge0-backed runs

Dedicated pages for GitHub, collaboration, AI guidance, profile, and the manual itself

Fast start

1.Sign in, land in the editor, and confirm the active file in the workspace header.

2.Create files or folders from the explorer, or import an existing set into the local workspace.

3.Pick the active language from the top bar, write code, then use Run or Preview.

4.Use the unified console to inspect stdout, stderr, compile output, runtime status, and workspace commands.

5.Open the tool pages when you need GitHub publishing, collaboration, AI help, profile edits, or this handbook.

Figure A

Workspace map

Technical blueprint of the VoidLAB workspace showing the editor, unified console, and tool hub.

Core zones

Editor: write and switch files with language-aware Monaco editing.

Unified Console: one execution surface for output, workspace terminal commands, and future ports.

Tool Hub: dedicated routes for the manual, GitHub, collaboration, AI guide, and profile.

Workspace behavior

Files are tracked inside a local workspace model, not a native filesystem shell.

Folders, file paths, and terminal history persist across sessions in the browser state.

The active file drives language selection, preview behavior, and GitHub publish targeting.

Figure B

Interactive execution flow

Technical execution diagram showing Run, inline stdin capture, Judge0, and structured results.

Step 1

Run or Preview

Runnable files go through Judge0. Previewable browser documents open directly in a new tab.

Step 2

Inline stdin capture

If the active program appears input-driven, VoidLAB pauses in Output and buffers stdin lines inline.

Step 3

Judge0 submission

Buffered input is encoded into the submission payload together with the active source code and language target.

Step 4

Structured results

Output returns with stdout, stderr, compile output, runtime messages, memory, time, and exit metadata.

Operations

Unified console behavior

Output

The default tab. It shows execution transcript events, inline stdin prompts, runtime metrics, and all structured Judge0 results in one place.

Terminal

This is the local workspace command layer for commands like ls,tree, touch, open, and rm.

Ports

A reserved operational area for future forwarded runtime ports. For now, browser previews still open directly from the editor toolbar.

Reference

Workspace command sheet

help

Shows the supported workspace commands available inside the built-in terminal.

pwd

Prints the current workspace directory.

ls [path]

Lists files and folders in the current or targeted directory.

tree [path]

Renders a folder tree so you can inspect project structure quickly.

cd <path>

Moves the workspace terminal to a different folder.

mkdir <path>

Creates a folder and preserves the full folder chain.

touch <path>

Creates a new file, infers the language by extension, and opens it.

open <path>

Focuses an existing file in the editor.

cat <path>

Prints file contents into the Terminal tab.

rm <path>

Removes a file or folder path from the local workspace model.

clear

Clears terminal history inside the workspace command view.

Modules

Tool hub reference

GitHub Publish

Push the active file into a new or existing repository after linking GitHub.

Collaboration

Create rooms, share links, sync workspace state, and exchange room messages.

AI Guide

Ask the built-in guide about workflows, debugging strategy, supported commands, and organization.

Profile

Manage your bio, optional display picture, social links, and recent activity history.

Preferences

Profile and theme notes

Profile controls

Display picture uploads are optional. Leaving the avatar empty is a valid clean state and does not block profile saves.

The off-white theme (Fade white) is the default, designed for higher contrast with a refined cherry-red accent.

Theme system

The rich black theme pairs a deep dark background with vivid red highlights for an immersive coding experience.

Workspace data, terminal history, and profile-side activity are stored locally in the browser experience unless synced through dedicated flows such as collaboration or GitHub publishing.

Checklist

Deploy-ready habits

Final operator pass

1.Confirm the active file and language before running or exporting.

2.Use Preview for browser-native documents such as HTML, CSS, Markdown, JSON, or XML when applicable.

3.If a program needs input, let VoidLAB collect stdin inline in Output before execution rather than using a detached input box.

4.Review stdout, stderr, compile output, memory, time, and exit metadata in the Output tab after each run.

5.Push a clean result to GitHub from the publish page once the file and branch target are correct.