Alien Desk

Guides

What to do when a Claude Code conversation gets too long

Long Claude Code conversations get summarized again and again, and details fade. Here is what compacting does, what starting over loses, and how to carry your work into a fresh conversation with a note you can read.

Work on one thing in Claude Code for a few days and the conversation gets long. Nothing breaks. Claude just starts asking about things you settled yesterday, or brings back an approach you already dropped.

What Claude Code does on its own

When a conversation no longer fits, Claude Code summarizes the earlier part and keeps going. This is compacting. It happens automatically, and you can also run /compact yourself.

It works, and most of the time you do not notice it. But each summary is a summary of a summary. Which of your decisions made it through, and which did not, is hard to see from where you sit.

The other built-in choice is /clear: a new, empty conversation. Nothing fades because nothing comes along. You explain everything again.

The middle path: a handoff note

What people do by hand is ask Claude to write down where things stand, start a new conversation, and paste that in. It is the right idea. It also takes a few minutes, and the note is only as good as the request you typed that day.

Alien Desk's Warp does this in one click, from the tab's … menu:

It takes about 30 seconds to a minute.

What goes into the note

The note always has the same ten parts, in this order:

Two rules matter most. A decision counts as yours only if you said it in your own words; an idea you floated, or something Claude recommended, is written down as open. And names and numbers are copied as they appear, not rewritten.

The note is written in the language you were using.

Why the new Claude speaks first and waits

A note can be out of date the moment it is written. So the first request in the new conversation asks Claude to read the note, check it against the actual files, say what it picked up and what it plans to do next, point out anything that does not match, and then stop.

In our tests this was the part that mattered most. In one conversation the note said the next step was to upload a build. The new Claude read the project's own records, found the build had already been submitted, and said it would not do that step. If you answer only "go ahead", it does the first step that needs no approval and nothing more.

What stays and what changes

When Alien Desk suggests it

Warp never runs by itself. After a conversation has been compacted three times, the alien on that tab asks once whether you want to warp. Say no and it does not ask again for that conversation. Across our own 88 conversations, one had reached that point.

You can warp at any time from the menu, for example right after finishing one piece of work and before starting the next.

How we tested it

Limits

Questions people ask

**Isn't this just /compact?** Same root: both summarize. Compacting keeps you in the same conversation with a summary you do not see. Warp starts a new conversation with a note you can open, at a moment you choose, and the new Claude checks the note against your files before it does anything.

Does Claude forget everything else? It starts from the note, your project's files, and your own instruction files such as CLAUDE.md. It does not see the old conversation.

Can I go back? Yes. The old conversation is untouched.

More guides