Skip to content

Scelo TUI

scelo tui: soft data to tools to hard data, in your terminal

The three-pane Scelo workstation in a terminal. Drop a file in and the agent profiles it, cleans it to a fixed point, reads it, picks an analysis and runs it. You steer what it decided from chat. The whole session exports to Python, Jupyter, R, Excel and the Scelo IDE in one command.

Before you start

Scelo TUI installs from source rather than from a release, the analysis menu is eight entries against the IDE's thirty, and there is no session persistence. See Limits for the full list.

What you are looking at

The whole product is one screen. Left is the data, middle is what the agent decided, right is the result. Each pane has its own chat box at the bottom.

tab pane · drag to select+copy · ⏎ send (or paste a path) · ↑↓ history · /copy values · /help commands · ctrl-e export · ctrl-o model · ctrl-c quit

Colour is the one thing here that is ours. The terminal draws this in ANSI; the panes are tinted to the site palette so that this screen and the demo on the marketing site agree about what each stage looks like.

Every screen on this site is a real capture of the running program, not a mock-up.

The idea

Chat does not start work. Dropping a file does. The agent ingests, cleans, reads, picks and runs without being asked, and fills the panes as each stage lands. The bots exist to change what it decided, which is why every pane states what was done and why it was done.

That inverts the usual chat tool, where nothing happens until you compose a good enough prompt. Here the useful default has already run by the time you have finished reading the file name.

Sixty seconds

scelo policies.csv

Pick a model, press Enter, and the panes fill. Then:

you type what happens
/list the analyses that apply to this data, numbered
/run 5 switch to that one, the HARD pane re-renders
/charts every plot this data makes, full screen
/export six files: cleaned CSV, pandas, Jupyter, R, Excel, .sce
/live mirror the session into RStudio and Jupyter as it runs

Nothing above needs a model. Slash commands are actions rather than conversation, and they keep working when the model is unreachable.

Where to go next

  • Install

    Two repos side by side, bun install, bun link. No build step.

  • First run

    The model picker, then dropping a file in.

  • The three panes

    What each one shows and why it says what it says.

  • Export

    Six artifacts, and how they are verified against the pane.