An AI assistant that lives in your Telegram.

Bring your own API key, paste a bot token, start talking. No server to run, nothing to install.

op

ops assistant

bot ยท node build-01 online

  • What's eating disk on the build server?
  • exec on node build-01: du -sh /var/lib/docker/*
  • Docker build cache is 41 GB. Overlay2 layers from images you no longer run. Want me to prune dangling images only?
  • yes, dangling only
  • exec on node build-01: docker image prune -f
  • Done. Reclaimed 27.3 GB. Free space on / is now 118 GB.

Works with the keys you already have

  • AnthropicAnthropic
  • OpenAIOpenAI
  • Google GeminiGoogle Gemini
  • OpenRouterOpenRouter
  • OllamaOllama
  • TelegramTelegram

Three pastes and you have an assistant.

  1. Add an API key

    Anthropic, OpenAI, Gemini, OpenRouter or any OpenAI-compatible endpoint. Encrypted at rest, tested on save.

  2. Paste a bot token

    Create a bot with BotFather, paste the token. We verify it and wire the webhook. Add as many bots as you like.

  3. Talk to it

    Your first message gets a pairing code. Approve it once in the dashboard and the bot is yours. Nobody else gets in.

Hosted by default. Yours when you want it.

Everything runs on our side until you decide to plug in your own tools, servers or machines.

MCP servers, pluggable per bot

Point a bot at any Model Context Protocol server over HTTP or SSE. Tools are discovered automatically and you pick which bots may call which tools.

A workspace with memory

Persona, notes and daily memory live as plain files you can read and edit.

Your machine as a node

One command connects Windows, macOS, Linux or a Docker host. Files and shell, with approvals.

Many bots, one account

A terse ops bot on one model, a chatty research bot on another. Each with its own prompt and access list.

Your keys, your bill

We never resell tokens. Usage shows up on your provider invoice, and in the dashboard.

Reach your own machines when the cloud is not enough.

A node is a small agent you run anywhere. It opens an outbound connection, declares what it can do, and waits. Risky commands ask for approval right in the chat.

  • Windows, macOS and Linux binaries, or a Docker image with a persistent volume.
  • Capabilities are opt-in per node: files, shell, screenshots, notifications.
  • Revoke a node from the dashboard and it is gone instantly.
# on your machine
npx easylopster-node connect 7KQ2-M9XA

# or as a container with its own filesystem
docker run -d --name el-node \
  -e EASYLOPSTER_TOKEN=... \
  -v el-workspace:/workspace \
  ghcr.io/noneym/easylopster-node

Free while in beta.

Three bots, two nodes, five MCP servers per account. Enough to run a small team's worth of assistants.

Start free