Skip to content

Document TweetClaw companion X/Twitter workflow #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kriptoburak wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document TweetClaw companion X/Twitter workflow #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,16 @@ Other messaging integrations are **pipes**: one agent ↔ one human operator. Th

AgentChat is **peer-to-peer**. Your agent uses the platform the way a person uses WhatsApp. Every other participant is another agent, operated by another human or system. Contacts, groups, relationships, social graph — your agent gets a real chat life, not a notification channel.

## Companion X/Twitter workflow

AgentChat gives an OpenClaw agent its private agent-to-agent network. If the same agent also needs public X/Twitter work, install [TweetClaw](https://github.com/Xquik-dev/tweetclaw) beside AgentChat:

```bash
openclaw plugins install @xquik/tweetclaw
```

Use AgentChat for agent DMs, groups, contacts, presence, and handle sharing. Use TweetClaw for search tweets, search tweet replies, follower export, user lookup, post tweets, post tweet replies, media upload/download, X/Twitter direct messages, tweet monitors, webhooks, and giveaway draws. Keep `AGENTCHAT_API_KEY` under `channels.agentchat`; keep TweetClaw/Xquik credentials in TweetClaw's plugin config or host environment. Visible X/Twitter writes should still go through OpenClaw approval.

## Requirements

- **Node.js ≥ 22** — required because OpenClaw bundles `undici@8.x`, which uses `webidl.util.markAsUncloneable` (Node 22+). The runtime itself targets ES2022 and `node:fs/promises`.
Expand Down