ASSA lets you get timeline digests and have conversations with people on X (formerly Twitter)via rich UI components. Built for Goose and other MCP-compatible AI agents.
What is ASSA?
ASSA reclaims your social life by moving your activity off of algorithm driven sites and apps and into your personal agent, where you control the flow and decide how to engage. Enjoy:
Anti-Social Social Agent - MCP server for Twitter/X integration with rich UI components
Digest tell you what's happening without opening any social app. Let your agent filter spam, ads, and hate speech!
Have conversations right in your agent's interface, no need to open the X app or site.
Features
🔐 Safe authorization via Arcade: Access you social accounts with sharing your password with an agent (or accidentally committing it, oops!)
📊 Interactive interface: Mentions displayed with avatars, text. Respond right there!
🔁 You're in control: Nothing posts without your explicit approval
git clone https://github.com/nearestnabors/assa
cd assa
bun install
bun run build
Add to Goose App (recommended—Goose CLI can't display interactive UI!)
In Goose's sidebar, go to Extensiions
Select "+ Add Custom Extension"
Add the command: node PATH TO ASSA FOLDER/dist/index.js
Add Environment variables ARCADE_USER_ID (the email you signed up to Arcade with) and ARCADE_API_KEY (get your Arcade API key here
Select "Add Extension"
How to use
Check X Activity
Check my X mentions from the last 24 hours
Get Timeline Digest
Show me a digest of my X timeline from the past 24 hours
Note: Timeline digest requires Chrome running with remote debugging. See Timeline Digest Setup below.
Post a Tweet
Post a tweet: "Just shipped a new feature! 🚀"
Reply to Someone
Reply to @anthropic_devs saying I'll share slides after the talk
Timeline Digest Setup
The timeline digest feature accesses your "Following" timeline using your existing browser session and Playwright. This is free (no API costs) and uses your logged-in state. (An API would be more robust, but X only makes timeline API functionality available to industrial developers who can afford extortionate fees. So here we are, as hobbyists.)
Prerequisites
Google Chrome installed
Logged into X in Chrome
Start Chrome with Remote Debugging
Before using timeline digest, start Chrome with the remote debugging port:
Then make sure you're logged into X in that browser window. (I keep one open and minimized on startup.)
Goose Recipe
ASSA includes a recipe for scheduled timeline digests:
Recipe
Description
x-news-digest.yaml
Daily digest of your Following timeline (requires Chrome with remote debugging)
Import the Recipe
Option 1: Generate a Deep Link
goose recipe deeplink recipes/x-news-digest.yaml
This outputs a goose://recipe?config=... URL. Paste it in a browser to import into Goose Desktop.
Option 2: Import in Goose Desktop
Open Goose Desktop
Click Recipes in the sidebar
Click Import Recipe or browse for file
Choose recipes/x-news-digest.yaml from the Recipe File input field
Option 3: Run via CLI
goose run --recipe recipes/x-news-digest.yaml
Schedule the Recipe
After importing, on the Recipes screen:
Click the clock icon next to the recipe
Select the frequency and time in the Add Schedule modal
Click Save
Note: Requires Chrome running with --remote-debugging-port=9222.
Tools
Tool
Description
x_auth_status
Check authentication, show connect button if needed
x_conversations
Show unreplied mentions as a conversation inbox
x_dismiss_conversation
Dismiss a conversation (reappears on new activity)
x_draft_tweet
Create draft with preview
x_post_tweet
Post after approval
x_timeline_digest
Fetch and summarize your Following timeline (past 24h)
x_show_tweet
Display a single tweet as a rich card with reply option
Development
# Run in development mode (auto-reload)
bun dev
# Type check
bun typecheck
# Lint check
bun check
# Run tests
bun test
# Run tests in watch mode
bun test:watch
# Build for production
bun run build
# Run all tests
bun test
# Run tests in watch mode (re-runs on file changes)
bun test:watch
# Run a specific test file
bun test src/__tests__/utils/time.test.ts
# Run tests matching a pattern
bun test --grep "snowflake"
Test Structure
Tests are located in src/__tests__/ mirroring the source structure:
Create a .test.ts file in the appropriate __tests__ subdirectory:
import { describe, expect, test } from "bun:test";
import { myFunction } from "../../utils/my-module.js";
describe("myFunction", () => {
test("does something expected", () => {
const result = myFunction("input");
expect(result).toBe("expected output");
});
});
Mocking
Use mock.module() to mock Node.js modules:
import { mock } from "bun:test";
// Mock before importing the module that uses it
mock.module("node:os", () => ({
homedir: () => "/tmp/test-home",
}));
// Now import your module
import { myFunction } from "../../state/manager.js";
Test Isolation
When testing stateful modules, use unique IDs and clean up between tests:
import { beforeEach } from "bun:test";
let testCounter = 0;
function uniqueId(prefix: string): string {
return `${prefix}_${Date.now()}_${++testCounter}`;
}
beforeEach(() => {
clearState(); // Reset shared state
});
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Assa?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Assa einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Assa?
Assa läuft lokal über stdio.
Wann wurde Assa zuletzt geprüft?
Zuletzt geprüft: 2026-10-27. Anti-Social Social Agent - MCP server for Twitter/X integration with rich UI components