Repository navigation
In-panel provider management and the DeepSeek Harness preview
Reroute 0.4.2 lets an existing configuration be repaired and extended from the /reroute panel, and ships the DeepSeek Harness adapter as a preview entry point in the same package. Pi remains the supported host for everyday use. The engine, router, provider SDK lines and cost rules are unchanged, so no new paid-cloud or model-selection acceptance is claimed here.
npm: @onedotmint/reroute@0.4.2 (latest), integrity sha512-QqOtC+9kSSYFbPIar8f5KrViVZjpVPqhuBxtxd45liTMs1vVgAxeKnGRx0xq30cVRlccQpNqy/90gz+iF7HP/w==
Changes from 0.4.1
- Manage providers without a terminal. With an existing configuration, Manage providers offers the same in-panel onboarding as first-run, plus Use a saved credential account, Enter missing API key (hidden input) and the previous wizard kept as Advanced terminal setup. Filling a missing key writes only that provider's credential file; profile settings and spending authorization are untouched.
- Spending authorization asks, and defaults to No. Authorization is an explicit
No — save without spending authorization/Yes — authorize paid creation/startselect. Escape cancels without saving.Nostill saves a usable profile that cannot create or start paid compute. - Quick onboarding no longer replaces billable references. A managed profile with recorded resources is refused by quick onboarding, because destroyed compute can leave billable storage behind. Keep the old profile/account and change it through Compute & budget.
- Project overrides stay project-scoped. Project-only onboarding, saved-account reuse and the E2B sandbox path write to the project override instead of the global user defaults.
- Masked input uses Pi's own parser. Paste, Kitty CSI-u keys and grapheme editing now match ordinary Pi text fields, and the value is still only ever rendered as a mask.
- E2B is reachable from first-run onboarding, alongside SSH, Daytona and Modal.
- DeepSeek Harness preview entry point. The package now also exports
./dshand shipscordis.patch.ymlactivating@onedotmint/reroute/dshfor Harness0.2.1-rc.5. Harness SDKs stay host-provided. This is a WIP preview: distribution is not qualification, and its evidence is Linux/Node 24 fixtures, not real-model or paid-cloud acceptance.
Upgrade
pi install npm:@onedotmint/reroute@0.4.2 # native Pi package, global by default
npm install -g @onedotmint/reroute@0.4.2 # optional standalone CLIThe old npm:...@0.4.1 specification stays pinned; select 0.4.2 explicitly, check pi list for obsolete copies, then restart or reload Pi. Updating the package does not grant project execution consent or spending authorization, and no credential/configuration migration or cloud resource operation is needed.
Verification
npm run verify(strict typecheck, build, 370 tests with 368 passed / 2 skipped, CLI smoke) passed on Node 24.22.1 / npm 11.19.1.- The packed tarball installed in a clean prefix under both the default and disabled install-script policies; the CLI smoke, a separately installed Pi 1.4 host loading
/rerouteplusreroute_run/reroute_status, and the SDK/CBOR-JS/protobuf probes passed. - CI passed on Node 22/24 × npm 11/12, real localhost SSH/rsync, real Pi/AFT coexistence, plus the limited Windows job.
- Production dependency audit: 3 moderate / 0 high / 0 critical. The pinned Pi and Harness SDK development/host tree keeps its disclosed high findings; this is not a zero-vulnerability release.
Limits
Not verified for 0.4.2: real paid-cloud runs, billing, broad fault recovery, standard Harness Web/Desktop UI, real-model tool selection, and Windows beyond the limited CI job. Historical 0.4.0 cloud measurements remain historical evidence and do not qualify the current dependency tree against the live services.
Assets
onedotmint-reroute-0.4.2.tgz — the exact tarball published to npm.
sha256 cf52a57a62bdf8675e6514faf1c43a5c85d154bbfb1ec8a36677dbfa280392b9
shasum b88146b0022163fadd3e08f7ea69f6a27c4da4b2