Do I need a TypeSafe key to try it?

No. The local 3D baseline is the default controller and needs neither a key nor a backend. Selecting the TypeSafe controller adds a small Bun backend, returned Choice probabilities, bounded inference, and attempt and latency accounting; the ready screen also offers a guided replay that uses recorded decisions and makes zero inference calls, so you can see the whole workflow before spending anything.

When it picks differently from the baseline, does that mean TypeSafe did better?

No, and the README says so directly: a different choice does not establish a better expedition outcome. The comparison mode records the baseline's alternative from a detached copy of the same input and reports agreement or disagreement on the complete action including its route, which is a comparison of choices rather than a verdict on quality.

Can I actually see why it decided to do something?

Yes, that is the core of the project. Expanding the decision timeline shows the knowledge, resources, the complete candidate list and the selected action at each decision, and selecting a numbered map target pauses the session and shows that decision's original observations, memory, resources, probabilities and usage.

What happens when a Jev call fails mid-expedition?

It does not silently fall back. The project adds explicit Retry and baseline continuation after inference failure, with controller transitions recorded in the timeline and results. Pending, failed and obsolete Jev decisions keep their suggestion without executing it and without changing which controller is in charge.

What is the world the rover actually explores?

A 42 x 38 authored area with a charging base, twelve sample sites in three research regions and a localized dust storm. Expeditions last eighteen minutes.

How do I run RoverLab locally?

It is a React, TypeScript and Vite app using Three.js through React Three Fiber, with Bun for dependency management and tests plus a small Bun backend that uses the official TypeSafe JavaScript SDK.

Do the expedition records survive a browser reload?

Yes. Expeditions save automatically to browser-local storage, and saved records can be inspected read-only and exported or imported as validated JSON.

CommunityJev Demos & Experiments

Roverlab

A browser-based planetary rover sandbox with a keyless local 3D baseline and an optional selectable TypeSafe controller, where every decision can be inspected, held in teaching mode, saved, replayed and compared against the baseline.

See highlights

Open github.com

Stars: 0
Language: TypeScript
Published by: Community
Author: juancamiloqhz
Last verified: Oct 2026

juancamiloqhz/roverlab

User repository on GitHub

View on GitHub

A 3D planetary rover sandbox for experimenting with autonomous decisions using TypeSafe AI.

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

A browser-based planetary rover sandbox for experimenting with autonomous decisions using TypeSafe AI. Give a rover a mission, change its environment, and inspect how its choices affect exploration, energy use, and discoveries.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

The decision timeline shows the knowledge, resources, full candidate set and chosen action at each step; numbered map targets link back to it.
The baseline needs no key; the TypeSafe controller runs through a local Bun backend with Choice probabilities and attempt/latency accounting.
Failed inference gets explicit Retry and baseline continuation, and comparison records the baseline's alternative from a detached copy of the same input.
Teaching mode holds each controller choice before its action runs; mission edits and detected storms invalidate held choices.

Watch out

The README is a running log of numbered tickets under .scratch, so what you get depends on the build: early saved records keep their original five-minute conditions while the expanded world uses eighteen-minute expeditions, and versions 1 through 8 replay under their original rules with missing evidence shown as unavailable. The TypeSafe path is optional and needs your own key, the local Bun backend, and limits you set explicitly. The README states plainly that a different choice from the baseline does not establish a better expedition outcome, and that map inspection, teaching explanations and replay describe recorded route estimates rather than completed results or model reasoning. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

laya-server

Self-hosted Docker service and web UI that packages Laya structured-decision inference behind a compatible System One endpoint.