Repository navigation
v2.10.0
Independent recommendations and verification records are easier to compare, and structured credential fields are now masked by name.
- Fix masking of opaque, short and non-string values under recognized sensitive keys, including nested objects and arrays. Ordinary identifiers such as
primary_keyremain readable; text-assignment masking keeps its existing rules. - Report observed replacements during file/diff preparation, brief rendering and result normalization. Older observations remain unknown. Consultants now provide synthetic examples using separate variables and boolean assertions, so masking does not destroy their reproduction code.
- Add a concise
recommendationseparate from stance. Matching stances can recommend different actions; older history stays explicitly undeclared. Comparison and individual retrieval retain the existing size limits through nine consultants. - Add
refutedand carry bounded evidence summaries into follow-ups. Partial checks stay unverified. Legacy local notes are not forwarded until explicitly recorded again. - Explain material gaps and changed requirements, and shorten the path from installation to the first question. Standalone plugin documentation now includes install, usage, contribution and license information.
- Make ESM test fixtures explicit for the earliest supported Node 22 release.
Install or update:
npm publication is pending the registry's one-time-password authentication. npm latest still resolves to 2.9.2. The GitHub release archive below contains v2.10.0 and can be installed directly.
npx -y --package=https://github.com/coz-a/severally/releases/download/v2.10.0/severally-mcp-2.10.0.tgz severally-mcp installThe installer updates the global runtime command and registered copies. Restart clients afterward. See the installation guide.
Validation on 2026-10-27 (JST): build, auto format, format check, ESLint, strict type checking and package-content checks passed. Linux/Node 24.20.0 ran 603 tests with 593 passes and 10 platform skips; Node 22.0.0 passed 587 with 16 platform/SQLite skips. Independent review found no Critical or Important issues. The development-candidate S3 comparison used five runs per version; all five refined received examples were reproduced using actual functions. These are narrow checks, not a competitive re-score or a latency superiority claim.
The existing Codex credential-path limitations remain documented: individual-file rename replacement, executable-containing roots and later legacy job homes are not fully covered. Live enforcement on Windows/macOS, first-login journeys, next-day continuation and the full competitive comparison remain unverified. The known generic redaction return-type annotation still does not express sensitive-property type replacement.
PR #20 and the merged main commit passed CI on Linux (Node 22/24), macOS and Windows (Node 24).
Real CLI checks on Linux/Node 24.20.0, 2026-10-27 (JST), using the host's configured models and a 180-second probe budget:
| CLI | Version | Consultation | Doctor |
|---|---|---|---|
| Codex | 0.164.0 | Passed | Passed |
| Claude Code | 2.1.311 | Passed | Passed |
| Antigravity | 1.4.7 | Timed out after configured quota fallback | Passed |
| OpenCode | 2.0.24 | Passed | Passed |
Antigravity exhausted the configured gemini-4-argon-high quota, used the operator's configured gemini-3.8-flash-high fallback, and did not finish the review in 180 seconds. This is not counted as a successful consultation. Doctor results describe only the observed probes; they do not erase the documented read gaps or establish all prohibited operations on every OS. Effective provider models/effort were not independently observed.