VisionFall Studio Handbook

01Overview#

VisionFall Studio is a development environment for Windows, macOS and Linux, built by VisionFall Pvt. Ltd. It is designed around three things that usually cost developers the most time:

• Getting someone into your code. Share your whole studio with a nine-digit ID and decide exactly what the other person may do — Sharing a studio.
• Getting a language onto your machine. Install a complete toolchain in one click, verified afterwards — Setting up languages.
• Remembering the exact command. The terminal suggests commands, flags, branches and paths as you type — Terminal suggestions.

Around them sits a complete editor: completion that reads your project, integrated debugging, native Git, six themes and six keymaps, and a bridge that lets Windows and Linux share one workspace.

02Launch & downloads#

VisionFall Studio 1.0 launches on 1 October 2026. The setup files below unlock on their own at that moment — there is no need to reload.

03System requirements#

On every platform#

Memory

8 GB minimum, 16 GB recommended

Disk

About 2 GB, plus the languages you install

Display

1280 × 800 or larger

Code sharing

An internet connection on both sides

04Sharing a studio#

Code sharing lives in the Remote Assist view. One person shares their studio; the other connects to it from their own copy of VisionFall Studio. Nobody needs an account, and nothing has to be pushed anywhere first.

Share your studio#

1. Open the folder you want help with. A session shares the workspace folders, so a window with no folder open cannot share.
2. In Remote Assist, choose Share This Studio.
3. Give the other person the Studio ID — nine digits, such as 428 615 903 — and the session password. Copy ID & password puts both on the clipboard at once.

Connect to someone else's studio#

1. In Remote Assist, choose Connect to a Studio…
2. Enter the Studio ID the other person read out.
3. Enter the session password shown on their screen.

Choosing what they can do#

When someone connects, the host sees who is asking, which version of the studio they run and on which platform, and picks one of three levels — or declines.

During a session#

• Chat — message the other side without leaving the studio.
• Follow Their Cursor — your view moves with theirs as they work.
• Shared Terminal — available when the session has full control.
• Add to Workspace — their shared folders appear in your Explorer beside your own, and are removed again when the session ends.
• Activity — a running log of every file opened, edited, created or renamed during the session.

If the host has unsaved changes in a file, the studio asks the guest to wait for a save before editing it, so nobody overwrites anybody.

Ending a session#

• Disconnect leaves a session you joined.
• Stop sharing ends your session and disconnects everyone in it.
• New password issues a fresh session password. People already connected keep their access.

Settings#

05Setting up languages#

Languages are installed from the Development Environments view. Pick one, press Install, and the studio fetches the toolchain, configures it and adds the matching editor extensions.

Available in one click#

Need something that is not on the list? Search from the same view — the studio looks for a matching environment in the extension marketplace.

What an install does#

Progress is shown as “Step 2 of 6”, with each stage named as it runs:

Why verification matters#

An installer can finish without error and still leave nothing usable behind. The studio only reports success when its second look actually finds the toolchain — otherwise it says so, with notes on anything that needs a manual step.

Removing a language#

The same view removes a toolchain, and verifies that too — a removal only counts as done once the toolchain can no longer be found.

06Terminal suggestions#

As you type in the integrated terminal, the studio suggests commands, flags, git branches, file paths and earlier commands — inline as faint ghost text, and in a list with a short description of each.

Using suggestions#

Supported shells#

Bash, Zsh, Fish and PowerShell on every platform, and Git Bash on Windows — including shells running inside WSL2. Suggestions rely on the terminal's shell integration, which is on by default.

Settings#

07Themes & keymaps#

You choose a theme and a keyboard layout the first time the studio opens, and can change either at any time from the Command Palette — no restart needed.

Code completion#

Suggestions in the editor are ranked by what the surrounding code actually does, with the signature, a short preview and the import added for you when you accept.

08Launch modes#

Running it in a browser#

Start the studio server with visionfall-studio serve-web, then open http://localhost:8000.

Network parameters#

For the documented bridged setup, these defaults are assumed:

Local IP

172.17.190.230

Subnet mask

255.255.255.128

Gateway

172.17.190.129

DNS

172.17.190.129, 8.8.8.8

09WSL2 bridge#

On Windows, the studio can run its core inside a WSL2 Linux distribution and show it on the Windows side — as a native window through WSLg, or in the browser. Everything it runs then follows Linux conventions, whichever side you started from.

Mixed Windows and Linux work tends to fail in small, expensive ways: a script saved with CRLF endings that will not run, a path that exists on one side only, a shell that is not the one the command expected. The bridge normalises line endings, shell and paths before anything reaches Linux.

10Troubleshooting#

11Support#

VisionFall Studio is built and supported directly by VisionFall Pvt. Ltd. Every message is read and answered by a person.

Licence#

VisionFall Studio is proprietary software. © 2026 VisionFall Pvt. Ltd. All rights reserved. Use is governed by the licence agreement shown during installation.

12Reference#

Command line#

Where the studio keeps things#