cd /news/ai-agents/show-hn-catt-0-2-1-test-agents-servi… · home › topics › ai-agents › article
[ARTICLE · art-155660] src=github.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Show HN: CATT 0.2.1: Test agents/services against a Muse/Instinct-alike, in CI

A team has open sourced CATT 0.2.1, a Consumer Agent Testing Tool that lets developers test their services against a surrogate Muse or Instinct agent, with runs executable in local builds or CI with or without LLM backing. CATT records full interactions including tool calls and responses so testers can diff what happened from what the agent reports, and it labels its assumptions about assistant-specific behavior as `documented`, `unofficial`, `assumed` or `unknown`; the tool is not affiliated with Muse or Instinct. The release targets reproducibility problems caused by agent memory and account statefulness when building APIs or MCP connectors for proprietary assistants.

read2 min views4 publishedOct 22, 2026

Hey HN, we recently open sourced our Consumer Agent Testing Tool to help teams iterate against proprietary assistants like Muse and Instinct. We built this to reduce our own frustrations with building an MCP/API for these agents to consume.

The problem: testing against these tools is hard! Agent memory + account statefulness make reproducibility, in the ways required for repeatable/reliable outcomes, between agents and the APIs/MCPs they interact with very challenging.

The solution: CATT lets devs test their services against a surrogate Muse or Instinct agent (not affiliated with either of these companies). Testers define starting conditions, approvals, and success conditions for their service's state. CATT then records the full interaction (incl. tool calls, responses) so it can diff what happened from what the agent reports. Runs can be tested in local builds or via CI, with or without LLM backing.

CATT is designed to emulate the important parts of personal assistant interactions. Its got:

  • Tool calls and command-line tool access - Simulated approvals for service actions - Outcomes tracking and comparison - Optional MCP profile based on an unofficial Muse template

There are limitations to how much we know about different assistant specific behaviors so the tool labels its assumptions as documented, unofficial, assumed or unknown for developer review. We'll do our best to keep the tool updated as new insights about the internal workings of these assistants come to light. It is an area of active research and interest, a good example is this recent report on how Instinct uses Exa for web search [0].

Are you building a connector or MCP? If yes, we'd like to hear from you! Have you had assistants behave incoherently, use stale information, or procalim success without evidence? What else should we add tests for?

The best way to get started is...to point your coding assistant at the repo and ask it to integrate the tool with your CI or local testing pipeline!

Hope it's helpful!

[0]: [https://www.sunbeam.ai/thoughts/instinct-is-using-exa-for-we...](https://www.sunbeam.ai/thoughts/instinct-is-using-exa-for-web-search)

Comments URL: [https://news.ycombinator.com/item?id=50201860](https://news.ycombinator.com/item?id=50201860)

Points: 1

── more in #ai-agents 4 stories · sorted by recency
── more on @catt 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/show-hn-catt-0-2-1-t…] indexed:0 read:2min 2026-10-22 · —