Skip to content

IRMind v0.5.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 11:04
· 240 commits to main since this release

IRMind v0.5.1 — Complete model responses and evaluation readiness

Format impact: Case, artifact, skill and export versions are unchanged. Model
replies in subagent branches may now use the available 1 MiB frame capacity;
other branch payload limits are unchanged. Model-token settlement accepts signed,
verified usage above an already admitted reservation without creating capacity.

  • Use native model output maxima instead of application token caps, with signed model capability settings for custom/local endpoints. Enforce case budgets between requests and retain completed responses and actual usage when they overdraw the balance.
  • Continue a provider-limited answer once without tools when budget permits, keeping one continuous answer. Retain full in-frame child replies separately from their 16 KiB parent summaries; label security-boundary prefixes explicitly.
  • Test model connections with the current unsaved provider, URL, model, key and output profile; probing does not save configuration or credentials.
  • Show case help in a scrollable view and resume the conversation at its end after the demo presentation.
  • Refresh the verified-install quick start and synthetic v0.5.0 images, and add clean-release PTY checks for Linux, macOS and Windows.
  • Add opt-in real-service validation and multi-model HuntEval development helpers. Prepare disabled tag-only Developer ID signing and notarization; native signing remains unavailable until provisioned and validated.

Known limitations

  • Pre-1.0 evaluation with synthetic data. A real DeepSeek greeting was accepted by the analyst; the remaining investigation procedure and a real connector validation are still pending. This is not a production incident-response validation.
  • Existing 1,000,000-byte guard, 2,000,000-byte stream and 1 MiB signed-frame limits remain. A retained prefix at a security boundary is labelled incomplete.
  • Native Developer ID/notarization and Authenticode remain unavailable; use the Sigstore bundles, exact workflow identity, GitHub attestations and SHA256SUMS.
  • No production catalog public key is compiled yet. Core skills remain available; catalog publication is separate.
  • Context/caching changes are design-only in PR #302.

See the configuration guide, real validation guide and verified installation instructions.