reboundNew here? Start with the documentation for setup, workflow, data controls and contributing.
Before you start.
Use Node 24.15+ on the 24.x line, or Node 26+, with npm, git, bash and curl. On Windows, use WSL with a Linux environment. The integrated starter builds the shared contracts and API and installs root/workspace dependencies when missing.
git clone https://github.com/AnkitParekh007/rebound-ops.gitcd rebound-ops
scripts/start-demo.shFirst-run troubleshooting.
“Recovery service is offline” appears.
Restart the integrated demo with scripts/start-demo.sh. The workspace uses port 4317 and the recovery API uses port 4174. The bridge will not invent a fallback plan when the API is unavailable.
A port is already in use.
Stop an existing local ReboundOps process before starting another. The integrated demo needs ports 4317 and 4174. Check the terminal output for the process that failed to start.
My recovery session disappeared after a restart.
Memory-only sessions do not survive API restarts. In the full recovery app, download a JSON backup or explicitly opt into local disk saving after configuring a private data directory. Durable recovery sessions are not exposed through the integrated demo bridge yet.
I want the standalone Angular recovery app.
From the repository root, run npm ci, then npm run dev. Open http://127.0.0.1:4200. This runs the Angular frontend alongside the local Fastify API.
Do I need to configure AI?
No. Start with the core recovery flow. Optional recovery AI needs both local enablement and a provider key, followed by payload preview and consent per request. Open Set up AI assistance from Start or Settings for private key configuration and a connection test. The launcher supports explicit recovery AI opt-in with --ai; full requirement review runs in Angular. See the AI setup documentation.
Go deeper.
Your next move starts locally.
Open source. Optional AI. You set the direction.