The workspace

The screen most people use. A conversation, a live preview beside it, and every goal this project has had — with the whole engine one button away when you want it.

What a project looks like by default#

Deliberately simple. Most of the time the interesting thing is what got built, not which agent built it.

Say what you want
Type it, or speak it. No form, no fields, no ticket template — a sentence is the input.
The preview, docked
The running app beside the conversation rather than in a second browser tab, so a change and its result are on one screen.
Every goal, and how it ended
The history of the project: what was asked, what shipped, and what stopped. Clicking one reopens it in full.
The build, task by task
Each task being built is a card with its own progress bar, and each finished task says what you can try. Nothing waits for you to approve it.

And the whole engine, on demand#

One button — Watch goal while it is running, View execution once it has finished — opens what Tharas actually did. It is the same panel for a live goal and one from last week.

  1. 01Agent floorWho is working, on what, right now.
  2. 02TimelineTimestamp, agent, event, status — what happened, in order.
  3. 03VerificationWhat was tested and what it proved.
  4. 04Model activityThe raw calls underneath, behind an expander.

Transparency you can open, not transparency you must read

The execution panel is a differentiator and it is not the default screen. Somebody who only wants a working app should never have to read a build log to get one — and somebody who wants to know exactly which model changed which file is one click from all of it.

The same screen in three places#

The workspace is one implementation. The browser opens it, the desktop app opens it in its own window already signed in, and the phone renders it inside the native shell. That is not a claim about consistency of design — it is the same code, so a control cannot exist in one of them and be missing from another.

Common questions

Is my code uploaded to render this?

The workspace shows what the engine reports — goals, plans, timelines, previews and outcomes. Where the work itself runs depends on the project: on your own machine, or on a hosted worker you asked for.

Can I work on several projects at once?

Yes — each project is its own workspace, with its own conversation, preview and history.

SurfacesThe desktop appInstall it, sign in once, and your machine can build — with the workspace in a window and a tray icon that says what is happening.SurfacesThe phoneNothing stops while you are away from a desk — nothing waits for a yes. The phone is how you see what got built, and say what to build next, from wherever you are.GuidesWatch a buildYou say what you want and Tharas starts. There is nothing to approve along the way — this is what the screen shows instead, and what each part of it means.