blackopsrepl

GitHub profile1 plugin in the catalog

Plugins by blackopsrepl

1 plugins by blackopsrepl in the catalog, most-starred first.

blackopsreplsolverforge-routingPersonal multi-stop driving trips: tell Hermes where you need to go, review the places it finds, and a SolverForge constraint solver orders the stops on OpenStreetMap roads. Change plans in the conversation (skip a stop, choose the first visit, add a place, finish elsewhere) and the trip is repaired, keeping visited stops, the next stop and before rules; an older solve never overwrites a newer edit, and results are labelled best-found, not proven optimal. Desktop: the road map beside the chat, a route card, a status-bar chip, Google Maps, Apple Maps and OpenStreetMap links, and one QR code at a time for the phone. Disclosure — `hermes solverforge-routing install` (or /routing install) downloads one engine binary for your platform from this repository's own engine-v0.2.2 GitHub release, built by its release workflow with a GitHub build attestation, and refuses it unless its SHA-256 matches the value pinned in engine_bin.py; the agent cannot start that download. Place searches the user asks for send the query and region to Nominatim (configurable with geocoder_url). The first solve in a new area sends a bounding box to Overpass to download OpenStreetMap roads; each solve then runs the engine once as a subprocess (JSON on stdin and stdout). The map pane loads OpenStreetMap tiles, which reveal the visible area and your IP to the tile servers. Opening a navigation link or scanning its QR code sends the stop coordinates to that provider. The route database, road cache and engine stay in <hermes home>/plugin-data/solverforge-routing/; a geocoder pacing lock file (a timestamp only, shared by all profiles) is kept in ~/.cache/hermes-solverforge-routing/. No credentials, no location tracking, no telemetry, no background process.Communitytools