# Remocode Troubleshooting Guide: Common Issues and Quick Fixes
Quick Reference for Common Problems
Every tool has hiccups. This guide covers the most frequently encountered Remocode issues and how to resolve them fast.
Telegram Connection Issues
Problem: Bot Not Responding
Symptoms: You send commands to your Telegram bot and get no response.
Solutions:
- ●Check that Remocode is running on your Mac. The bot needs the desktop app to relay commands.
- ●Verify your internet connection on both your Mac and phone.
- ●Go to Remocode Settings and check the Telegram bot status indicator. If it shows disconnected, click reconnect.
- ●Verify your bot token is correct. Regenerate it from BotFather on Telegram if needed and update it in Remocode settings.
Problem: Messages Delayed
Symptoms: Telegram messages arrive minutes late instead of instantly.
Solutions:
- ●Check your Mac's internet latency. Slow connections cause relay delays.
- ●Ensure Remocode isn't being throttled by macOS energy management. Keep the app in the foreground or disable App Nap for Remocode in System Settings.
- ●Check Telegram's server status — occasionally Telegram itself has delays.
Problem: via Session Shows No Output
Symptoms: You start a via session but see no terminal output in Telegram.
Solutions:
- ●Make sure you're using the correct tab name. Tab names are case-sensitive.
- ●Check that the terminal tab actually has an active process. An idle terminal produces no output.
- ●Disconnect and reconnect the
viasession.
AI Agent Detection Issues
Problem: Agent Not Auto-Detected
Symptoms: You launch Claude Code or Gemini CLI but Remocode doesn't enable smart features.
Solutions:
- ●Ensure you're launching the agent from within a Remocode terminal tab, not an external terminal.
- ●Some agents need a moment after startup to be recognized. Wait 5-10 seconds after launching.
- ●Check that your AI agent is up to date. Remocode detects agents based on their output patterns, which can change with updates.
- ●Restart the terminal tab and relaunch the agent.
Problem: Questions Not Being Forwarded
Symptoms: Your AI agent asks questions in the terminal, but they don't appear in Telegram.
Solutions:
- ●Confirm that question forwarding is enabled in Remocode settings.
- ●Ensure the Telegram connection is active (see connection troubleshooting above).
- ●Some questions may not match Remocode's detection patterns. Use
viafor a live session if auto-forwarding misses a question.
Performance Issues
Problem: Remocode Feels Sluggish
Symptoms: Terminal input is laggy, panes resize slowly, or the app stutters.
Solutions:
- ●Close unused terminal tabs. Each tab runs a separate node-pty process.
- ●Clear terminal scrollback in tabs with excessive output. Very long scrollback buffers consume memory.
- ●Check Activity Monitor for overall system resource usage. Running multiple AI agents simultaneously is CPU-intensive.
- ●Restart Remocode to clear any memory leaks.
Problem: High Memory Usage
Symptoms: Remocode uses over 1GB of RAM.
Solutions:
- ●Reduce the number of open terminal tabs to those you actively need.
- ●Close the AI assistant panel when not in use.
- ●AI agents themselves use significant memory independently of Remocode. Check if the agents are the actual memory consumers.
AI Assistant Panel Issues
Problem: Panel Shows No Response
Symptoms: You send a message in the AI panel but get no reply.
Solutions:
- ●Check that you've configured at least one AI provider with a valid API key in Settings.
- ●Verify the selected provider's API is accessible. Try the provider's web interface to confirm.
- ●Check your API key hasn't expired or run out of credits.
Problem: Wrong Provider Responding
Symptoms: You expected one AI model but got responses from a different one.
Solutions:
- ●Check the provider selector in the AI panel. Make sure the correct provider is selected.
- ●If you recently changed providers, the panel may need to be closed and reopened.
Terminal Issues
Problem: Terminal Output is Garbled
Symptoms: Strange characters, broken formatting, or missing colors in terminal output.
Solutions:
- ●Ensure your shell is set to use UTF-8 encoding.
- ●Check that the terminal font supports the characters being displayed.
- ●Some CLI tools output control sequences that xterm.js handles differently than native terminals. This is rare but can happen with highly customized prompts.
Dangerous Command Filter Issues
Problem: False Positives
Symptoms: The dangerous command filter alerts on commands that are safe.
Solutions:
- ●Review the alert and proceed if you're confident the command is safe.
- ●The filter is intentionally cautious. False positives are better than missed dangerous commands.
Still Stuck?
If none of these solutions resolve your issue, check the Remocode community channels for help. Include your macOS version, Remocode version, and a description of the steps to reproduce the problem.
Ready to try Remocode?
Start with a 7-day Pro trial — no credit card required. Download now and start coding with AI from anywhere.
Download Remocodefor macOS