We just gave every Hermes Agent a free cloud browser.
Use the Browser Use ecosystem in Hermes Agent for free
> Unlimited browser hours
> Free proxies
> Persistent authentication
@NousResearch 🤝 Browser Use
Paradox: If you see a baby located 90 light-years from Earth, right now it would be a 90-year-old, but you see it in your present, as a baby.
While the light takes time to reach you, the baby grows and ages.
When you look at the universe, you are always looking at the past.
ByteRover is now live in the Hermes Agent memory update @NousResearch
One minute setup: just run hermes memory setup and your agent gets memory.
Fully open-source & local, no cloud API keys. Built on native markdown architecture (validated by @karpathy), but we automated the entire curation (management) layer so memory actually scales with your projects.
Prompt as usual, and the agent will recall the exact knowledge and historical decisions.
Proven in real production with teams. Optimized for accuracy, latency & token reduction.
@MichaelParisi@NousResearch@karpathy ByteRover itself is fully local, The LLM API key prompt is for the LLM provider that uses to power the agent (OpenAI, Anthropic, etc.). The memory system runs on pure markdown + local compute, but the agent still needs an LLM to think with.
It looks like my @telegram iOS PR has been deployed (or something similar).
Now you can talk to your @openclaw via Siri / CarPlay on iOS.
1. Create an iOS Contact for "Claw" (or any name)
2. Add a URL field with name `Telegram` and value `@id12345" target="_blank" rel="nofollow noopener">t.me/@id12345` where 12345 is your bot's peer id
3. "Hey Siri, message Claw on Telegram" now works!
Note that you have to have an open chat with your bot already and you cannot accidentally start chatting with random bots with this design.
🦞 Openclaw update fix
If your agents are hitting exec approval walls after the latest update, the fix is three settings:
In exec-approvals.json defaults:
- security: "full"
- ask: "off"
- askFallback: "full"
In openclaw.json:
- tools.exec.security: "full"
- tools.exec.strictInlineEval: "false"
Then restart gateway.
The allowlist wildcard * alone isn't enough. There's a second policy layer that gates complex commands independently.
@steipete I keep getting 500 errors when using "/btw". Also the web ui dashboard at localhost:18789 hasn’t shown reasoning or chat updates without a refresh for a few updates now. Are these known bugs, or just an @ollama issue?