The desktop app is built on the same agent you can read.

It runs the same engine as the terminal, so the app and the terminal share one agent. It is a development build today, and the browser app is not open yet.

Desktop: Development buildBrowser app: Not open yet

What the development build looks like

These are captures of the desktop development build, taken against a test fixture, so some names and text in them are placeholders. Details will change before a release.

The desktop app showing a session named Explain this codebase. A sub-agent is running, and a side panel lists the agent, one changed file, the git branch and a short activity log.
A session with a sub-agent running. The side panel keeps agents, changes and activity next to the conversation. Development build capture.
The desktop app asking Run a command? with the exact shell command shown and three buttons: Allow once, Allow for this conversation and Don't allow.
A command waits for your answer before it runs, with the exact command in view. Development build capture.
The desktop app's new session screen with the model picker open and filtered to two DeepSeek models, beside a thinking-level menu with Default, Off, Low, High and Max.
Choose a model and a thinking level before you start. Development build capture.

What works without an account, and what an account adds

The app does not ask you to sign in up front. Where a control needs an account, it says so beside that control. Sign-in is not available in every build yet.

Works without an account

Your folders and conversations
They stay on this computer, and signing out leaves them in place.
Your own models
Use your own model keys or a local model.
Plugins
Skills, connectors, hooks and the plugin bundles that carry them run on this computer with no sign-in.
The terminal and the local browser
Both are released and need no account.

What an account adds

Shared conversations
Share a conversation with other people.
Projects in your account
A project lives in your account instead of on one computer.
Cloud computers
Send work to a cloud computer. Cloud computers are invite-only.
Agents that keep going
Let an agent look after a repository on GitHub while you are away.

When sign-in is available and you have an account, the app opens your browser to finish signing in and then returns you to the app. Signing out leaves your folders, conversations and model keys in place. How sign-in works

Where Codewhale runs today

SurfaceStateWhat it means
TerminalReleasedInstall release binaries for Linux, macOS, or Windows; npm and Cargo also work, and Android on Termux is a preview. The interactive TUI and codewhale exec for scripts ship together. Install guide
Local browserReleasedRun codewhale web to open Codewhale in your browser. Read the conversation, send a task, and answer approvals on your machine. It comes with the terminal and needs no account. Local browser guide
Browser appNot open yetBeing rebuilt to match the desktop app, and not open yet. For a browser view today, run codewhale web on your machine.
DesktopDevelopment buildA desktop app on the same engine. Review changed files and commit them, and edit an earlier message to continue from it in a new conversation. No public download yet.
PhoneNot publicThe phone app is not available to the public yet.

Start with the terminal today.

The terminal and codewhale web run the same agent the desktop app is built on. The sign-in guide explains how accounts work.