REBOUNDOPS / LOCAL DEVELOPER PREVIEW

Getting started

Install once, start the local demo and complete a fictional first journey.

Before you begin

Install Git, npm and a supported Node.js runtime. Node 24.15+ on the 24.x line is recommended; the root application also supports Node 22.22.3+ and Node 26+. The integrated launcher needs Bash and curl. On Windows, use WSL for the launcher.

Install and run

git clone https://github.com/AnkitParekh007/rebound-ops.git
cd rebound-ops
npm ci
npm ci --prefix workspace --ignore-scripts
bash scripts/start-demo.sh

Open http://127.0.0.1:4317/#/start. Keep the terminal open; press Ctrl+C to stop both services. The launcher builds the recovery API, binds services to loopback and leaves AI off unless you explicitly opt in with --ai. See AI setup.

Your first five minutes

  1. Choose Use a fictional example on the start screen.
  2. Review the experience and available time, then create a plan.
  3. Explore directions and select one to test.
  4. Open the search workbench, browse opportunities and inspect the application tracker.

The example is synthetic. Visible application statuses and job scores demonstrate the interface; they are not customer outcomes.

Choose the interface you need

Use the integrated demo for recovery followed by job-search tools. For the fuller evidence, source-quotation and backup controls in the Angular recovery app, run this from the repository root instead:

npm run dev

Open http://127.0.0.1:4200. Stop the integrated demo first to free API port 4174. For a compiled local recovery app, run npm run build, then npm run start -w @reboundops/api and open http://127.0.0.1:4174.

If something does not start

  • Port in use: stop another ReboundOps process. The integrated demo uses ports 4317 and 4174; Angular development uses 4200 and 4174.
  • Recovery service offline: check the launcher terminal and restart both services with bash scripts/start-demo.sh.
  • Unsupported Node version: check node --version against the requirements above, then reinstall with npm ci.
  • Session gone after restart: memory-only sessions do not survive API restarts. Read Data and backups before using personal records.

More detail: integrated demo guide ↗. Report problems with your OS, Node version and redacted error text; exclude private records and keys.

Documentation lives with the code. Suggest a correction ↗.