v0.1.4 — Prompt Enhancement (PE) & Multi-Prompt Sequence (MPS)
Nexpath's first tagged release — born at AI Hackfest 2026 (MLH), now shipping the core of what Nexpath is built around: a local-first behaviour-guidance layer that catches what AI-generated work quietly leaves out, before it becomes shipped risk.
What's new
Prompt Enhancement (PE)
Every prompt gets a quality pass before it reaches your agent. PE reads your prompt, the current development stage, and relevant workflow signals, then rebuilds it into one editable, higher-quality prompt — your original intent stays intact, and missing pieces (scope, constraints, verification, rollback, acceptance criteria, safety confirmations) are added only when the task actually calls for them. No filler, no auto-send: you review, edit, or return to the original before anything goes out.
Multi-Prompt Sequence (MPS)
Bigger tasks rarely fit one prompt. When the work is complex enough, MPS decomposes it into a clear current task plus a compact, ordered sequence plan for what comes next — so multi-step changes stay structured across the whole sequence instead of drifting halfway through.
Both run automatically once installed, alongside Prompt Enhancement Feedback (PEF), the feedback loop underneath them.
Demo video
A demo video for this release is up on YouTube — watch Prompt Enhancement in action:
Agent support in v0.1.4
| Agent | Status |
|---|---|
| Claude Code | Fully supported — end-to-end tested |
| Cursor, Windsurf, Replit, Lovable, Bolt.new | Not yet supported — end-to-end testing planned for v0.1.5 |
Install
git clone https://github.com/hi0001234d/nexpath.git
cd nexpath
npm install
npm run build
npm link
# Register with your coding agent and verify
nexpath install
nexpath --versionRequires Node 18+. Full setup, configuration, and troubleshooting are in the README.
Privacy
Local-first by design. All data stays under ~/.nexpath/; only targeted classification calls leave your machine, and secrets (API keys, bearer tokens, PEM blocks) are auto-redacted before anything is stored. Telemetry is a separate install-time consent and can be disabled anytime.
Tell us where it breaks
This is a launch, and honest feedback shapes v0.1.5. Open a Discussion and tell us where the README lost you, where the install broke, or where an advisory fired at the wrong moment.