Spacebot

Spacebot is a multi-threaded AI agent harness that runs LLM agents on Discord, Slack, Telegram, and Twitch.

  • AI
  • Automation
Spacebot is a multi-threaded AI agent harness that runs LLM agents on Discord, Slack, Telegram, and Twitch. It keeps persistent state in structured storage — a typed memory graph in SQLite — and drives autonomy with a task state machine linked to goals, capturing reusable skills from finished work. It suits teams, communities, and anyone who wants an always-on agent that improves with use.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
81last commit 57 days ago
Popular
682,429 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
103 serious findings, 12 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 16 days ago

GitHub stars
2,429
Open issues
186
Last commit
2026-09-25
Latest release
v0.5.0
Activity
stale

Checked 13 days ago - source: GitHub (spacedriveapp/spacebot)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Put durable tools in /data/tools/bin Copy or download persistent command-line tool binaries into `/data/tools/bin`, and avoid relying only on package managers like apt or brew. That folder is on the app's PATH (the list of folders it checks for commands) and survives restarts, so tools won't disappear and leave the agent unable to run them. source
  • Install a skill from a .skill file To add a saved skill, run `spacebot skill install path/to/skill.skill` in your terminal. If you skip this step, that skill's instructions and files won't be available to the agent. source
  • Skills need a SKILL.md with name and description When creating a skill, include a `SKILL.md` file with the required frontmatter (the small metadata section at the top) including `name` and `description`. These tell Spacebot what the skill is called and what it does, helping it load the skill correctly. source
  • Quick start A one-click deploy script (spacebot.sh) connects Discord, Slack, Telegram, or Twitch to your agent and configures it in a single step. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where should I put persistent command-line tools so Spacebot still has them after restarts?

Copy durable tool binaries into /data/tools/bin and avoid relying only on package managers like apt or brew. That folder is on Spacebot's PATH and survives restarts, so tools won't disappear and leave the agent unable to run them.

How do I add a saved skill so the agent can use it?

Run spacebot skill install path/to/skill.skill in your terminal. If you skip this step, the skill's instructions and files won't be available to the agent. The skill also needs a SKILL.md with frontmatter including name and description so Spacebot can load it correctly.

Can I run Spacebot behind Caddy when self-hosting?

A self-hosting setup guide for Ubuntu Server uses Caddy as a reverse proxy for Spacebot. It also covers building from source, systemd, model routing, and nightly auto-updates.

Which Spacebot 0.5.0 issues are tracked for Docker or self-hosted use?

The issue list includes model allowlist behavior, an agents.permissions schema gap, channel-level fallbacks, dedicated voice-transcription endpoints, and non-atomic config writes.

Answers sourced from github.com, github.com, github.com, www.jnye.co

Community

Collected 49 days ago - public community threads