Skip to content

v1.4.0

Choose a tag to compare

@github-actions github-actions released this 29 Jun 00:32

What's Changed

Features

  • Free OpenRouter council: A new amicus setup option that builds a zero-cost council from OpenRouter's free :free models. Run it with amicus fanout --council free or via the amicus_fanout MCP tool's council parameter. The wizard detects free models live from the catalog, lets you pick a vendor-diverse set (or takes sensible defaults), and saves them as councils.free — a first-class config primitive with collision-safe free-* aliases. Free models are rate-limited and quality-variable; the wizard discloses these caveats and the data-sharing requirement. Your config.default stays untouched, and you only need an OPENROUTER_API_KEY.

  • Council member graceful degradation: When a council member is delisted from the catalog, it's dropped with a warning instead of failing the wave, as long as at least 2 members survive. This keeps the council running robustly even as free-tier models change.

  • Setup wizard free-council picker: Both the readline wizard and Electron setup UI now offer a dedicated step to configure the free council, with multi-select model picking and inline disclosure of free-tier trade-offs.

  • CLI and MCP council presets: The amicus fanout CLI and amicus_fanout MCP tool both accept --council <name> / council parameter to run a saved council instead of listing models inline. The second-opinion skill reads councils.free automatically.

Improvements

  • Site redesign and polish: Refined hero section with Amicus rail-yard identity, improved card hover effects with glow, added floating swarm illustration, and more generous spacing across sections for a cohesive visual refresh.

  • Config read-modify-write: createDefaultConfig now preserves all pre-existing top-level keys (like councils) instead of clobbering them, ensuring setup operations never lose user data.

  • Documentation and transparency: Added inline notes in the second-opinion skill documenting free-tier usage and added a detailed implementation plan and design spec to the docs for full transparency.

Full Changelog: v1.3.0...v1.4.0