Developer assistant

The work stays visible.

Supen is for complex projects and professional documents. The official CLI stays on your computer. You open that same session from a phone, tablet, or browser, see where it stopped, and take over when you choose. The assistant carries the goal and brings you back only when a decision, a checkable result, or a change to that goal needs you.

Open the terminal

Web and PWA. The computer connects out on its own. Herdr is the first terminal.

Decision needed

Concept of the first scene: the official CLI, and the reminder that opens it.

Same session.

Discovery, history, live output, native confirmation, and unsent drafts come from the official CLI on that computer. Opening the session shows it. Takeover and release follow the real input permission.

Three reasons to come back.

A decision is needed.The native prompt is still waiting.

A result can be checked.The completion standard can be opened.

A change affects the goal.Something moved the work you are in.

The work thread is the one you open.

The assistant's own session stays behind the work, for understanding and checking. You open the ordinary Codex thread. The plan, the execution, and the stage results stay with that thread.

Now.

Terminal firstThe first release is this remote terminal.

Same standard laterFiles, previews, and the dev-server view follow it.

Assistant afterThe assistant follows once the terminal is accepted and released. Public-network browser acceptance is still open.