Skip to content
Ali-Labs-XPublic

About

Build your bot army: bots with roles that collaborate in squads, hand off work and report to a commander. Self-hosted. By AliLabsX.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1,486 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Nova Bots

Nova Bots

English | 中文

version license

Build your bot army.

Spin up a bot for any job, give it a role, and let them collaborate: they hand off work, run in squads and report to a commander. Each bot has a name, a role, instructions and a model, and keeps its own chat, memory and working folder. Squads are group chats where bots message each other, hand off work with @ and report back in one place. Orion, your commander (a Main Bot), creates, changes and removes the other bots. Self-host it, and all of it runs on your own machine.

I built it because I would rather own the stack than rent it. Your hardware, your data, your models.

Nova Bots

How it works

  1. Spin up a bot. Give it a name, a role, instructions and a model.
  2. Form a squad. A group chat puts several bots on one problem, with an admin that answers first and calls in the others.
  3. Let them collaborate. One researches, one builds, one reviews: bots hand work along, post progress in the squad and report the result back. You see every handoff and can stop any of them.
  4. Command with Orion. Your commander has the highest rights and runs the army for you. There can be more than one commander.

Quick start

The fastest way to run Nova Bots is Docker. It builds the whole stack — engine, plugin, browser runtime and the Nova interface — into one container.

git clone https://github.com/Jahanzaib211/nova-bots.git Nova-Bots
cd Nova-Bots
cp docker/.env.example docker/.env
./nova-bots.sh start
./nova-bots.sh url

Open the printed login URL once. After that, http://127.0.0.1:13080/ opens the UI directly. For a full walkthrough — host folders, ports, models, backups and reboot survival — read RUNNING.md and the Docker guide.

The public address

The Docker deployment publishes the workspace under a public name and signs you in with an email and a password:

./nova-bots.sh tunnel          # print the public URLs
./nova-bots.sh tunnel-status   # connector state and reachability

Behind the address sits a small web front end (nginx) and a portal that keeps the accounts and hands the request to the bots. The accounts live in their own database; the bots' engine is bound to the loopback, so nothing but the portal can reach it. See RUNNING.md for the whole shape.

Run it as a plugin

Nova Bots also installs as a plugin into a compatible agent runtime. Build or download nova-bots-0.2.6.tgz, then add it through the runtime's plugin manager — the same page where you add any other plugin — and enable it.

The plugin package is built from ds-bot/. For source builds, tests and internals, see ds-bot/README.md.

Run it as the desktop app

Nova Bots also has its own Electron desktop app (app/), which carries a pinned runtime and never writes to ~/.dsh. It installs on Windows, macOS and Linux. The Working folder menu lives in the app's Settings, the plugin's own dialog, and offers "Choose a folder…" — a native OS folder dialog to browse and pick any local folder as a Bot's working folder, no typing needed — where the runtime mounts a native picker (macOS and Windows, and a Linux desktop that has a chooser installed), and "Browse folders…" where it mounts the in-app folder browser instead; "Enter a path…" always works. The window itself has no Bot details drawer. Build, test and packaging details are in app/README.md.

Meet the team

One bot, one window

Talk to a bot the way you talk to a person. It remembers what you told it, keeps its working folder, and picks up where it left off. Its details panel shows its model, memory and usage; switch models there whenever you need to.

Orion, your Main Bot

Every new team starts with Orion, the Mission Commander and team lead. Orion has the highest rights: it creates, changes and removes the other bots and keeps the group chats in order. It also walks you through setup the first time you open the app.

Have a question? Ask Orion.

Group chats

A group chat puts several bots on one problem. Every group has an admin: the admin answers by default and calls in the specialists you need. You can also @ a bot directly and it answers you in the group. To give the group another chat as context, use + → Reference a chat in the message box.

Bots hand work to each other with @. The helper posts progress in the group, finishes on its own, and the bot that asked answers with the result. The group's details panel shows every handoff and can stop one.

Each group has its own memory. What you say in the group stays there: its members use it, and your other chats do not see it.

Capabilities

Settings → Capabilities is a shared library of MCP servers, skills and packs. Attach a capability to a bot and it is available from that bot's next message, in its own chat and in every group it belongs to. A local MCP command needs your approval before it can run. While other bots use a capability, only you or a Main Bot can change or delete it.

Usage

Settings → Usage breaks token usage down by time, bot and model.

Office files

Bots create and edit .docx, .pptx and .xlsx files. They can read a document's structure with stable ids, check a package for the defects Office would reject, make targeted edits (comments, tracked changes, fields, table cells), reorder or duplicate slides, list workbook errors, and review rendered pages on a contact sheet. The Docker image carries everything needed for the full workflow.

Your data

Everything stays on your machine. The Docker deployment keeps its state in docker/data/; a plugin install keeps it in the runtime's home folder. Uninstalling the plugin does not delete the data.

Back up docker/data/ and docker/.env (stop the container first). Mounted host folders are backed up with the rest of your files.

Development

  • ds-bot/ — the bot features and interface source.
  • docker/ — the container build, Nova brand layer and operator settings.
  • nova-bots.sh — start, stop, rebuild, mounts, login URL and the boot unit.
  • CONTRIBUTING.md — tests, branches and review.
  • AGENTS.md — the same rules for AI coding agents.
  • CHANGELOG.md — what changed between versions.
cd ds-bot
npm ci
npm run harness
npm test
npm run build
npm run lint

Credits

  • esbuild bundles the interface code.
  • The bot-memory format, group-chat rounds, chat search and handoff notes were informed by ideas published by AgentMemoryRepo, OpenAI Codex, OpenMausBot, Hermes Agent, OpenCode, goose, pi, Gemini CLI and obelisk. No code from those projects is included.
  • Nova Bots is derived from DS Bot by Fei2411 and the DS Bot contributors, licensed under Apache 2.0. Its notice is kept in NOTICE.
  • Everyone who runs Nova Bots, asks questions and reports bugs.

Links

License

Apache License 2.0. Provided "as is", without any warranty. Third-party code and its license are listed in NOTICE.

Disclaimer

Nova Bots is an independent project. Bots use your own model quota, and they read and write files and run commands when you ask them to. Check important actions yourself.

Work with me

Nova Bots is built by Jahanzaib Ali, Founder & Systems Engineer at AliLabsX. If you want your own bot army, a self-hosted deployment or help with platform engineering, get in touch. If you would rather not run it yourself, there is a hosted version at https://bots.alilabsx.com.

About

Build your bot army: bots with roles that collaborate in squads, hand off work and report to a commander. Self-hosted. By AliLabsX.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages