Skip to content

Persistent AI agents.
On your own server.

Give every agent its own Docker container, a workspace that survives restarts, and a private Telegram chat with optional Discord DMs. Keep your agents working while your computer is off.

curl -fsSL https://raw.githubusercontent.com/celeris-it/nimbot/main/install.sh | bash

Compatible with macOS and Linux. Requires Docker Compose.

THE TOOLS BEHIND THE BENEFITS

Their own space.
Your everyday tools.

Six practical capabilities for running persistent agents on infrastructure you control.

One agent. Its own world.

A dedicated Docker container for every agent. Separate tools, dependencies, and files. Nothing gets mixed up.

A workspace that remembers.

Files and conversations survive restarts. Pending tasks are saved before they run. Tasks interrupted by a restart are marked so you know what needs attention.

Your server. Your rules.

Agents keep working on your server while your personal computer is off. You control the infrastructure and set CPU and memory limits for each agent.

Tasks, progress, and a private chat.

Agents work with files, run terminal commands, and use a browser inside their containers. Queue tasks, follow progress, cancel work, and receive results in each agent’s private Telegram or configured Discord DM. Both channels use one task queue; progress and results return to the channel that received the task.

A clear boundary for secrets.

Bot tokens stay on the server, outside agent containers. Agents run as non-root, without the Docker socket or server credentials.

Administration in one panel.

Create, configure, start, stop, and delete agents from an authenticated web panel. Connect, replace, test, or remove Discord without changing Telegram. Deleting an agent never silently deletes its persistent volume.

WHO IT IS FOR

A little help with real work.

For people comfortable running their own tools. Start with a task you already do.

Developers

Delegate code changes, inspect a project, or ask for a script. Keep each project’s tools and dependencies in its own agent workspace.

Researchers

Ask an agent to browse sources, compare findings, and save a research summary you can review.

Technical users

Work with files, prepare reports, and run scripts through a private Telegram or Discord conversation. Review results and approve sensitive actions.

SMALL SETUP. LASTING POSSIBILITIES.

Make yourself at home.

A Linux server, Docker Compose, and a bot. That’s where it begins.

  1. Bring your own server

    Follow the Docker Compose guide. Nimbot keeps state in SQLite and Docker volumes. No extra database service.

  2. Give an agent its own space

    Sign in to the web panel, create an agent, and link its Telegram bot from BotFather.

  3. Start a conversation

    Send your Telegram bot a private message to link your chat automatically. Optionally connect Discord in the panel and send tasks through either owner DM.

TOOLS & INTEGRATIONS

A small stack. A clear role for each.

Telegram and optional Discord for conversations, Docker Compose for deployment, and OpenCode as the AI engine.

Telegram

Send tasks, follow progress, give approvals, and receive results in a private chat with each agent.

Discord

Optional owner-only DMs with the same agent, workspace, and context as Telegram. Follow progress, approve actions, and cancel work with /stop.

Docker Compose

Run Nimbot on your Linux server, with separate agent containers and persistent Docker volumes.

OpenCode

Nimbot’s AI engine, connected through ACP. Configure your AI provider for each agent.

New superpowers. Familiar conversations.

Your bots don’t need a separate chat app. Send a task, check progress, and get the result in the messenger you already use.

Two channels. One agent.

Start with each agent’s own Telegram bot and optionally connect a Discord bot from the panel. Only the configured owner can use each private chat. Both channels share the same workspace, context, and task queue; approvals return to the originating channel.

Test a fixed Discord message from the panel and check its delivery status. Discord may block DMs because of privacy settings, a blocked bot, or no shared server. These tests do not enable autonomous or scheduled notifications.

WhatsApp and other messaging apps remain future possibilities. Guild channels and group chats are not supported.

CHOOSE YOUR HOME

Your server today. Our hosting next.

Start with the free self-hosted software. Managed hosting is planned for later.

Self-hosted

Free

Apache 2.0 software license

For people who want to run Nimbot on their own infrastructure.

  • You host and manage Nimbot
  • Dedicated containers and persistent workspaces
  • Telegram, optional Discord DMs, and administration panel

Your server and AI provider are paid separately, under their own pricing and terms.

Install with Docker Compose

Managed hosting

Coming soon

Price to be announced

A paid plan where we host your bots. Planned for people who prefer us to handle hosting.

Not available yet. Pricing and plan details will be announced later.

A few things to know.

What is free, and what will the paid plan cover?

The self-hosted Nimbot software is free under Apache 2.0. You pay for and manage your server and AI provider. A separate paid plan where we host your bots is planned, but is not available yet. Pricing and plan details have not been announced.

Is Nimbot a hosted service?

The current MVP runs on your own Linux server with Docker Compose. You manage the infrastructure and connect your AI provider. A separate managed hosting plan is coming later.

Do I need another app to chat with my agents?

No separate Nimbot chat app. Every agent has its own Telegram bot, and you can connect an optional Discord bot from the web panel. Both private conversations use the same agent and context. WhatsApp is not supported.

What happens when I stop or delete an agent?

Stopping an agent preserves its workspace. Deleting an agent does not silently delete its persistent volume. Your saved files remain until you explicitly remove the data.

Can I use Nimbot commercially?

Yes. Apache 2.0 lets you use, modify, and deploy Nimbot commercially under its license terms, without an additional commercial license from Nimbot. Infrastructure and AI provider costs and terms still apply.

Does all my data stay on my server?

Your agent workspaces are stored on your server. Telegram processes your chat messages; Discord processes messages sent through its optional connection, and your AI provider receives the context sent to it. Self-hosting gives you control of the deployment; it does not mean all data stays offline.

What is the current project status?

The self-hosted MVP is complete. Docker Compose installation has been validated on macOS and Linux. Optional Discord conversations and panel delivery tests are implemented. See GitHub for the latest development status.