INTRODUCING REATERM / RUST NATIVE

Explore everything.
Change nothing.

The terminal built to look, not touch. A small, intentional set of read-only commands, backed by OS-specific kernel restrictions—so inspection stays inspection.

Linux / macOS / Windows No arbitrary shell execution
reaterm · read-only session
❯reaterm ls -la
dir4096src/
dir4096docs/
file4324README.md
❯reaterm chmod 777 README.md
✕ DENIEDnot in the read-only allowlist
❯
NATIVE RUSTLANDLOCK + SECCOMP
Read-only by design

Illustrative terminal output

08Explicit read-only commands
00Arbitrary executables allowed
02OS kernel guards

01 / THE IDEA

Not a shell with rules.
A smaller surface entirely.

ReaTerm does not try to guess which Bash commands are safe. It only implements read-only inspection operations and rejects everything else.

Allowlist, not guesswork

ls, cat, grep and five other native commands. No interpreters, scripts, unknown flags, or subprocess forwarding.

POLICY / 001

Kernel-level guardrails

Linux requires Landlock and seccomp; macOS uses Seatbelt; Windows uses a low-integrity write-restricted access token. Enforcement failures stop the command.

KERNEL / 002

Scoped. Predictable. Small.

Read paths are relative to a caller-chosen root. File sizes, output and directory listing lengths are bounded. No hidden command hooks.

DESIGN / 003

02 / UNDER THE HOOD

An intentionally short path.

The parser validates the entire request. Only explicit read operations can reach the native filesystem reader after mandatory kernel confinement is installed.

OPTIONAL The Python and TypeScript adapters can ask an OpenAI-compatible model to veto a request. An AI response can never extend the Rust allowlist.

03 / QUICK START

From zero to read-only.

Choose your integration. Each path uses the same compiled native engine and requires Linux with Landlock and seccomp, macOS with Seatbelt, or Windows x86-64 with a low-integrity write-restricted token.

Install the native CLI

Clone the repository and install the binary into Cargo's bin directory. Run commands directly from your terminal.

BASH
git clone https://github.com/Pro-GenAI/ReaTerm.git
cd ReaTerm
bash scripts/install.sh
reaterm ls -la
reaterm cat README.md

Cargo's bin directory must be on PATH. Alternatively, build via cargo build --release --manifest-path src/rust/Cargo.toml.

04 / INTEGRATIONS

One engine. Three ways in.

Install locally from source today. Package registry listings are linked for discovery, but publication status has not been verified.

NATIVE

Rust CLI

The security boundary. All commands are implemented directly in Rust.

cargo install --path src/rustExplore Rust source

Registry availability is not guaranteed. Use the repository source and installation instructions above until a package is confirmed published.

05 / THE BOUNDARIES

Security without
the fine-print tricks.

Read-only means the ReaTerm process does not implement writes. It is not a replacement for a trusted launcher or a confidentiality control.

Read the full threat model

Parent shells are separate. Redirecting reaterm ls > file.txt can still create or truncate a file before ReaTerm starts.

Inherited descriptors matter. Landlock does not revoke previously opened file descriptors; launch it from a trusted process.

The root is caller-selected. ReaTerm is not a tool for hiding files inside an otherwise readable directory.

Linux, macOS and Windows x86-64. Other Windows architectures and 32-bit ARM are unverified. Windows token protection is thread-scoped.

READY TO INSPECT?

Keep the insight.
Drop the risk of accidental writes.

Start with the Rust CLI, or build against the same engine using Python or TypeScript.