Hermes Tweet

> Xquik is an independent third-party service. Not affiliated with X Corp. > "Twitter" and "X" are trademarks of X Corp.

Native Hermes Agent plugin for X automation through Xquik.

Hermes Tweet brings X search, account reads, tweet posting, replies, likes, retweets, follows, DMs, monitors, webhooks, draws, extraction jobs, media, and trend reads into Hermes as structured tools.

Use it when you need a Hermes Agent Twitter plugin, Hermes X automation, social media automation for agents, or a native Hermes toolset for X/Twitter.

Highlights

• Published Python package with a native Hermes plugin entry point.
• Installable from PyPI as hermes-tweet.
• 99 agent-callable Xquik endpoints generated from OpenAPI.
• 31 MPP-tagged read endpoints in the bundled catalog.
• Read and action tools are split for least-privilege operation.
• Action endpoints are disabled by default.
• Bundled Hermes skill for agent-facing usage guidance.
• Slash commands for account status and trends.
• Current guidance for Hermes Agent v0.16.0 Desktop, remote gateway, and dashboard credential workflows.
• Strict CI with formatting, linting, type checking, tests, coverage, security scan, dependency audit, and package build checks.

Install

Recommended Hermes plugin install:

hermes plugins install Xquik-dev/hermes-tweet --enable

Hermes Agent treats third-party plugins as opt-in. Without --enable, the installer can discover Hermes Tweet, but it may leave the plugin in the not enabled state until you run hermes plugins enable hermes-tweet or toggle it in the interactive hermes plugins UI. Use hermes plugins list when a fresh install does not show the hermes-tweet toolset.

Hermes will prompt for XQUIK_API_KEY during an interactive install and save it to ~/.hermes/.env. In non-interactive installs the prompt is skipped; set the key through the environment or ~/.hermes/.env before running tweet_read. If you edit ~/.hermes/.env while Hermes is already running, use /reload in an interactive CLI session, or restart gateway and cron sessions before calling tweet_read. When XQUIK_API_KEY is not configured, Hermes should expose only the no-network tweet_explore tool from this plugin. That is expected safe gating, not an install failure.

Install the published Python package from PyPI into the Hermes Python environment:

uv pip install --python ~/.hermes/hermes-agent/venv/bin/python hermes-tweet
hermes plugins enable hermes-tweet

If your Hermes venv includes pip, this path is also valid:

~/.hermes/hermes-agent/venv/bin/python -m pip install hermes-tweet
hermes plugins enable hermes-tweet

From a local checkout:

hermes plugins install file:///absolute/path/to/hermes-tweet --force --enable

If you are testing from a project-local .hermes/plugins/ directory instead of installing the plugin into ~/.hermes/plugins/ or through the PyPI entry point, start Hermes with HERMES_ENABLE_PROJECT_PLUGINS=true only for trusted repositories.

Hermes Agent v0.16.0 adds a native desktop app and remote gateway profiles. For a remote gateway profile, install and enable Hermes Tweet on the remote Hermes host because that is where plugin code executes and where XQUIK_API_KEY must be available. The desktop app is the chat surface; it should not receive or store the key unless it is also running the Hermes runtime locally.

Python Package

Hermes Tweet also ships source-native .codex-plugin metadata, a root security policy, a local composer icon, and a HOL Plugin Scanner workflow for Codex plugin catalogs that require local validation evidence before listing.

Configure

Create an API key in the Xquik dashboard, then set:

export XQUIK_API_KEY="xq_..."

Optional settings:

export XQUIK_BASE_URL="https://xquik.com"
export HERMES_TWEET_ENABLE_ACTIONS="false"