Overview
This is the desktop client rather than the browser tab, and the difference shows up in the small things. It sits behind a global hotkey, so a question is one keystroke away from whatever you are already doing, and it can take a region screenshot of the current window and hand that straight into the conversation without a save and upload round trip. Files dragged onto the window are read in place, which covers documents, spreadsheets, source files and plain text logs, and the reply keeps a reference to what it read so you can scroll back and check.
The Classic build is the one people ask for by name because it kept the older conversation layout, one window, one thread list on the left, no side panels sliding in over the text. It is the same underlying client as the current release, just with the interface changes reverted and the newer promotional surfaces stripped out. The repack removes the account gate on launch, so the client opens straight into a usable window with the tier restrictions on model choice, attachment size and thread history lifted.
What the desktop client does that the browser does not
The screenshot path is the feature that earns the install. Press the capture hotkey, drag a box over anything on screen, and the image lands in the composer with the cursor already waiting after it. That covers reading an error dialog, transcribing a table out of a document that will not let you select text, and asking why a chart looks wrong, all without leaving the application you were in.
File handling is the other half. Drop a folder of text files and the client queues them as one context rather than making you paste each in turn. Long documents are chunked in the background and the client tells you which parts it actually used, which matters when the answer is wrong and you need to work out whether it read the right section. Threads are stored locally in this build, so the history survives being offline and does not sync anywhere.
The Classic layout
The current client moved to a multi pane layout with a persistent side rail, inline suggestion cards above the composer, and a model switcher that hides itself when the window is narrow. Classic keeps none of that. There is a thread list, a conversation, and a composer, and the model switcher is a plain dropdown that stays where you left it.
Typography is the part that most people notice second. Classic renders replies at a larger default size with wider line spacing, and code blocks keep the older monospaced treatment with a copy button in the corner rather than a hover toolbar. Markdown tables render as tables, long lists do not collapse themselves after ten items, and the reply text can be selected across message boundaries, which the newer layout broke.
Practical notes on running it
The client is not a local model. It talks to a hosted endpoint, which means the machine needs a connection for a reply to come back, and it means replies are as fast as your line is. Nothing here changes that. What the repack changes is the gate in front of the window: there is no sign in step, no tier check on the model dropdown, and no upgrade panel wedged into the thread list.
Memory use is modest for a client of this kind, around 400 MB with a few threads open, rising when a long document is loaded into context. It parks in the tray when closed so the hotkey keeps working. If you would rather it did not, the tray behaviour is a single toggle in settings and the client exits properly with it off.
What you get
- Global hotkey that opens the composer over any application
- Region screenshot capture that drops straight into the conversation
- Drag and drop file reading for documents, sheets, code and logs
- Classic single window layout with the older thread list restored
- Local thread storage with no account attached
- Model dropdown with the tier restrictions lifted
- Markdown, table and code block rendering with per block copy
- Voice input with local push to talk rather than a hosted trigger
- Tray mode that can be turned off for a clean exit
Inside the archive
- ChatGPT Classic desktop client, offline installer
- Hotkey and capture helper component
- Interface language packs for the list shown above
- Readme covering the first launch behaviour of this repack
System requirements
| Operating system | Windows 10 version 21H2 or Windows 11, 64-bit |
|---|---|
| Processor | Any dual core 2 GHz or faster |
| Memory | 4 GB minimum, 8 GB recommended |
| Graphics | No dedicated card required |
| Storage | 2 GB free |
| Network | Broadband connection required for replies |
Installing it
- Unpack the archive to a local folder.
- Turn off real time protection first, since the launch gate is patched and scanners read that as tampering.
- Run the setup executable as administrator.
- Launch the client once. It opens straight into the window with no sign in step.
- Set your capture hotkey in settings before you close it, since the default may collide with a screenshot tool you already run.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | North America | No wait, resumable | Online |
| Torrent magnet | Global | Optional, file is small | Online |
Release history
- Fixed the capture overlay appearing on the wrong monitor in mixed scaling setups
- Thread search now covers attachment contents
- Reduced idle memory use in tray mode
- Classic composer restored after the layout change in the mainline client
- Fixed code blocks losing indentation when copied
- Local thread storage moved off the sync path entirely
- Drag and drop accepts folders rather than single files only
Questions about this release
Does this run a model on my own machine?
No. The client is an interface to a hosted endpoint, so it needs a connection to answer. The repack removes the account gate, not the network requirement.
Why is it called Classic?
It keeps the older single window layout that was replaced in the mainline client. The engine behind it is the same.
Are my threads uploaded anywhere?
Thread history in this build is written to a local store and the sync component is removed, so the list stays on the machine.
Will it update itself?
The updater is stripped out. The build stays at the version you installed until you replace it.
Comments
Classic layout is exactly as I remember it. No side panel sliding over the text mid answer.
Opens with no sign in. Threads stay local, checked the folder myself.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
The screenshot hotkey alone is worth it. Grab an error box, ask what it means, done.