Claudette

Claude Code, in a real desktop window

Every session in a tab.
Every change in sight.

Claudette runs the real Claude Code, with your settings, CLAUDE.md, MCP servers and hooks, and draws it as a native app: a tab for each session, every change ready to review, and your plan's usage on screen the whole time.

Needs Claude Code · Windows 10 and 11, macOS 12 or later, Linux on x64 · Every package

Claudette's window: seven tabs over three game projects in the sidebar, a C++ conversation with tool calls and a code block, the Changed files page in the side panel, the plan's usage in the header, and Claudette herself standing on the message box

For game developers

Made by game developers.
For game developers.

Claudette knows the engines, editors and depots games are made with. Open a project's folder, and its tab knows what's in it: the engine and its version, how to build and launch it, and where the editor writes its log.

Unreal Engine

UE 4 and 5, from the launcher or built from source

  • Launch the editor, generate project files and build, in Development or DebugGame
  • Open the solution, or the project in Rider
  • Its log in tidy columns of time, category and verbosity
Unreal Engine

Unity

The exact editor the project names, found through Unity Hub

  • Open the project, with Release or Debug code optimization
  • Run the EditMode tests, and see how many passed
  • Regenerate the C# solution, and clean Library when it's time
Unity

Godot

Godot 3 and 4, C# projects too

  • Open the editor, or run the main scene
  • Build C# with dotnet, and open the solution
  • Clean .godot, or Godot 3's .import, for a fresh import
Godot

See it in action

Everything Claude does,
where you can see it.

From the first message to the last diff. Scroll through a day with Claudette.

01 Tabs and sessions

A dozen sessions.
Not one lost.

Every session gets a tab, grouped by project in a sidebar that shows each one's status, branch, model and context at a glance. Mark tabs your way, and press Ctrl/Cmd+J for the next one waiting for you. Fold a busy tab's sub-threads, subagents and logs away under it.

Tabs and sessions
The sidebar: three project groups and seven tabs, each with its status, model and effort, git branch and context ring, a thread with its two sub-threads, and the Studio account's tag

02 Plans, tasks and threads

Big jobs.
Shared out.

Follow Claude's plan as it writes it, with every version, and watch each task get done: who's on it, how long it took and what it changed. Make a tab a thread, and its Claude hands work to the other tabs in its project, with one report back.

Threads
A thread moving a Unity game to the Input System: its two sub-threads under it in the sidebar, the plan it approved with Changes from v1, and its tasks two of seven done

03 The agent map

See every agent
at work.

The agent map draws Claude's subagents as a tree while they fan out, nested as they nest, with what each is doing right now. Select one for what it was asked and what it returned, or stop it.

The agent map
The agent map: three Explore subagents that surveyed the project in parallel, the first selected with its prompt and its report

04 Usage and limits

Know your plan.
Before it runs out.

Live meters for the session and the week, a projection of where you'll land, and alerts before you hit a limit. If you do hit one mid-task, the tab waits for the reset and carries on by itself.

Usage and limits
The detailed usage header: the session chart heading for 90% just before the reset, the week with a model's own line, the burn rate per hour and the busiest tabs

05 Reviewing changes

Every change.
Reviewed.

Every file the session touched, with a real diff view, Revert for a hunk or the whole file, and ticks that stick until Claude edits the file again. Or send the diff to Beyond Compare, VS Code or your own tool.

Reviewing changes
The diff view of StarfallCharacter.cpp: the include, the air control change and the grappling hook's component Claude added

06 Project files

The code,
beside the conversation.

A project's files in a tab of their own, with an explorer and an editor. Claude's changes are marked in the gutter, with a peek at what was there. Click a file Claude names, and it opens at the line.

Project files
A project's Files tab: the explorer with the files Claude changed marked, and StarfallCharacter.cpp open in the editor with Claude's changes in the gutter

07 Editor logs

The editor's log.
Right under the tab.

While Unreal, Unity or Godot has the project open, its log is a row under the tab, followed as it's written, with its errors and warnings counted. Filter it by level, category or text, click a file it names to open it, and when the editor crashes, the log stays to say why.

Editor logs
The Unreal editor's log under the Grappling hook tab and shown in the main area: a chip for each level with its count, then the log in columns of time, category, verbosity and message, with an error in red and warnings in amber

08 Accounts

Your plan for yours.
Their key for theirs.

Run a client's projects on their API key and everything else on your own plan. The key stays in your OS's credential store, and the header shows what it's spending today, this week and this month.

Accounts
A tab on the Studio API key: the header shows Studio's estimated spend today, this week and this month, and Studio's tag marks its group and tab

09 History and syncing

Pick up
anywhere.

Search every past session, Claude's replies too. Carry a conversation to your other computer through a folder Dropbox, Google Drive or OneDrive keeps in sync, or keep it going from your phone with the Claude app.

History and syncing
History narrowed to the starfall project by its chip: its open tabs' sessions and older ones, one from a worktree

10 Settings

Settings that say
what they do.

Each setting has a line saying what it does, and the search finds it by what you'd call it. Changes apply as you make them, and Appearance shows them in a preview. Settings stays open beside your work, so you can see what a change does, and each section resets on its own.

The Settings window
Settings on Appearance: its pages in groups down the left, and a preview of a message, thinking and a reply in the chosen style above the Look, Text, Accessibility and Claudette sections

Make it yours

Two looks.
Light and dark.

Standard is dense and calm, in your OS's accent color. Claude takes after the Claude apps, with warm colors, rounder cards and a serif for replies. Both follow your system, or not.

The Standard style
Standard
The Claude style
Claude

Styles and themes

Meet Claudette

She keeps you
company.

Claudette stands on the message box while you work. She reads along with a magnifying glass, hammers while Claude edits, juggles a ball for each subagent, waves when Claude needs you, and throws confetti when the task list is done.

Poke her and drag her about, and play her at tic-tac-toe while a usage limit resets. She stands still if you reduce motion, and Settings can turn her off.

Claudette on the composer
Claudette climbing up onto the message box, then dancing, tossing a ball, sitting on the edge, juggling, hammering, bursting into confetti, twirling, blowing a heart and falling off behind the box to climb back up

And the rest

Made for the way you work.

Where it runs

Windows, macOS, Linux.
Same Claudette.

One Claudette for all three, built and tested on each with every change. Your tabs, settings and shortcuts work the same on every one, and your sessions and settings can follow you from one to another.

Windows

Windows 10 and 11, on x64 and Arm64

  • A signed MSIX that installs in a click and keeps itself up to date
  • Claude Code's settings and sign-in shared with the claude in your terminal
  • Toasts, a badge and a flash on the taskbar, and your folders in its jump list
Installing on Windows

macOS

macOS 12 or later, on Apple silicon and Intel

  • A signed, notarized .dmg, and an app that keeps itself up to date
  • A menu bar, and a badge on the Dock icon, where Claudette types, waves and waits
  • Your login shell's PATH, so Homebrew's tools are found from the Dock
Installing on macOS

Linux

Built from source, on x64, under X11 or Wayland

  • Tested with every change, the only system where the tests drive the real Claude Code
  • New commits on main pulled, built and restarted into, with your tabs kept
  • Notifications, the Secret Service for keys and systemd-inhibit to stay awake
Installing on Linux
Claudette on Linux, from nothing
# Claude Code
curl -fsSL https://claude.ai/install.sh | bash
# Claudette's source, and the .NET SDK it names
git clone https://github.com/dotBunny/Claudette.git ~/Claudette && cd ~/Claudette
curl -fsSL https://dot.net/v1/dotnet-install.sh | bash -s -- --jsonfile global.json --install-dir ~/.dotnet
export PATH="$HOME/.dotnet:$PATH"
# Build it and run it
dotnet run --project src/Claudette.App -c Release

Then keep .NET on your PATH and put Claudette in your app menu: Installing on Linux takes you through it.

What differs on each system

Your next session starts here.

Install Claude Code. Download Claudette. Open a folder.