Welcome to Ajapopaja Build – an automated task‑pipeline manager for Coding AI agents, with a human‑supervised management layer. It helps you break work into tasks, let agents design, implement, and review the changes, and approve the results before they land.
A pipeline of tasks that move through a clear lifecycle
(created → scheduled → in progress → implemented). A web dashboard gives you
full control, while a set of autonomous agents do the heavy lifting. The
project is a monorepo:
backend/– auvworkspace (coremodels,apiFastAPI server,ajapopaja_mcpMCP server).frontend/– a Vite + TypeScript Single Page Application (Tailwind CSS).design/– architecture and bot design documents.INSTALL.md– full production installation guide (Docker + systemd).
Agents work on real code inside isolated sandboxes and report back through the UI:
- CoderBot 🧑💻 – the end‑to‑end coder. It implements tasks described in design documents by driving the Pi coding agent in headless mode, then submits a pull request for your approval. Accept it (optionally auto‑committing the change) or reject it – all in the dashboard.
- ArchitectureBot 📐 – drafts a design document for a task with one click.
- ReviewBot 🔍 – performs an automated technical review of an implemented task (spec + design doc + git diff) and stores the review in the task.
- DocBot 📝 – creates design documents, code comments, and documentation.
- BotManager ⚙️ – queues and serializes every bot so only one LLM session runs at a time.
- Pull‑request workflow – every CoderBot change becomes a PR that is reviewed and committed (or rejected) in the UI.
- Human‑in‑the‑loop design review – tasks can require a design document that you approve before implementation starts.
- MCP + Pi integration – AI agents connect over the Model Context Protocol; a
piskill andmcp_client.pyCLI make task search/management scriptable. - Real‑time UI – WebSocket‑driven dashboard with a git‑status indicator, multi‑layout columns, persisted state, and a streaming logs viewer.
- Secure by default – JWT‑based authentication across the API, sandboxed workspaces with path‑traversal protection, and Markdown sanitization.
Production (Docker + Linux systemd service): follow the complete guide in
INSTALL.md – it covers building the Docker image, configuring
environment variables, and installing/applying the systemd service.
Quick local dev setup:
# Backend (Python 3.11+, uv, MongoDB, Ollama)
cd backend && uv sync
# Frontend
cd frontend && npm install
# Run them
cd backend && uv run --package api uvicorn api.main:app --reload # http://localhost:8000
cd frontend && npm run dev # http://localhost:5173See INSTALL.md and CONTRIBUTING.md for
environment variables and development guidelines.
- In the dashboard, create a Pipeline and point it at a local workspace.
- Create Tasks – give each a technical spec and choose whether it needs a design document (and which agent should handle it).
- Let the agent pick up the task: CoderBot implements it, ArchBot drafts a design, ReviewBot reviews it.
- Review the results (design docs, diffs, PRs) in the UI and accept or reject them.
# Backend
cd backend && uv run pytest
# Frontend
cd frontend && CI=true npm run testSee RELEASENOTES.md. The current release is 0.3.0.
Licensed under the Apache License 2.0. See LICENSE and LICENSE_COMPLIANCE.md for dependency licensing details.
Note: this repository has a
pre-pushhook that blocks unintentional pushes. To push to GitHub manually, setALLOW_PUSH=true git push.