1 of 11

EVO IDE

The Only Coding AI That Lets You Watch It Think.

Live reasoning. Live telemetry. Nothing hidden in a black box.

PROTOTYPE · IN ACTIVE DEVELOPMENT

2 of 11

AI Coding Tools Are Black Boxes

No visibility

You see the final code, never the reasoning that produced it.

Cloud-only by default

Your prompts and files leave your machine with no alternative.

Fragmented output

Multi-file patches you have to stitch together yourself.

No sense of "health"

No signal for whether a generation is going well until it fails.

What if the IDE showed its work?

Not just a wall of prose reasoning -- actual live signals: token velocity, syntax validity, whether code fences are closed, how the generation is trending, all while it’s still writing.

EVO IDE

2

3 of 11

Meet Evo IDE

Five things that make it genuinely different today.

Reason First

A live <think> trace streams before any code is written

Monolithic Output

One complete file per turn -- never a stub

Live Telemetry

Watch velocity, health, and token counts as it works

Sandboxed

Jailed writes, atomic saves, timestamped backups

Local or API

Run fully offline, or connect a hosted model

EVO IDE

3

4 of 11

It Reasons Before It Writes

Every turn streams a live reasoning trace inside a <think> block -- visible in its own Reasoning tab, before code appears.

The reasoning stream survives a tag torn across chunk boundaries

A turn with no reasoning at all is flagged, not silently accepted

You can read the model’s plan before its code ever touches a file

<think>�The user wants a web scraper for a�product listing page. I should check�for pagination before assuming a�single page holds every item, and�use a session so headers persist�across requests.�</think>��File: scraper.py

EVO IDE

4

5 of 11

1

FILE PER TURN

no stubs, no elisions

One Prompt. One Complete File.

A second file in one turn is treated as a violation, not a style choice

Placeholder markers like "...rest unchanged..." are rejected outright

What you get back is a whole, runnable file -- not a diff you have to reassemble

EVO IDE

5

6 of 11

Watch It Think, Not Just Read About It

A live telemetry panel runs alongside every generation -- pulled straight from the running app.

VELOCITY

tok/s

live while streaming

peak

highest burst

ttft

time to first token

avg

session average

TOKEN VELOCITY

think / code split

Separately tracked -- so you can see how much time goes to planning versus producing the actual file.

think

code

elapsed

HEALTH

Syntax valid

Fences closed

Frame count

Loss trend

A single glance tells you whether a generation is trending healthy -- before it finishes.

EVO IDE

6

7 of 11

Every Write Is Jailed. Every Save Is Backed Up.

Jailed writes

Absolute paths and directory traversal are rejected outright.

Atomic saves

Temp file + replace -- never a half-written file on disk.

Timestamped backups

Every overwrite leaves a recoverable copy behind.

Opt-in execution

Nothing runs automatically -- you choose when code executes.

EVO IDE

7

8 of 11

Run It Local. Or Connect an API.

The backend is a choice, not a lock-in.

LOCAL

Point it at a local Ollama daemon and nothing you write ever leaves the machine.

Fully offline · no API key · no usage sent anywhere

API

Or connect a hosted model over an API when you want more horsepower than your machine offers.

Same interface, same telemetry, same safety rails -- only the backend changes

EVO IDE

8

9 of 11

What You Can Build With It

One line in. One working file out.

Web scraper

"scrape this product page and export to CSV"

A full website

"build a landing page for a coffee shop"

CLI tool

"build a csv → sqlite loader with a CLI"

API client

"write a client for this REST API"

Data pipeline

"parse these logs and summarize errors"

Automation script

"rename and organize files by date"

EVO IDE

9

10 of 11

Where It Stands Today

An honest split between what’s working now and what’s still being built.

WORKING TODAY

Live reasoning trace (<think>)

Monolithic single-file output

Live telemetry panel

Sandboxed, jailed, backed-up writes

Local + API-connected backends

IN DEVELOPMENT

Self-repair on traceback (not yet reliable)

Multi-file project awareness

Broader template library

Plugin / tooling ecosystem

EVO IDE

10

11 of 11

EVO IDE

Reason visibly. Build monolithically. Stay in your control.

A WORKING PROTOTYPE, BUILT IN THE OPEN

EVO IDE

11