Software Development

Four surfaces,
one session

Start a task at your desk, keep an eye on it from your phone, and take it over in an editor. It is the same conversation throughout.

TUI

The terminal agent

Early access

A chat interface that lives in your terminal and does work rather than describing it. It reads and writes files, runs commands, and reports back with every action visible.

■Reads and edits files in place
■Runs terminal commands and shows the output
■Every tool call is visible in the transcript
■Bring your own model provider

View TUI ➔

GUI

The desktop app

Early access

The same session with a window around it — for when you want the transcript, the file tree, and a diff view side by side instead of stacked in a terminal.

■Same session as the TUI, not a separate one
■Diff and file views alongside the conversation
■Runs locally on your machine

View GUI ➔

IDE

The editor

In development

A full editor with the assistant built in, so you can write code by hand and hand a task to the agent without leaving the file you are in.

■Editor with the assistant built in
■Hand a task over from the file you are editing
■Shares context with the TUI and GUI

View IDE ➔

Mobile

The session in your pocket

Early access

A phone client that connects to a session already running on your machine. Check on a long task, read what the agent did, and send a follow-up from wherever you are.

■Connects to a running TUI or GUI session
■Read the transcript and send new messages
■Built for checking in, not for typing a codebase

View Mobile ➔

Why four tools and not one

Because the right place to work changes through the day. A terminal is the fastest way to hand over a task; a desktop window is better for reviewing what came back; an editor is where you want to be when writing the code yourself; and a phone is all you have when the build is still running and you are not at your desk. One session, four ways in.

The engine underneath

NIRA

The four tools above are surfaces. NIRA is what runs underneath all of them — the agent loop, the toolset, and the accumulated knowledge that turns a request into work actually done.

It is what reads the file, runs the command, and decides what to do next. Every surface talks to the same NIRA, which is why a task started in the terminal can be finished in the editor without anything being explained twice.

■ The agent loop — plan, act, observe, repeat
■ 25+ built-in tools it can call
■ Provider-agnostic: bring your own model
■ Shared across every surface, one session

Learn more

Also see: Electronic Design and Mechanical Design.

Electronic Design Mechanical Design