Skip to content

CapyAgent an agent that walks into your business systems itself. Go core, Python connectors, your data stays with you.

RUEN
Get started

Changelog

What changed
and why

Nine releases across ten days of development. There is no «stability improvements» line below: every entry answers the question of what exactly was breaking.

Project news Full journal

The full change journal lives in the repository and carries a list of honest limitations for each release.

v0.9.0current

in development

The day that added more checks than capabilities

Web search, the browser and skills in conversation. But the main thing is elsewhere: over three days the same thing happened eleven times - code written, covered by tests, green in CI, and nothing to invoke it.

  • Web search and page fetching: Yandex Search API v2, SearXNG and Brave under one result shape
  • Browser: reading script-rendered pages, and actions behind three locks
  • make check-wiring looks for things declared and called by nobody, and fails the build
  • You confirm a specific action, not a tool type: «click «Checkout» on avito.ru», not «run browser__browser_click»
  • Before clicking, the connector compares the label against the live page
  • The extension no longer grants itself permissions

v0.8.0

20.08.2026

The release that passed a full audit

The core runs as a service on a production server, scheduled jobs are executed by the agent, and a model outage no longer leaves you without an assistant.

  • Security audit: 21 findings closed
  • Scheduled jobs are executed by the agent, not by a stub
  • A fallback model provider when the primary one fails

v0.7.0

19.08.2026

Installs as a service and survives the night

The release from which the assistant can be installed as a service and used daily. Based on a readiness audit and a comparison with Hermes and OpenClaw.

  • A channel crash now brings the process down: previously the channel died, the service showed as active, and the bot stayed silent for days
  • Exits with a non-zero code, systemd restarts it
  • This is not a replacement for Hermes: the goal is to work alongside, not instead

v0.6.0

15.08.2026

The release about resilience

The assistant from v0.5.0 worked but did not survive load: one large connector response knocked out the dialogue, a long conversation lost its beginning, and the very first 429 reached the human as a refusal.

  • A tool result is capped at a fraction of the model window, and truncation is marked honestly
  • A long conversation is compacted rather than losing its beginning
  • The comparison with three foreign cores was done after implementation, not before: comparing beforehand produces a copy

v0.5.0

14.08.2026

InterClaw became a personal assistant

The channel accepts free speech rather than only commands: it holds a conversation with the model, remembers it, sets reminders and calls connector tools.

  • The agent loop: think, act, observe, with a mandatory ceiling on turns
  • Model providers: an OpenAI-compatible adapter, MiMo, YandexGPT, GigaChat
  • Memory, reminders and new channels
  • A tool invented by the model comes back as the text «there is no such thing» rather than crashing the loop

v0.4.0

13.08.2026

Channels

A shared channel layer appeared, with Telegram as the first implementation.

  • The sign of life is the time of the last successful exchange, not a «running» flag
  • Connections go strictly over IPv4 through our own dialer inside the process: fixing /etc/gai.conf would fix the whole machine, and on a client's machine that is not acceptable

v0.3.0

12.08.2026

Local interface and a token

interclaw serve brings up HTTP strictly on 127.0.0.1. The address is nailed into the code rather than taken from configuration: the core holds keys to other people's CRMs.

  • A token is mandatory and compared in constant time
  • A local port without a token is reachable by any open tab
  • CORS is allowed for extensions only

v0.2.0

12.08.2026

The Yandex.Direct connector

Four tools, written around four ways of losing data silently.

  • 201 and 202 mean a queued report, not an error
  • The error arrives in the response body with status 200
  • API limits are counted before the request, not after a refusal

v0.1.0

12.08.2026

The first working slice

The core can bring up a connector and call its tools, and the Bitrix24 connector can discover a portal and export data without losing it silently.

  • An MCP client over stdio: handshake, tools/list, tools/call
  • CLI: version, connector tools, connector call
  • Portal discovery before analysis

Want to know when the next one ships?

Write to us and we will tell you about the release that closes your task.

Write to us Project news