Creating Custom Telegram Commands for AI Terminal Analysis

Beyond Built-In Commands

Remocode's built-in commands — via, status, reply, peek, submit, audit — cover the core remote workflow. But every developer has unique needs. Custom commands let you define your own AI-powered analysis operations that run against terminal buffer content.

What Custom Commands Do

A custom command triggers an AI analysis of the terminal buffer with a prompt you define. When you send the custom command via Telegram, Remocode captures the current terminal content and passes it to the AI along with your custom prompt. The AI's response is sent back to your Telegram chat.

This is similar to status (which generates a progress report) and audit (which checks for security issues), but with a prompt you control entirely.

Use Cases for Custom Commands

Code Review Summary — Define a command that asks the AI to summarize all code changes visible in the terminal output, highlighting potential issues.

Dependency Check — Create a command that examines terminal output for dependency-related messages and flags version conflicts, deprecated packages, or security vulnerabilities.

Task Progress Tracker — Define a command that maps terminal activity against a task list and reports which items are complete, in progress, or blocked.

Error Categorization — Create a command that collects all errors from the terminal output, categorizes them by type (syntax, runtime, network, permission), and suggests fixes.

Performance Analysis — Define a command that looks for timing information, benchmark results, or performance metrics in the terminal output and summarizes trends.

How Custom Commands Work

Custom commands operate by combining your defined prompt with the terminal buffer content and sending both to an AI model for analysis. The key components are:

• ●Command trigger — The word or phrase you type in Telegram to invoke the command.
• ●Analysis prompt — The instruction that tells the AI what to look for and how to format its response.
• ●Terminal buffer — The raw content from the terminal session, automatically captured by Remocode.

When you send the command trigger, Remocode assembles these pieces and returns the AI's analysis to your Telegram chat.

Designing Effective Prompts

The quality of custom command output depends heavily on your prompt design. Tips for effective prompts:

Be specific about output format. Instead of "analyze the errors," write "list each error with its type, line reference if available, and a one-sentence suggested fix."

Specify what to ignore. Terminal buffers contain a lot of noise — status bars, progress indicators, ANSI artifacts. Tell the AI to focus on substantive output and ignore formatting artifacts.

Set a scope. If you only care about recent output, say "analyze the last 50 lines of output" or "focus on output from the most recent command execution."

Request actionable output. End your prompt with a request for specific next steps or recommendations, not just observations.

Custom Commands vs. Other Features

When should you use a custom command versus built-in features?

• ●Need real-time interaction? Use via mode.
• ●Need a general progress update? Use status.
• ●Need raw AI responses? Use reply.
• ●Need a specific, repeatable analysis? Create a custom command.

Custom commands shine when you find yourself repeatedly asking the same type of question about different terminal sessions. Instead of entering via mode, reading the output, and forming your own analysis each time, define the analysis once and invoke it with a single word.

Practical Example

Suppose you frequently want to know whether your AI agent has introduced any TODO comments in newly generated code. You define a custom command with a prompt like: "Examine the terminal output for any code that contains TODO, FIXME, HACK, or XXX comments. List each occurrence with the file name and the comment text. If none are found, state that clearly."

Now, whenever you want to check for TODOs, you send that command to your Telegram bot and get a focused report. No scrolling through output, no entering via mode, no manual searching.

Custom commands transform Remocode from a fixed tool into a customizable platform that adapts to your specific development workflow and monitoring needs.