LoopForge
Describe the change in chat, and LoopForge opens a Docker sandbox, checks out your repositories, hands the work to specialist agent roles, and opens the pull request. That is the conversational path: a Main Bot coordinates planning, implementation, review, and testing roles, each with its own prompt, executor, model, rules, skills, and tools, and you can queue or steer messages mid-reply, then pause, resume, or take over a run at any point. When a way of working proves itself, you freeze it as an SOP: a visual canvas of agent steps, deterministic script steps, human gates, and sub-workflows that every requirement then follows in the same order with the same checks. Four built-in SOPs cover backend delivery, frontend delivery, product proposals, and bug fixes, and each one can be copied, edited, and versioned per project. A Needs review inbox collects every gate waiting on you, with per-node status, tool traces, logs, and artifact snapshots as the evidence behind each approval. Recurring AI tasks run on schedules with the same workspace and workflow access, and insights reports track engineering metrics and token costs per run and per conversation. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Deploy