FAQ

I restarted my machine and Cmd+Ctrl is not connected. What do I do?

Daemons don't start automatically after a reboot unless you've set up auto-start. Run the start script to bring all your registered daemons back online at once:

curl -fsSL https://docs.cmd-ctrl.ai/start.sh | bash

To avoid this in the future, see Auto-Start for launchd (macOS) and systemd (Linux) setup.

Does my development machine need to stay on?

Yes. Cmd+Ctrl's daemon runs on the same machine as your coding agent and connects to the server over the internet. If your machine goes to sleep, loses connectivity, or shuts down, you won't be able to send messages or receive updates until it's back online.

Can I close the Claude Code CLI and keep working from the Cmd+Ctrl app?

Yes. You can close the terminal and continue the conversation from the web or mobile app. The daemon keeps running independently. When you want to return to the CLI, use claude -c or claude -r to pick up where you left off.

Does Cursor or VS Code need to be running?

Yes, if you're using Cmd+Ctrl with an IDE-based coding agent. The IDE must be running with --remote-debugging-port enabled so the daemon can communicate with it. See the Cursor or VS Code Copilot installation guides for setup details.

Does Cmd+Ctrl work with Claude Code in the Claude desktop app?

Yes. Claude Code in the desktop app talks directly to your Claude Code on your command line, and it's through that local connection that Cmd+Ctrl works.

Does Cmd+Ctrl work with Claude Code on the web?

No — Claude Code on claude.ai runs in ephemeral cloud VMs. It's not until you teleport the conversation into your local Claude Code that Cmd+Ctrl can work with it.

Does Cmd+Ctrl work with the Claude Code VS Code extension?

Yes, the same way as the CLI. The daemon runs on your machine alongside your code – it doesn't matter whether Claude Code is invoked from a terminal or from the VS Code extension. Just install the daemon and it works with both.

Why can't I respond to Claude Code's plan-mode or permission prompts from Cmd+Ctrl?

Claude Code sometimes pauses to ask for input – plan approval, clarifying questions, or permission to run a tool. These interactive prompts are part of Claude Code's CLI and are not accessible to Cmd+Ctrl. You'll see the plan content and agent activity in Cmd+Ctrl, but the prompt waiting for your response only appears in the terminal.

You can still reply via Cmd+Ctrl and the agent will continue, but you may not see every prompt it's waiting on.

My Claude Code CLI session doesn't show messages I sent from Cmd+Ctrl. What do I do?

Claude Code CLI sessions don't pick up messages sent outside the CLI until you exit and resume. Use claude -c or claude -r from the command line, or /resume from within the Claude Code prompt.

How do I report a bug?

Open an issue on GitHub or email [email protected].

How do I delete my account?

Open the app and go to Settings → Account → Delete Account. You'll be asked to confirm twice before anything is deleted. Deletion is immediate and permanent – your account credentials, session metadata, notification preferences, push tokens, and device registrations are removed right away. See our Privacy Policy for details.