Contents

teamsloppy/sloppy

> Did you catch your Sloppie?

🎯 Sloppy is right for you if

βœ… You vibe-code and want AI agents that handle the boring stuff while you focus on ideas

βœ… You want personal master agents β€” like a team of experts that execute anything you ask

βœ… You automate repetitive workflows and need agents that run reliably, not just once

βœ… You orchestrate multiple AI agents (Claude, Codex, Cursor, OpenClaw) and need one place to see what everyone is doing

βœ… You want agents running autonomously 24/7, but still want to audit, steer, and chime in when needed

βœ… You want native macOS & iOS apps, a web dashboard, plus Telegram & Discord β€” all talking to the same runtime

βœ… You want to manage your autonomous workflows from your phone

πŸ’‘ What Is Sloppy

Sloppy is a control plane for AI agents and tool-driven workflows.

At its core, the project provides:

| Component | Purpose | | --- | --- | | sloppy | πŸ–₯️ HTTP API, routing layer, orchestration services, persistence, scheduling, and plugin bootstrap | | AgentRuntime | 🧠 Runtime model built around Channel, Branch, Worker, Compactor, and Visor | | PluginSDK | πŸ”Œ Extension points for model providers, tools, memory, and gateways | | Node | βš™οΈ Daemon for process execution | | Dashboard | πŸ“Š Vite/React UI for runtime visibility |

The runtime is designed to keep agent execution structured, inspectable, and recoverable instead of collapsing everything into one opaque prompt loop.

✨ Features

| Feature | What it provides | | --- | --- | | πŸ”€ Channel / Branch / Worker runtime | Separates user interaction, focused work, and execution flows | | πŸ“ Rule-based routing | Makes route decisions deterministic and inspectable | | πŸ—οΈ Worker modes | Supports both interactive and fire-and-forget workers | | πŸ“¦ Compaction | Triggers summarization on context thresholds | | πŸ‘οΈ Visor bulletins | Produces periodic memory digests for operators | | πŸ’Ύ SQLite persistence | Stores channels, tasks, events, artifacts, and bulletins | | πŸ”Œ Plugin system | Extends models, tools, memory, and gateways without hard-coding providers | | πŸ€– AnyLanguageModel bridge | Connects providers such as OpenAI and Ollama | | πŸ’¬ Telegram gateway | Bridges Telegram chats into Sloppy channels | | πŸ“Š Dashboard | Exposes chat, activity, artifacts, and runtime state in the UI |

🧩 Problems Sloppy Solves

Sloppy is built for teams that need more structure than a single-agent chatbot can provide.

| Problem | How Sloppy addresses it | | --- | --- | | πŸ” Agent behavior is too opaque | Turns execution into explicit runtime entities and lifecycle events | | ⏳ Long-running flows are hard to understand | Persists state, artifacts, and event logs | | πŸ“ˆ Context grows too quickly | Splits work into branches and workers and returns concise outputs | | πŸ’° Token costs drift upward | Uses compaction and short structured payloads | | 🧢 Integrations become fragmented | Unifies channels, tools, memory, and model providers behind one runtime | | πŸ™ˆ Operators lack visibility | Exposes the system through an API and dashboard instead of raw prompt debugging |

πŸ† Why We Are Different

What makes Sloppy distinct in its current form:

  • πŸ¦… Swift-first runtime β€” the orchestration layer, persistence, HTTP transport, and executables live in a single Swift package.
  • 🎯 Deterministic routing before autonomy β€” routing is policy-driven and inspectable, not hidden inside a monolithic LLM prompt.
  • πŸ‘οΈ Runtime visibility as a product feature β€” channels, workers, events, artifacts, and bulletins are first-class concepts.
  • πŸ”Œ Plugin boundaries instead of hard-coded providers β€” models, gateways, tools, and memory can evolve independently.
  • 🏠 Local-first development path β€” you can run the core, SQLite persistence, dashboard, and local model integrations without building a large distributed system first.

πŸš€ Quick Start

git clone https://github.com/TeamSloppy/Sloppy.git
cd Sloppy
bash scripts/install.sh
sloppy run

By default the installer builds the server stack and bundled dashboard assets. To skip the dashboard build, run:

bash scripts/install.sh --server-only

Default local endpoints after sloppy run:

  • API: http://localhost:25101
  • Dashboard: http://localhost:25102

Remote bootstrap variants:

curl -fsSL https://sloppy.team/install.sh | bash
curl -fsSL https://sloppy.team/install.sh | bash -s -- --server-only

πŸ“– For detailed install options, Docker, and configuration, see docs/install.md and docs/index.md.

❓ FAQ

Do I need an API key to run Sloppy?

No. The runtime, tests, and dashboard can run without OpenAI credentials. You only need provider-specific credentials when you want to use those providers.

Which channels are supported?

The repository currently ships built-in Telegram and Discord channel plugins. The HTTP API is also a first-class entry point, and additional gateways can be added through the plugin system.

Does Sloppy support MCP and ACP?

Yes. Sloppy can connect to external MCP servers and expose their tools/resources to agents, and it can delegate agent execution to external ACP-compatible coding agents.

Where does Sloppy store data?

The default runtime uses SQLite for persistence. Workspace data, logs, artifacts, and related runtime files are created under the configured workspace root.

Does Sloppy have observability tooling built in?

Yes. The dashboard, persisted events, artifact tracking, and Visor bulletins are all part of the current product surface, not future roadmap items.

Is there a native app?

Yes. The repository includes an Apple client workspace in Apps/Client. It is currently an internal-first native client, built separately from the root server package.

Does Sloppy support Linux?

Yes. Linux is part of the active build and release matrix in CI. For direct terminal builds on Ubuntu or Debian-based systems, install libsqlite3-dev before running Swift commands.

Where can I read more about the architecture?

Learn more about Sloppy in DeepWiki

🀝 Contributing

Contributions should stay aligned with the current architecture, validation steps, and repository rules.

πŸ“– Start here: install and development workflow

⭐ Star History

[[Star History Chart]](https://www.star-history.com/?repos=teamsloppy%2Fsloppy&type=date&legend=top-left)

πŸ“„ License

Sloppy is released under the MIT License. See LICENSE.

Package Metadata

Repository: teamsloppy/sloppy

Default branch: main

README: README.md