Skip to content

LoopForge

Your Personal AI Engineer for real shipping work.

Start with one command, get a real artifact, and keep a reproducible trail from prompt to deliverable.

Start with onboard Starter tasks Troubleshooting Why LoopForge Runtime Architecture

LoopForge is optimized for builders who care about local-first workflows, real artifacts, and audit-friendly delivery.

Product name: LoopForge. CLI: loopforge. Runtime data path: ~/.loopforge.

Start Here

1
2
ollama serve
loopforge onboard --workspace loopforge-onboard-demo

1
loopforge onboard --workspace loopforge-onboard-demo --skip-agent

1
loopforge onboard --workspace loopforge-onboard-demo --starter workspace-brief

After onboard, LoopForge writes:

  • loopforge-onboard-demo/.loopforge/onboard-report.json
  • loopforge-onboard-demo/.loopforge/onboard-report.md

These files tell you what passed, what failed, and what to do next.

  • First-Day Starter Tasks Pick a guided first task instead of writing a prompt from scratch. Open starter tasks

  • Onboarding Troubleshooting Fix common first-run issues quickly: config, provider, browser, or model setup. Open troubleshooting

  • Fix One Failing Test Ask LoopForge to run tests, repair one failure, and write notes/fix-report.md. Copy/paste prompt

  • Reproducible Progress Keep a clear trail: change -> verify -> checkpoint. Harness workflow

  • Agent Team Playbook Organize Planner / Builder / Reviewer / Release roles with one artifact trail. Open playbook

  • Runtime Architecture Understand how CLI, runtime, tools, memory, and audits fit together. Open architecture guide

Where We Fit

  • Choose LoopForge when you care most about engineering delivery, reproducibility, and useful artifacts.
  • Choose assistant-style products when you care most about everyday personal chat workflows.
  • Choose broad operations platforms when you need channel coverage first.

Next Steps