The REPL and script runner (gsi)

gsi is G#'s interactive REPL and single-file script runner. It ships as the Gsharp.Repl .NET global tool and is the fastest way to try the language without creating a project. It is a full-screen, keyboard-first TUI built on Spectre.Console that reuses the same Core compilation engine and LanguageServer analysis as the compiler, so the prompt behaves like a small editor (live syntax colors, completion, hover, and diagnostics) rather than a plain line reader.

Install

gsi requires a .NET 10 runtime.

dotnet tool install --global Gsharp.Repl

Update or remove it with the usual global-tool commands:

dotnet tool update --global Gsharp.Repl
dotnet tool uninstall --global Gsharp.Repl

Command-line usage

Usage: gsi [file.gs] [--help] [--version]
  file.gs      Run the given G# script and exit.
  --help, -h   Show this help and exit.
  --version    Show the gsi version and exit.
  (no args)    Start the interactive REPL.

Interactive REPL

Run gsi with no arguments in an interactive terminal to open the REPL:

gsi

Each submission becomes a transcript "cell" (your input plus its result or diagnostics). Because the session state carries forward, you can build up definitions incrementally:

» let xs = [1, 2, 3]
» import System.Linq
» xs.Select((x int32) -> x * 2).Sum()
= 12

The REPL is organised into keyboard-selectable tabs — REPL, History, Variables, Diagnostics, Help, and Settings — and includes a command palette (open it with :) for session commands:

Command	Effect
reset	Clear all accumulated session state and start fresh.
clear	Clear the current editor input.
theme [name]	Switch the color theme, or cycle themes when no name is given.
load <file.gs>	Evaluate a .gs file into the current session.
exit / quit	Leave the REPL.

gsi needs an interactive terminal; if its input is redirected it exits with a message instead of starting the UI.

Run a script and exit

Pass a .gs file to evaluate it in-process and print the final value. This is handy for quick experiments and shell one-offs — no .gsproj required:

gsi hello.gs

package Hello

import System

func greet(name string) string {
    return "Hello, $name!"
}

Console.WriteLine(greet("world"))

Diagnostics are written to standard error, and the process exits with a non-zero status if evaluation fails, so gsi file.gs composes cleanly in scripts and CI checks.

How it relates to gsc

gsi and the compiler share lexing, parsing, binding, and lowering. The REPL always runs on the interpreter path (the same in-process evaluation gsc uses when you omit /out:), which is ideal for exploration and tests. When you are ready to produce a managed assembly, switch to a .gsproj project or invoke gsc with /out:. Some CLR interop features are emit-only; see the gsc reference and the introduction for the differences between the interpreter and emit paths.