Overview
Learn how to get started and implement ReArch Engineer through our developer resources.
Key Features
Section titled “Key Features”- Background Execution — Sandboxed VMs that work while you sleep.
- MCP Support — Choose from the gallery, or use your own.
- Visual Verification — Screenshots and live previews.
- Multiplayer — Collaborate in real-time sessions.
- Your Repositories — Connect GitHub or Bitbucket. No migration needed, no lock-in.
- Last Frontier Models — Cutting-edge AI models.
- Cost Monitoring — Statistics per user, conversation, and more.
- Work Space — VS Code also available.
Scaffold exactly what you need
Section titled “Scaffold exactly what you need”The ReArch Agent lets you pick your starting point. Need custom pages? Use --pages and they’re generated with routes and nav already wired. Pair it with --i18n and you get localized versions too — translations scaffolded and ready.
No prompts to click through. No wizard to escape. Just flags that do what they say.
How it works
Section titled “How it works”- Connect your repositories — Link your GitHub or Bitbucket repos. ReArch clones, indexes, and understands your codebase automatically.
- Describe what you need — Use natural language to tell ReArch what to build, fix, or improve. Anyone on your team can do this — not just engineers.
- ReArch works in the background — A sandboxed VM spins up, writes the code, runs tests, and takes visual screenshots for verification.
- Review and ship — Get a pull request with the changes, preview the results, and merge when ready.
Use cases
Section titled “Use cases”- Non-technical teammates shipping features — Product managers, designers, and ops teams describe what they need and ReArch delivers working code.
- Bug fixes and maintenance — Point ReArch at an issue and let it investigate, fix, and verify the solution while you focus on other work.
- Scaffolding new projects — Spin up pages, components, API routes, and i18n support with a single command.
- Code reviews and refactoring — Let ReArch analyze your codebase and propose improvements, migrations, or cleanups.
- Prototyping and experimentation — Quickly test ideas without pulling engineers off their current sprint.