Local-first RocketScooter level and display-context capture feeds.
RS Levels lets a user capture level and display-context data from their own RocketScooter browser session, normalize it locally, and expose it through localhost APIs for display tools and charting-platform plugins.
RS Levels is organized around three display-only pieces:
- Browser extension: captures allowlisted RocketScooter display data from the user's own browser session, provides
Copy TradingView, scrubbed diagnostics, API docs links, and extension status/debug tools. - Local levels server: runs on
http://127.0.0.1:8765by default, normalizes the latest captured ES/MES and NQ/MNQ levels, exposes read-only JSON/text/SSE/OpenAPI endpoints, and can be explicitly configured for trusted private networks such as Tailscale. - Platform plugins, indicators, and studies: includes TradingView Pine scripts, Sierra Chart ACSIL studies, NinjaTrader indicators, Quantower indicators, Bookmap add-on sources, and VARIS Zones support using captured risk interval (
RI) where the platform can use it.
Screenshots are available for the main user paths:
- No trading strategy.
- No trade recommendations.
- No order entry, cancel, flatten, or broker execution.
- No account, PnL, batch, or trade-journal features.
- No redistribution of RocketScooter data.
Users must have their own RocketScooter access. This project only processes data already loaded in the user's browser and keeps it local by default.
Use this table as the repo map. TradingView users can start with the extension and Pine indicator; the local server is still useful for diagnostics, API docs, examples, and direct platform plugins.
| Use case | Start here | Then use |
|---|---|---|
| TradingView levels only | TradingView quickstart | TradingView reference |
| TradingView VARIS Zones | TradingView quickstart | VARIS Zones |
| Local API, diagnostics, examples, or private-network setup | Local API and extension setup | API, Networking |
| Sierra Chart, NinjaTrader, Quantower, or Bookmap | Local API and extension setup | Platform plugins |
| API clients or display adapters | API | Schema reference, display plugin contract |
| Packaging and release checks | Packaging | Release checklist |
The full documentation map lives in docs/index.md.
npm test
npm startPost public-safe demo levels after starting the service:
npm run demo:captureCreate a release directory:
npm run packageThe release output includes a source-style directory, a source zip archive, a standalone browser-extension zip, RELEASE-MANIFEST.json, SHA256SUMS.txt, and checksum sidecars.
Packaged users can start the local API with npm start or the wrappers in scripts/start-local-service.*.
OpenAPI spec: docs/openapi.yaml, also served at http://127.0.0.1:8765/openapi.yaml after startup. Local API docs: http://127.0.0.1:8765/docs.
Examples: examples/html-dashboard, examples/node-client, and examples/python-client.
Default service URL:
http://127.0.0.1:8765
apps/
browser-extension/
local-service/
packages/
schemas/
core-parser/
plugins/
manifest.json
sierra-chart/
ninjatrader/
quantower/
bookmap/
tradingview/
examples/
html-dashboard/
node-client/
python-client/
docs/
scripts/
Public-safe foundation in progress. The schema package, parser, exporter package, local service, browser extension, TradingView paste workflow, display plugin sources, VARIS Zones source artifacts, release packaging, and public validation checklist are implemented with tests. Remaining work is primarily field validation against live RocketScooter/platform runtimes, persisted service settings, and native app packaging.