CapyAgent an agent that walks into your business systems itself. Go core, Python connectors, your data stays with you.
Install
The core is a single Go binary with no runtime. The connectors are Python files from the standard library. Beyond Python and the binary itself there is nothing to install.
The statuses below are not marketing. Where there has been no live run, it says so: promising that something works without running it on a machine is not a promise.
Platforms
Linuxverified
Go 1.26+, Python 3.12+, Git
The main platform. The core runs as a systemd service on a production server, scheduled jobs execute, and a channel crash is picked up by the service manager.
$ git clone https://github.com/nobi-k/interclaw && cd interclaw$ make build$ ./bin/interclaw setup
Windowscross-build
Windows 10/11, Python 3.12+
The cross-build and the installer are produced, and the Python interpreter is chosen during setup. We have no live machine to run it on, so we do not write «works».
$ make build-windows
Serververified
systemd, a dedicated service user
The working mode for a pilot: a service under its own user, ProtectHome=true, plugins and skills stored in the data directory rather than in a home folder.
$ systemctl status interclaw
Browser extensionverified
Chrome or compatible
A panel beside the page. It reaches only the core's local address and only with a token: a port without a token is reachable by any open tab.
Web interfaceverified
any browser
The chat page is served by the core itself on 127.0.0.1. The address is nailed into the code and is not exposed outward.
$ ./bin/interclaw serve
Androidskeleton
-
The client skeleton is in the repository but has never once been built: the build machine has no SDK. Calling it an application would be wrong.
After install
01 model
MiMo, any OpenAI-compatible API, YandexGPT or GigaChat. The key goes through the environment, not through process arguments.
interclaw setup
02 channels
Telegram, Discord and the Bitrix24 chat. Each needs its own token. Telegram from Russia comes up through SOCKS5.
INTERCLAW_TELEGRAM_TOKEN
03 connectors
Each connector receives only its own variables. Credentials for one service are invisible to the connector of another.
/etc/interclaw.env
04 policy
The list of tools that require confirmation and of sites where browser actions are permitted. An empty list means «nowhere».
BROWSER_ACTIONS_ALLOW
05 schedule
In plain words: «every Monday at 9:00». The agent executes it and the result arrives in the channel where you set it.
interclaw schedule
06 plugins
Installed by command, they request permissions through a manifest, and their contents are pinned by a lock file.
About skillsQuestions
The step-by-step walkthrough from zero to the first answer takes fifteen minutes.