Claude God Tip #14: My Translation App Declared War on Claude Code
Published: December 10, 2025 - 4 min read
Welcome to another episode of Claude God tips! This one is quick but particularly useful for me because of a software clash I've been dealing with for months.
If you don't know what this series is about, I suggest checking out the blog post where I introduced it.
The Reverso Situation
I have this software called Reverso installed on my laptop. I installed it this past summer, and it's been a game changer for my French learning journey. I won't spend too much time talking about it since you can simply check it out yourself.
But here's the best thing about having Reverso on my computer: every time I need a word or sentence translated from French to English (or vice versa), I simply highlight the text and hit Ctrl+C+C. A small dialog box opens with the translation. Simple, fast, muscle memory.
If you've used Claude Code in the terminal, you can probably see where I'm going with this.
The Clash
To exit a Claude session in the terminal, the command is Ctrl+C+C. Yes, the exact same keyboard combination I use to open Reverso.
Now you can imagine the battle that ensues when I hit Ctrl+C+C. I see Reverso open up, but the Claude session doesn't terminate. I have to keep pressing Ctrl+C+C repeatedly until the session finally dies. It's annoying.
I know the quick fix: go to Reverso settings and change the keyboard combination for text translations to something else. But using Ctrl+C+C has become second nature for me. That's not an option.
So this blog post is about the different ways you can exit a Claude session without using the Ctrl+C+C keyboard combination.
Method 1: The /exit Slash Command
The first method is the /exit slash command. It's simple, fast, and a straightforward way to quit the running Claude session. Just type /exit and you're out.
I've talked about slash commands before, and since then I've written about a number of them:
- Tip #7: The /rewind command for disaster management
- Tip #10: The /config command for verbose output
- Tip #13: The /clear command for context window management
Method 2: The Ctrl+D+D Keyboard Combination
When Ctrl+C+C fails, try Ctrl+D+D.
This method is nice since you don't have to type anything. It's simply another keyboard combination that's also easy to remember when you consider that D could stand for "Die." When you hit that keyboard combination, you're telling the session to die. Twice. (It only listens after the second D is pressed though.)
Why am I going down this tangent? Anyways...
Method 3: The /clear Slash Command
The next two methods are more like reminders because we've seen them before.
In the previous Claude God tip, I talked about the /clear slash command. With /clear, you can exit the current session and automatically start a new session for the current project. No need to explicitly exit first.
Method 4: The /resume Slash Command
In the very first Claude God tip, I talked about using the --resume and --continue flags when starting a session. You should definitely check that out if you haven't.
Now I want to mention that there's a slash command equivalent to the --resume flag. You guessed it: /resume.
With /resume, you can juggle between multiple sessions without ever having to explicitly exit the current running session. It opens a session picker that lets you switch to any previous conversation in that project.
The Bigger Picture
Now that you know these four methods, do you see where I'm going with this?
- With /clear: Exit current session, automatically start fresh
- With /resume: Switch between sessions without exiting
You can play around with both to juggle between sessions and automatically start new ones. This way, you only ever use the exit commands when you're done programming for the day.
Quick Reference
| Method | Command | What It Does |
|---|---|---|
| Exit | /exit | Ends the session completely |
| Die twice | Ctrl+D+D | Keyboard shortcut to end session |
| Fresh start | /clear | Ends session, starts new one |
| Session hop | /resume | Switch to different session |
Wrapping Up
I hope this helps someone who's dealing with a similar software clash. Or even if you're not, having multiple ways to exit and manage sessions is always useful knowledge.
As always, thanks for reading!