Repository navigation
Nestor 0.7.7 — first release aimed at users outside the author's setup. Verified on a fresh Claude Code 2.1.296 profile (empty config dir, empty project, pal built from scratch, one live quick consultation).
Install (three commands)
claude mcp add -s user pal -e OPENROUTER_API_KEY="$OPENROUTER_API_KEY" -- uvx --with "mcp<2" --from "git+https://github.com/dkushnikov/pal-mcp-server.git@61d869f421e65a8bf163f59e62df880cd2d05092" pal-mcp-server
claude plugin marketplace add dkushnikov/nestor-plugin
claude plugin install nestor@nestor-pluginThen, in a session: «Ask Nestor for a quick check: any obvious mistakes in this idea — …». Before sending files to the council, set the model registry (references/setup.md §1, example file included).
What changed since 0.7.4
- Execution contract fixed after an external audit (0.7.5): seat restoration policy in one place, partial-roster rules per mode, router invariants (deliberative stage 1 is neutral; explicit role stances + deliberative → clarification, never a hybrid),
stage2labels for every outcome, eleven router acceptance cases. - Every final answer opens with its route (
Route: <mode> · <preset> · <stances> · rule <base>[ + 0: <fields>]) — hosts that show no intermediate output (claude -p, bots) otherwise lost the announcement. - Model registry shipped as an example (
references/openrouter-models.example.json, 25 ids = presets + fallback chains) with a test that fails when a roster id has no entry. Without a registry pal assumes a 32K window and silently drops most files from the packet — now documented where it bites. - Setup rewritten from a clean-host run: the OpenRouter key travels in the
claude mcp add -ecommand; pal fork pinned to a commit (tagv9.8.2-citations.1); measured start times; what a local-path install reads (the source, in place) versus a GitHub install (a cached copy keyed by this version string). - Manifest moved to
plugins/nestor/.claude-plugin/plugin.json, the location Claude Code documents — updates are now keyed by the version string. Installs from 0.7.6 or earlier show a commit SHA as their version; that is history, not a stale copy. - Binding stated as a product decision: pal
consensusis the execution contract, OpenRouter the single gateway, rosters are spec-level. Another gateway or your own roster is a fork today — open an issue if you need one. - Issue templates: Consultation report (what changed because of the council — the pilot's unit of feedback) and Install problem.
Known limits
Synthesis runs in your own session (not architecturally isolated); the router is a model reading rules and can mis-route (the route line makes it visible and overridable); a quick run costs cents on OpenRouter plus the chair's own tokens (≈$0.36 on Opus 5.5 via API in the reference run). Full list: README → Limitations.