Thanks to visit codestin.com
Credit goes to github.com

Skip to content

v0.3.0

Latest

Choose a tag to compare

@kaspermarstal kaspermarstal released this 12 Apr 14:40
· 129 commits to main since this release
c492df8

This release introduces new capabilities for connecting Cellm to external systems and improves underlying integrations with model providers.

What's New

  • Add support for Model Context Protocol (MCP): You can now connect Cellm to MCP-compatible servers, allowing your Excel sheets to interact with external data sources or trigger actions via Cellm functions. Effectively, it turns Excel into a low-code automation tool, enabling workflows orchestrated directly from your spreadsheet. We're still trying to wrap our head around the possibilities this unlocks. They are freakin' endless.
  • Adopt Anthropic.SDK for Anthropic Calls: Previously, we rolled our own custom Anthropic client because of the lack of an official SDK. We've migrated our Anthropic integration to the community-driven Anthropic.SDK (github.com/tghamm/Anthropic.SDK). This decision was driven by Anthropic's adoption of this SDK for their official .NET MCP library. This move ensures better standardization, aligns Cellm with Microsoft.Extensions.AI patterns, and leverages ongoing community improvements.
  • Telemetry: To help us identify bug and understand usage patterns, we now send anonymized crash reports and model interaction details to Sentry. We never capture any data from your spreadsheet. Still, you can opt out of this at any time by adding the following to your appsettings.Local.json:
{
    "SentryConfiguration": {
        "IsEnabled": false
    }
}

Bug fixes

  • Fixed a regression that inadvertently broke the use of tools with AI models.
  • Adjusted the prompt caching mechanism to correctly invalidate the cache when tools are added or removed.
  • Tuned the default settings for the rate limiter (Retry and Circuit Breaker policies) to work together more effectively during periods of high activity. These defaults prioritize stability and avoiding upstream provider rate limits. You can always crank up the limits or remove them altogether, but aggressive settings may lead to more errors from the AI provider.

What's Changed

New Contributors

Full Changelog: v0.2.0...v0.3.0