Iterate over your agents 10x faster. AI engineers use PySpur to iterate over AI agents visually without reinventing the wheel.
hero_dark.mp4
AI engineers today face three problems of building agents:
- Prompt Hell: Hours of prompt tweaking and trial-and-error frustration.
- Workflow Blindspots: Lack of visibility into step interactions causing hidden failures and confusion.
- Terminal Testing Nightmare Squinting at raw outputs and manually parsing JSON.
We've been there ourselves, too. We launched a graphic design agent early 2024 and quickly reached thousands of users, yet, struggled with the lack of its reliability and existing debugging tools.
step1.mp4
step2.mp4
step3.mp4
step4.mp4
- 👤 Human in the Loop: Persistent workflows that wait for human approval.
- 🔄 Loops: Iterative tool calling with memory.
- 📤 File Upload: Upload files or paste URLs to process documents.
- 📋 Structured Outputs: UI editor for JSON Schemas.
- 🗃️ RAG: Parse, Chunk, Embed, and Upsert Data into a Vector DB.
- 🖼️ Multimodal: Support for Video, Images, Audio, Texts, Code.
- 🧰 Tools: Slack, Firecrawl.dev, Google Sheets, GitHub, and more.
- 📊 Traces: Automatically capture execution traces of deployed agents.
- 🧪 Evals: Evaluate agents on real-world datasets.
- 🚀 One-Click Deploy: Publish as an API and integrate wherever you want.
- 🐍 Python-Based: Add new nodes by creating a single Python file.
- 🎛️ Any-Vendor-Support: >100 LLM providers, embedders, and vector DBs.
This is the quickest way to get started. Python 3.11 or higher is required.
-
Install PySpur:
pip install pyspur
-
Initialize a new project:
pyspur init my-project cd my-project
This will create a new directory with a
.env
file. -
Start the server:
pyspur serve --sqlite
By default, this will start PySpur app at
http://localhost:6080
using a sqlite database. We recommend you configure a postgres instance URL in the.env
file to get a more stable experience. -
[Optional] Configure Your Environment and Add API Keys:
- App UI: Navigate to API Keys tab to add provider keys (OpenAI, Anthropic, etc.)
- Manual: Edit
.env
file (recommended: configure postgres) and restart withpyspur serve
These breakpoints pause the workflow when reached and resume whenever a human approves it. They enable human oversight for workflows that require quality assurance: verify critical outputs before the workflow proceeds.
HIL.mp4
visualization.mp4
PDFs, Videos, Audio, Images, ...
multimodal.mp4

RAG_1.mp4
RAG_2.mp4
blocks.mp4
evals.mp4
optimization.mp4
We recommend using Cursor/VS Code with our dev container (.devcontainer/devcontainer.json
) for:
- Consistent development environment with pre-configured tools and extensions
- Optimized settings for Python and TypeScript development
- Automatic hot-reloading and port forwarding
Option 1: Cursor/VS Code Dev Container (Recommended)
- Install Cursor/VS Code and the Dev Containers extension
- Clone and open the repository
- Click "Reopen in Container" when prompted
Option 2: Manual Setup
-
Clone the repository:
git clone https://github.com/PySpur-com/pyspur.git cd pyspur
-
Launch using docker-compose.dev.yml:
docker compose -f docker-compose.dev.yml up --build -d
-
Customize your setup: Edit
.env
to configure your environment (e.g., PostgreSQL settings).
Note: Manual setup requires additional configuration and may not include all dev container features.
You can support us in our work by leaving a star! Thank you!
Your feedback will be massively appreciated. Please tell us which features on that list you like to see next or request entirely new ones.