Aily

Start in the terminal. Continue from anywhere.

Your AI agents run in tmux — aily bridges them to Discord and Slack so you can pick up right where you left off, without switching back to the terminal.

English | 한국어

Quickstart for Agents

Quick Start
Prerequisites: bash, curl, jq, tmux, python3 — Node.js only needed for npm install method.

aily init walks you through everything:

$ aily init — wizard output

Manual Install

Prerequisites: macOS or Linux, bash, curl, jq, tmux, python3, SSH key-based access to target hosts. Node.js only needed for npm method.

CLI Reference

What Happens After Setup

Once installed, aily works automatically in the background:

- Agent finishes a task — You get a Discord/Slack notification in a thread named after your tmux session, with the agent's response.
- Agent asks a question — The prompt appears in the same thread. Reply from Discord/Slack to answer it — no need to switch back to the terminal.
- You reply in the thread — Your message is forwarded to the agent's tmux session via SSH, as if you typed it at the keyboard.
- Shell command output — When the tmux session is running a plain shell (not an agent), command output is captured and relayed back to the thread automatically.

Every tmux session gets a dedicated thread. Start a session, get a thread. Close the session, the thread archives (or deletes — configurable). No manual wiring.

You can also manage sessions directly from Discord/Slack using bridge commands: !new  [host], !kill , !sessions. Inside a thread, use shortcuts to send key sequences: !c (Ctrl+C), !d (Ctrl+D), !z (Ctrl+Z), !q, !enter, !esc.

Unlike one-way notification tools, aily provides a full session bridge — monitor output, send input, and aily attach to jump into the same terminal view from CLI.

Demo

*Send…