Spore

Spore

Core. Code. Go.

One AI stack. Three faces. Bring any model.

the agent

Spore listens.
Spore learns.

Multi-user, persistent, self-hosted. Slack threads, Notion docs, web pages, your terminal — every conversation distills into a node Spore can recall, link, and reason over later.

context, recalled

Same agent.
Same memory.

Ask about a project and Spore pulls the threads — your teammates, their briefs, the libraries that just shipped — and answers in context. The graph is the throughline.

spore code

The same agent.
Precise on code.

A remote terminal session that taps into Spore Core — same memory, scoped to your project. Plan it, execute it, all backed by citations from the graph.

spore core evolves

Project work
feeds the graph.

Background agents distill each session into reusable knowledge — libraries, tools, decisions — and prune the raw memory so context doesn't bleed between sessions.

spore go

Spore Code,
on the go.

Walk away from your machine — your terminal session keeps running. Read the activity, approve plans, send the next instruction from your pocket. Android only for now.

feature surface

More than a chat box.
One connected system.

Spore is designed around a lot of surface area: multi-user channels, always-on web sessions, live terminal sessions, graph memory, plugin support, built-in SearXNG search, project activity, and mobile continuity all feed the same agent instead of becoming separate tools.

web + cli

Always-on sessions

Persistent web chat
Remote terminal sessions
Session picker and handoff
Spore Go continuity

multi-user

Team channels

Multi-user workspaces
Channel-based context
Shared project rooms
Invite-gated access

context

Graph memory

People, projects, tools
Source-linked recall
Reusable decisions
Scoped session context

tools

Plugins & search

Plugin support
SearXNG search included
Tool adapters
Model-agnostic wiring

work

Project execution

Repo-aware coding
Activity timeline
Activity and task panels
Background distillation

infra

Self-hosted control

Docker deployment
Bring your model key
Self-hosted runtime
Local data volumes

Channels keep people, projects, and long-running work organized.

Terminal sessions keep running and can be re-entered later.

Plugins and SearXNG search give the agent useful tools out of the box.

Distillation turns the work into graph knowledge the next session can use.

self-host

Get your Spore.

Docker image, your hardware, any model. Start the released image directly, or use the docs for persistent volumes and environment setup.

$docker run vibecoalition/spore-core:latest