Spacebot

Overview

Spacebot is a Rust-based AI agent framework from the Spacedrive team, designed specifically for teams, communities, and multi-user environments.^[1] While most AI agents are built for one person in one conversation, Spacebot handles concurrent interactions across Discord servers, Slack workspaces, and Telegram groups without any user waiting on another.

The core insight: a single-threaded agent breaks the moment two people talk at once. Spacebot's delegation model means it can think about User A's question, execute a task for User B, and respond to User C's small talk — all simultaneously.

Available as a one-click hosted deploy at spacebot.sh or self-hosted as a single Rust binary with no Docker or microservices required.

Status (as of June 2026): Actively developed. The repo launched February 11, 2026 and sits at ~2,266 stars and 345 forks, with five tagged releases shipped between March and May 2026 — most recently v0.5.0 on May 7, 2026.^[1][2] The last push to main was May 9, 2026, so there's been roughly a month of public quiet heading into June. The hosted offering at spacebot.sh is live with published pricing.^[3]

The Problem It Solves

Most AI agent frameworks run everything in a single session. One LLM thread handles conversation, thinking, tool execution, memory retrieval, and context compaction — all in one loop.^[1]

When the agent is doing work, it can't talk to you. When it's compacting context, it goes dark. When it retrieves memories, raw results pollute the context with noise.

The Spacebot README directly calls out OpenClaw: "OpenClaw does have subagents, but handles them poorly and there's no enforcement to their use. The session is the bottleneck for everything."

Spacebot splits the monolith into specialized processes that only do one thing and delegate everything else.

Five Process Types

1. Channels

The user-facing LLM process — one per conversation (Discord thread, Slack channel, Telegram DM). Has soul, identity, and personality. Talks to the user. Delegates everything else.

A channel does not: execute tasks directly, search memories itself, or do any heavy tool work. It is always responsive — never blocked by work, never frozen by compaction.

2. Branches

A fork of the channel's context that goes off to think. Has the channel's full conversation history — same context, same memories, same understanding. Operates independently. The channel never sees the working, only the conclusion.

Multiple branches run concurrently. First done, first incorporated. Each branch forks from the channel's context at creation time, like a git branch.

3. Workers

Independent processes that do jobs. Get a specific task, a focused system prompt, and task-appropriate tools. No channel context, no soul, no personality.

Fire-and-forget — do a job and return a result (summarization, file operations, one-shot tasks).

Interactive — long-running, accept follow-up input from the channel (coding sessions, multi-step tasks).

Workers come loaded with tools: shell, file, exec, browser (headless Chrome), Brave web search, and OpenCode integration for full coding agent capabilities.

4. The Compactor

Not an LLM process — a programmatic monitor per channel that watches context size and triggers compaction:

Compaction workers run alongside the channel without blocking it.

5. The Cortex

The agent's inner monologue. The only process that sees across all channels, workers, and branches simultaneously:

• Generates a memory bulletin — periodically refreshed, LLM-curated briefing injected into every conversation
• Supervises running processes (kills hanging workers, cleans up stale branches)
• Maintains the memory graph (decay, pruning, merging near-duplicates)
• Detects patterns across conversations and creates observations

Memory System

Not markdown files. Not unstructured blocks in a vector database. Spacebot's memory is a typed, graph-connected knowledge system.^[1]

Eight memory types:

• Fact, Preference, Decision, Identity, Event, Observation, Goal, Todo

Five graph edge types:

• RelatedTo, Updates, Contradicts, CausedBy, PartOf

Hybrid recall:

• Vector similarity + full-text search merged via Reciprocal Rank Fusion

Memory import:

• Drop files into ingest/ folder for automatic extraction
• Supports text, markdown, and PDF
• Migrating from OpenClaw? Drop your markdown memory files in and walk away

The agent doesn't just "remember things" — it knows the difference between a fact it learned, a decision that was made, a goal it's working toward, and a preference the user expressed.

Messaging Adapters

Native adapters for Discord, Slack, Telegram, Twitch, and Webchat with full platform feature support:

• Message coalescing — rapid-fire messages batched into a single LLM turn so the agent reads the room instead of spamming replies
• File attachments — send and receive files, images, documents
• Rich messages — embeds, buttons, select menus, polls (Discord); Block Kit and slash commands (Slack)
• Threading — automatic thread creation for long conversations
• Typing indicators — visual feedback while thinking
• Per-channel permissions — guild, channel, and DM-level access control, hot-reloadable

Multi-Agent Support

Each agent is an independent entity with its own:

• Workspace and databases
• Identity files and personality
• Cortex and memory graph
• Messaging bindings

All agents share one binary, one tokio runtime, and one set of API keys. Run a friendly community bot on Discord, a no-nonsense dev assistant on Slack, and a research agent handling background tasks — each with its own identity.

Model Routing

Four-level routing system that picks the right model for every LLM call:

1. Process-type defaults — channels get conversational models, workers get fast/cheap models
2. Task-type overrides — coding workers upgrade to stronger models
3. Prompt complexity scoring — lightweight scorer classifies user messages and routes to cheapest capable model
4. Fallback chains — automatic failover when primary models fail

Supports Anthropic, OpenAI, OpenRouter, Groq, Together, Fireworks, DeepSeek, xAI, Mistral, NVIDIA, MiniMax, Moonshot AI, Z.ai, and Ollama for local models.

Tech Stack

Single binary. No Docker required. No server dependencies. All data lives in embedded databases.

Spacedrive Integration

Spacebot is designed as the AI counterpart to Spacedrive — an open source cross-platform file manager built on a virtual distributed filesystem.^[4]

The vision: Spacedrive indexes files across all your devices, clouds, and platforms with content-addressed identity and semantic search. Spacebot brings autonomous reasoning, memory, and task execution. Together, an agent that can think, remember, and act — backed by terabytes of queryable data across every device you own.

Both projects are independent and fully functional on their own, but complementary by design.

Installation

Hosted (easiest):

spacebot.sh → Connect platforms, configure agent, done

Self-hosted:

git clone https://github.com/spacedriveapp/spacebot
cd spacebot
cargo build --release
spacebot  # start as background daemon

Minimal config.toml:

[llm]
openrouter_key = "env:OPENROUTER_API_KEY"

[defaults.routing]
channel = "anthropic/claude-sonnet-4"
worker = "anthropic/claude-sonnet-4"

[[agents]]
id = "my-agent"

[messaging.discord]
token = "env:DISCORD_BOT_TOKEN"

[[bindings]]
agent_id = "my-agent"
channel = "discord"
guild_id = "your-guild-id"

Pricing

As of June 2026, spacebot.sh publishes a hosted tier ladder plus paid support for self-hosters:^[3]

Annual billing is 25% off. Self-host support contracts run $59/mo (Basic) to $299/mo (Priority), with custom enterprise contracts. All plans are bring-your-own-keys — bundled LLM credits are "coming soon."^[3]

Releases Since Launch

Spacebot has kept a steady cadence since this profile was first written: v0.3.2 and v0.3.3 (March 2026), v0.4.0 and v0.4.1 (April 2026), and v0.5.0 (May 7, 2026).^[2] Highlights in v0.5.0: participant context in the memory system, non-blocking cortex synthesis, interactive shell streaming with live output, per-agent secret isolation, and a SpaceUI dashboard migration.^[5] The marketing site also now features cron scheduling with natural-language schedules and circuit breakers, plus first-class support for 10 LLM providers.^[3]

Strengths

• Concurrent by design — 50+ users interact simultaneously without blocking
• Typed memory graph — structure beats unstructured retrieval
• Single binary — no Docker, no microservices, no runtime dependencies
• Team-first — built for communities, not just solo users
• Message coalescing — handles busy channels without spam
• Spacedrive synergy — potential for deep filesystem integration
• Rust performance — no GC pauses, predictable resources

Weaknesses / Considerations

• FSL license — not fully open source until 2 years pass (then Apache 2.0)
• Complexity — 5 process types is more to understand than simpler alternatives
• Rust requirement — self-hosting requires Rust 1.85+ and cargo build
• Newer project — launched February 2026; less battle-tested than established frameworks
• Company sustainability — Spacedrive has a history of funding constraints; the flagship file manager's repo has slowed (last pushed April 19, 2026) and Jamie Pine has floated a "$spacedrive" token alongside Spacedrive 2, an unconventional funding signal worth watching^[4][6]
• Vendor-curated social proof — public adoption evidence is mostly testimonials republished on spacebot.sh, not independent reviews

What Developers Say

The most visible public commentary is the testimonial wall on spacebot.sh — note these are vendor-curated, and independent third-party reviews are still scarce as of June 2026:^[3]

"very nice indeed" — Tobi Lütke, CEO of Shopify (@tobi)

"spacebot replies so much faster than openclaw - using the same providers and same api keys.." — @stripeyhorse

"There IS a better way to do memory. And Spacebot is it. Early days, but it just makes sense." — @tylersookochoff

"Built for teams and communities is an insane selling point. Personal agents are cool but having an agent help your entire classroom, family group or friend group is sooo useful too." — @azapsoul

Who Built It

The Spacedrive team, led by Jamie Pine. Spacedrive itself has ~38K GitHub stars as an open source cross-platform file manager.^[4] Spacebot extends their vision into AI agent territory, leveraging the same Rust expertise and distributed systems thinking.

An honest caveat: Spacedrive's roadmap has been constrained by funding in the past, the file manager's commit activity has slowed in 2026, and Pine's January 2026 announcement of Spacedrive 2 referenced a "$spacedrive" token as part of the funding picture.^[6] Spacebot — with its paid hosted tiers — now looks like the team's primary commercial bet, which cuts both ways: it gets the attention, but its fate is tied to a small startup's runway.

Ideal User

• Community managers running Discord servers with active members
• Teams needing a shared AI assistant across Slack channels
• Rust developers who want a single-binary, no-Docker deployment
• Multi-agent experimenters wanting isolated agents with shared infrastructure
• Spacedrive users looking for AI integration with their file system

Bottom Line

Spacebot represents a serious architectural rethinking of AI agents for multi-user environments. The five-process-type model (Channel, Branch, Worker, Compactor, Cortex) directly addresses the "session bottleneck" problem where most agents go dark during heavy work.

The typed memory graph with 8 memory kinds and 5 edge types is more sophisticated than the markdown-file approach of most alternatives. Combined with hybrid vector+FTS search and LLM-curated memory bulletins, it's one of the more thoughtful memory implementations available.

The FSL license means it's not fully open source yet — a consideration for some teams — but converts to Apache 2.0 after two years. The execution since launch backs up the design: five releases in three months, a live hosted product with published pricing, and ~2.3K stars in its first four months.^[1][2]

Recommended for teams and communities tired of single-user AI assistants that crumble under concurrent load — it's the most purpose-built option available, and self-hosting is free. Not recommended yet as a load-bearing dependency for risk-averse production teams: the project is four months old and Spacedrive's funding history warrants caution.

Outlook: Watch whether the release cadence holds past the May 2026 push lull and whether hosted revenue stabilizes the company. If Spacebot becomes Spacedrive's commercial engine, expect deeper Spacedrive filesystem integration; if funding pressure resurfaces, the FSL-to-Apache conversion at least guarantees the code outlives the company.

---