Remote Work Through Discord: One Terminal, Another Input

I wanted the same session on my phone

I was using AI tools in a terminal on my Mac. Managing several SSH sessions from a phone or iPad was awkward. I asked AI to let me send commands and receive results through Discord while keeping the existing terminal available on the Mac.

The key condition was a shared session. Starting a separate AI conversation for each Discord interaction would not continue the work already underway. The extra input surface needed to reach the existing working session.

Receiving a message was only the first check

During implementation, AI reported a tmux targeting problem. The pane numbers—the identifiers for terminal areas within a window—did not match its assumption. The record describes a confusion between zero- and one-based pane targets and a change to make target identification more reliable.

Receiving a Discord message did not establish that the connection worked. The message also had to reach the intended terminal.

The request expanded to multiple channels. Each channel needed a defined session target, and I asked for documentation explaining how to add another channel later. That would preserve the setup steps beyond the first working connection.

Progress before the final response

After sending a remote command, waiting silently for a final response made it difficult to tell whether the job was running or stuck. I asked for intermediate progress visible in the AI CLI to be relayed through Discord too.

The target was status text actually displayed by the CLI, not access to a model’s private reasoning. AI reported implementing progress and completion indicators and restarting the bot.

The resulting end-to-end check would need to cover:

1. Sending a message from the phone.
2. Receiving it in the mapped working session.
3. Relaying progress displayed by the CLI.
4. Receiving the final response.
5. Returning after a disconnect and continuing the same work.

This is a description of the required user flow, not evidence that all five steps passed on a phone during the session.

Implementation reports and the remaining mobile test

The record includes syntax checks, tmux send-and-receive tests, and reports of bot login and restart. The final response asked me to try the actual Discord channel. The recorded endpoint was therefore implementation and startup, with the complete mobile test still outstanding.

AI built the connection and corrected the terminal target. I specified session continuity, multiple channels, progress messages, and documentation for adding connections. The acceptance question became whether I could continue the same work remotely, beyond merely sending a message.

This account uses records from February 24, 2026. Credentials and account and channel identifiers are omitted. I did not run the bot or send messages for this article, and the setup was not revalidated as a current installation guide.