archivebox/archivebox-chat-bot repository overview

⁠🏛️ ArchiveBox Bot

• mention @ArchiveBox in any thread → saves all URLs found in the last 10 messages
• DM @ArchiveBox bot with any text → archives every URL in your DM
• Add @ArchiveBox to group chats → optionally archive all URLs shared in groups it's added to
• Auto-tags URLs with source info → slack,bob,reading-list (connector, user, channel name)

⁠Connect your chat apps

git clone https://github.com/ArchiveBox/archivebox-chat-bot.git
cd archivebox-chat-bot
docker compose pull
docker compose up -d

⁠Providers

⁠Slack

• Connect: choose Create Slack app in the Chatbot Admin Console → install the preconfigured app → follow the two screenshot guides to paste your Bot token (xoxb-…) and App token (xapp-…) → Save & connect.
• Use: invite the bot to channels; mention it in a thread or send a DM.
• Destinations: Save & connect creates New URLs + Saved URLs automatically. Socket Mode needs no public webhook.

1 · Set up the Slack app	2 · Configure the bot	3 · Mention in a thread

Or send a DM	Browse Saved URLs

Where to get Slack tokens

Create the preconfigured app	Allow it in your workspace

• Install the app: Slack app setup⁠.
• Copy the bot token: Slack token types⁠.
• Generate the app token: Socket Mode setup⁠.

⁠Discord

• Connect: create an app⁠ → Bot → Reset Token → paste token into the Chatbot Admin Console.
• Enable: Bot → Message Content Intent → Save Changes → Find my bot → Add to Discord → select your server → Save & connect.
• Use: DM links, mention the bot in channels/threads, or use /archivebox save, search, auto, status, help.
• Destinations: New URLs + Saved URLs are created automatically; choose existing channels under bot preferences. No public webhook.

1 · Get your bot token	2 · Enable Message Content	3 · Add to your server

Official setup⁠ · Message Content Intent⁠

4 · Choose channels & preferences	5 · Browse Saved URLs

Live Cabbage check (2026-10-08): A channel mention, capture-bot DM, and AI DM were handled. All tested Ars Technica URLs resolve to snapshots whose captured response is 403 Forbidden; replay shows that error instead of article content.

Capture-bot channel mention	Capture-bot DM	Saved URL cards	AI DM reply

⁠Zulip

• Connect: create a Generic bot⁠ → copy bot email + API key⁠ → enter your server URL.
• Use: topics, mentions, DMs; create private New URLs + Saved URLs channels.

1 · Copy bot email	2 · Copy API key	3 · Browse Saved URLs

Live Cabbage check (2026-10-08): The stream mention and AI DM flows were handled, but both Ars Technica URLs already had snapshots showing 403 Forbidden. The AI reply reported that ONLY_NEW skipped a retry, so these results do not show captured article content.

Capture-bot stream mention	Saved URL results	AI DM reply

⁠Telegram

• Connect: BotFather → /newbot⁠ → copy token → add to group.
• Groups: disable bot privacy⁠, then remove/re-add the bot for group-wide capture.
• Commands: /save, /search, /auto, /status, /help; polling needs no public webhook.

1 · Add to your group	2 · Choose bot preferences	3 · Save references

⁠WhatsApp

• Connect: Settings → Agents → Create an agent → View API key⁠ on your primary phone.
• Groups: choose QR pairing → Linked Devices → Link a Device⁠. Agent keys⁠ support creator DMs only.

Live Cabbage check (2026-10-08): A real WhatsApp Agent DM used /archivebox save with two Ars Technica URLs. The DM confirmed the request, and the Cabbage console recorded two saved URLs and a completed message. Both snapshots contain Ars Technica's HTTP 403 Forbidden response, not article content.

Real WhatsApp DM	Cabbage saved result

⁠IRC

• Connect: server + nickname + channels⁠ → register an account⁠ → SASL⁠.
• Use: mentions, private messages, auto-archive channels; saved cards use text links.

1 · Configure the bot	2 · Browse Saved URLs

Live Cabbage check (2026-10-08): In the signed-in Lounge UI, ArchiveBoxTester mentioned ArchiveBoxCapture in #new-urls and sent two Ars Technica URLs in a capture-bot DM. Both captures completed, and the saved channel shows three result cards: April channel snapshot 06ac7719f3997373800022139b4a76f3, plus the April and October DM snapshots 06ac76f04b0473098000a102ed4bd265 and 06ac76f04b047f6780006432632c6c0f. Each result is titled 403 Forbidden; the snapshots contain the origin's error response, not article content. The IRC AI bot was configured through the console at ergo:6667 (plain IRC, no TLS), after its old 127.0.0.1:16667 endpoint failed. Its request created snapshots 06ac76358bae7ed78000c4cfe72049be and 06ac76358baf7cb88000cdb323aa1f0e, also HTTP 403. The AI used the normal CLI's --no-only-new option because ONLY_NEW skipped URLs with existing snapshots. In the capture job records, num_snapshots remained 0 even though their results listed the snapshot IDs.

Channel mention	Capture-bot DM	Saved snapshot result

⁠iMessage

• Connect: install imsg⁠ on a Mac → Full Disk Access + Messages Automation⁠.
• Use: existing conversations; local Mac or Docker → SSH.

1 · Enable Full Disk Access	2 · Allow Messages Automation