IronClaw lets users control what each tool is allowed to do.
Tools can be set to Always Allow, Ask Each Time, or Disabled. If a tool isn't needed, it can simply be turned off.
A simple way to keep control over what your AI agent can access.
IronClaw 1.2 now understands more of your Slack conversation.
When you mention IronClaw in a channel, it can read the last 30 messages. In a thread, it can read up to 100 replies.
So you can ask questions without explaining the whole conversation again and those messages are used only for context, not as instructions.
IronClaw 1.2 brings better conversations to Slack and Telegram, with more context and less setup.
It also improves how multiple approval gates are handled, while adding reliability fixes for Windows startup, secrets handling, and container health checks.
◽ Check out the full release notes for IronClaw 1.2 here
Joe, a NEAR dev, recently shared a walkthrough of IronClaw and how it can be used for research.
One key feature he highlights is that API keys stay in a secure vault that the model can't directly access.
If you're curious about how IronClaw works, check out the full video: https://youtu.be/JEZ2HxkqBUA?si=EI3Dm-BWBisKcXVb
Your $NEAR stake can give you access to run an IronClaw AI agent.
Sensitive credentials stay protected, while agent tools run in isolated WebAssembly environments.
Private. Secure. Built for real AI work.
Encryption protects your data, but AI agents still need to process it.
IronClaw uses Trusted Execution Environments (TEEs) to keep sensitive data protected while the agent is running. The host and admins can't simply see what's happening inside, and the environment can be independently verified.
A NEAR dev, Joe made a video explaining how this works and why it matters for secure AI agents 👇
https://x.com/joespano_/status/2087539372115562497
IronClaw agents now have their inference independently verified by Intel Trust Authority.
IronClaw already keeps credentials isolated from the model. Now the inference layer can also return an Intel-signed token that can be checked independently.
Another step toward making agent security verifiable from the ground up.
Self-sovereignty isn't just about owning an asset. It's about having that asset give you access to the network and compute you need.
With NEAR staking, you can receive an IronClaw subscription or inference credits.
Instead of simply paying for compute, you hold the asset that gives you access to it.
AI agents need real access to be useful, but that also creates security risks.
IronClaw keeps credentials protected, tools isolated, and secrets away from the model.
AttackBench tested major agent frameworks across 52 attack scenarios.
A NEAR dev, Joe tried giving IronClaw his Gmail password to see what would happen.
IronClaw refused and warned them not to share passwords with an AI agent. He tried twice more, and it gave the same response.
Then he checked the logs and started a fresh conversation. The password wasn't there. A simple test, but a useful look at how IronClaw handles sensitive information.
IronClaw 1.0 supports multi-tenant teams and fully isolated deployments. Teams can share tools and skills, so useful workflows can be reused instead of rebuilt.
Admins can manage the deployment without automatically seeing individual private workspaces. When access is required for compliance, it follows an auditable process.
And for teams that need complete separation, single-tenant mode keeps everything isolated with no external access.
NEAR Dev, Joe set up a daily automation in IronClaw to get every Massachusetts pro sports score at 9 AM, along with game results and trade news.
IronClaw built the workflow, asked for confirmation, and checked a few details before scheduling it.
After approval, updates were sent directly to Telegram or Slack. The same approach works for any daily task you want to automate.
IronClaw leads ClawBench with an 88.6% score, finishing 5.0 points above the field average and 4.7 points ahead of the next-best model.
ClawBench tests AI agents on 140+ real websites with complex, multi-step tasks instead of sandbox environments.
The results show that IronClaw is built to handle real work, not just simple demos.
Setting up Slack with IronClaw 1.0 in six easy steps.
Open a Slack app, then copy:
Basic Information → App Credentials → App ID
Slack Workspace ID → Team ID
OAuth & Permissions → Bot Token
Basic Information → App Credentials → Signing Secret
OAuth & Permissions → App Credentials → OAuth Client ID & Secret
Paste these into IronClaw → Extensions → Channels and click Save Channels.
Your IronClaw agent is now ready to securely respond in Slack channels and DMs with the same memory and security across every conversation.
IronClaw 1.0 now works the same on CLI, Web, Slack, and Telegram. You can start on one platform and continue on another.
Your assistant keeps the same memory and the same safety rules wherever you use it. You don't need to start over or set things up again.
When IronClaw adds support for new platforms, they automatically get the same security and features. One assistant, the same experience, everywhere.
IronClaw remembers your conversations, preferences, and past context, making every interaction more useful.
It can also create new sandboxed tools when needed and reuse them later, so your agent keeps improving over time.
That's what makes IronClaw feel like a real long-term AI agent.
IronClaw 1.0 includes a growing collection of built-in system skills that help with coding, code reviews, delegation, automation, content creation, workflows, Team-management and more.
These ready-to-use skills reduce setup time, making it easier to customize your agent and start building productive AI workflows right away.
From a single dashboard, you can review and manage permissions for built-in tools like HTTP requests, shell commands, JSON, time utilities, subagents, and more.
Instead of giving every tool unrestricted access, you decide how your agent should behave.
More control. Better security. Smarter AI agents.
Setting up Telegram with IronClaw 1.0 is surprisingly simple.
Your IronClaw 1.0 is now ready to work with you directly through Telegram.
Fast setup, no complicated configuration.
IronClaw 1.0 is officially here, introducing a major upgrade to how AI agents operate.
Key improvements include:
◽ A unified security checkpoint for every action.
◽ Goal-based execution with automatic task planning.
◽ Checkpointing that lets agents resume interrupted work.
◽ Persistent memory across sessions and channels.
◽ A consistent experience across CLI, Web, Slack, and Telegram.
◽ Support for both multi-tenant teams and fully isolated deployments.
IronClaw 1.0 is already powering agents across the NEAR Foundation and NEAR AI, and it's available today to deploy.
👉 Check out more detail here : https://near.ai/blog/introducing-ironclaw-1-0
