if xHermesBot could plug into one external thing your agent doesn't have yet — what's the first? reply with the integration. top-voted one ships next sprint.

Authentication infrastructure update. All onboarding paths now run through Auth.js, including X, GitHub, Discord, and wallet authentication. We've removed the legacy authentication stack, expanded audit logging, and simplified the provisioning flow moving forward. Next up: Telegram authentication. Since Telegram uses a non-OAuth HMAC login flow, it requires its own implementation and onboarding specification. Slowly reducing friction. One update at a time. xHermes.cloud

fuck yes... finally all auth providers are working flawlessly... rewrote all auth module to use auth.js library, crsf cookies are finicky, but got it all working, pushing soon to production.

192 active operators. Still shipping. The market is cooked. The platform isn't. Back to work. xHermes.cloud

no, i didn't disappear, all good - nothing's wrong. go touch grass, enjoy the sun (for those of you who have it) on sunday. agents are running, platform is working - hermes never sleeps, never stops. what's next: - multi-provider auth. still reworking the middleware - telegram github first, then discord. - self-healing updates also coming: it'll pull :latest and upgrade itself, so you can do self-update on docker. quiet ≠ stalled. just building.

never waste a good crisis

Next up: Social Auth. We're simplifying operator provisioning while keeping access tied to the ecosystem. Users will soon be able to sign in through supported social accounts such as Google, Telegram, GitHub, with additional providers rolling out over time. Access requirements remain the same: Hold 1M xHERMES in your linked wallet, or stake 1M xHERMES to provision and operate agents. One account. One operator. Ready to build. xHermes.cloud

xHermes update is out. Stake-to-access tier 3 is live: Pro Workdir. - 2 GB workdir free - 10 GB workdir for only 7M $xHERMES staked - Enforced at the kernel level - 14-day grace if you drop below the threshold - Files always survive a downgrade

Expect a 10 minute downtime on EU region agents while rolling over the filesystem.

New update now live. Users staking on Tier 2 can now migrate agents between regions. Simply choose a destination region and your agent snapshot will be transferred to the new host automatically. We've also updated the documentation to reflect the new migration flow and platform changes. As we continue expanding global infrastructure, we're focused on making it easier to move operators closer to where they're needed. Deploy. Automate. Scale. xHermes.cloud

Coming soon to xHermes: We’re exploring a utility-focused staking model for xHERMES designed around real infrastructure benefits for our users. Planned features include: - Agent snapshots and backups - Larger working directories and additional storage - Region migration across server zones - Early access to upcoming platform capabilities The objective is simple: align token utility directly with the infrastructure and tooling people actively use on xHermes. More details coming soon. xhermes.cloud

first thing - no point to engage with profiles without blue checkmark, just larps...

Safari login issue has been fixed. Some users reported authentication problems specifically on Safari, traced the issue down to Safari’s ITP purging cookies during the X authentication redirect process, and moved the session handling server side. One trip, you’re in. Appreciate everyone that reported the issue. These reports genuinely help us improve stability as more users and operators come online. xHermes.cloud

Region selection is now live on xHermes. When provisioning a new agent, users can now choose which region their autonomous operator runs from globally. This allows lower latency, faster response times, and infrastructure closer to where users actually are. This is a small but important step toward making a better user experience for users. xHermes.cloud

Tired of dashboards and just want to use xHermes from your terminal? Introducing xHermes CLI. Connect directly to your persistent agents from your local environment with a simple developer-first workflow. source · github.com/xHermescloud/cli install · npx @​xhermes/cli releases · auto-published from CI and Sigstore signed Your agent. Your terminal. xhermes.cloud

Just a small sneak peek for the upcoming, xHermes CLI tooling. Already have a provisioned agent but want to use it directly from your terminal instead of the dashboard? No problem. We’re building a CLI layer that lets you connect directly to your persistent Hermes agent from your local terminal without needing to manage VPS infrastructure, deployments, scripts, or backend setup yourself. Shipping soon!

We’ve officially submitted the xHermes CoinMarketCap application. Request number: 1366518 xHermes.cloud

We just submitted for @JupiterExchange Fast Track. xhermes.cloud

confirmed. persistent agents are real infrastructure now