Skip to content

Release 0.0.5

Latest
Latest

Choose a tag to compare

View all tags
@ripienaar ripienaar released this 25 Aug 17:36
· 19 commits to main since this release
v0.0.5
This tag was signed with the committer’s verified signature.
ripienaar R.I.Pienaar
GPG key ID: 02E5780DF1BC6F01
Verified
Learn about vigilant mode.
7a25efd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Channels

Channels are ways to access an agent via remote network protocols. The fisk serve command serves the Agent on one of multiple network Channels concurrently. This allows you to to isolate the Agent in a sandbox while connecting using different UI's and delivery methods to the Agent.

This release includes the following Channels:

  • A Slack channel allowing your agents to participate in Slack threads - each thread is a separate session with separate context
  • An Async Jobs chanel allowing messages to be consumed via a durable execution system complete with retry, session resumption and more
  • A NATS based A2A channel allowing agents to be contacted via a NATS client

The NATS protocol is full featured featuring Elicitation, Identity, HITL, Streaming and more.

The fisk run UI - both CLI and TUI - now supports connecting to remote agents via the A2A protocol and even in the default single process mode embeds the agent and access it over A2A.

Using these capabilities many clients can connect to a cluster of fisk serve and scale horizontally and vertically.

Coupled with JetStream based Session and Memory stores these agents can be hosted in different AZs for high availability.

Read more about Channels

MCP Client

While we make it very easy to add local tools and even serve those over MCP it's unrealistic to add all tools one might want in this manner.

Therefore we now support pulling in tools from MCP Servers both stdio and HTTP based including the recently announced stateless HTTP kind.

This allows you to integrate Fisk into countless 3rd party services.

As ever we focus on privacy and safety so the tools that you actually adopt from these services can be filtered against include and exclude lists so you have full control.

Read more about Importing from MCP Servers

PII Detection

We have on-by-default PII detection using Ferret Scan, this detects and redacts many kinds of PII like email addresses and more.

Any prompt input and tool call output is PII redacted by default and the model never sees the data.

This is obviously best-efforts, universal PII detection is not a thing so we are only as good as Ferret Scan plus a few we added ourselves.

The PII Detection can be put to enforcing meaning it will terminate any session that accesses PII or you can turn it off.

This further positions Fisk AI as a by-default privacy preserving harness.

Enhancements

  • Allow tools to have behavior hints mapping onto the MCP
  • Expose run state info
  • Introduce the concept of Channels
  • Adds a A2A over NATS Channel
  • Adds a Slack Channel
  • Adds a Async Jobs Channel
  • Turn the CLI into a A2A Client and support remote Agents
  • Add herdr support
  • Set FISK_AI=1 when calling tools
  • Add on-by-default PII redaction
  • Adds a MCP client

Full Changelog: v0.0.4...v0.0.5

Assets 19
Loading