IronClaw
IronClaw is an open-source personal AI assistant maintained in the nearai repository. Its documented scope includes a browser interface, terminal interaction, persistent memory, tools and background routines. Running it requires selecting and configuring a model provider; installing the assistant does not make that provider's usage free.
Choose a release and configure the instance
The README provides installers and prebuilt releases for macOS, Linux and Windows, plus a source-build route. Guided onboarding selects the model provider, stores its credential and creates local configuration. Review the chosen release and installation instructions before running commands downloaded from the internet.
The browser gateway exposes chat, memory, jobs, logs, extensions and routines. Terminal interaction reaches the same agent. Scheduled routines, event triggers and webhook handlers support recurring work, while parallel jobs use isolated contexts.
Start with a task whose result you can check, such as organizing a small set of notes. Background operation introduces a different responsibility from a single chat response: review what can run, which resources it can reach and how to stop an unwanted routine.
Separate local state from connected services
IronClaw documents local application state, encrypted secrets and hybrid full-text/vector memory search. It describes untrusted tools running in WebAssembly sandboxes with capability-based permissions, endpoint allowlisting and resource limits. It also lists Docker-isolated execution and MCP connections.
Those are documented security controls, not proof that a particular deployment cannot leak information. A chosen external model provider and connected tools have their own data-processing boundaries. Inspect permissions and provider terms before supplying sensitive documents or enabling actions on other systems.
Connect messaging only when needed
The channel overview currently documents Slack and Telegram. Setup separates administrator deployment credentials from each person's connection or pairing. Both channels receive webhooks, so the messaging platform must reach the instance over HTTPS.
That distinction explains why personal pairing alone cannot finish an unconfigured deployment. The documentation also states that Discord, Signal, WeChat and WeCom were available in version 1 but are not part of the 1.0 release. Do not treat an older integration list as current availability.
The project offers an Apache-2.0 or MIT license choice. This source review has not installed IronClaw, connected an account or tested sandbox enforcement. Its useful scope is a configurable assistant for operators prepared to manage credentials, deployment and connected-tool permissions.