Your feed, run by your agents, approved by you.
01
antiPost is a desktop app for posting, answering comments and DMs, and capturing leads without opening Instagram, X or YouTube. Your agents are coding CLIs you already pay for: Codex CLI, Claude Code, Grok CLI, Cursor Agent CLI or Gemini CLI. They work through a local MCP server. Nothing is published or sent until you approve it.
App data lives in one SQLite file. Secrets live in the OS keychain. It is built in Rust with Tauri 2.
02
Public downloads are not available yet. planned Builds are planned for Windows, macOS (Apple silicon and Intel) and Linux (deb, rpm, AppImage).
To run from source you need Rust (the repo pins its toolchain). Linux also needs WebKitGTK 4.1:
sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev libayatana-appindicator3-dev \
librsvg2-dev patchelf build-essential pkg-config libssl-dev
cargo run -p antipostThere is no Node build. The interface is static files embedded in the app.
03
The setup wizard walks through:
Each agent runs its CLI in a terminal session confined to its folder. Output streams into the chat and is saved in SQLite.
04
Settings → Connections shows a card per network.
| Status | Meaning |
|---|---|
| Not set up | antiPost does not have that network's developer app yet. Connect opens a short setup wizard. |
| App configured | The client id is saved and, when needed, the secret is in the OS keychain. |
| Connected as @name | You finished Connect and the network returned that account. |
The wizard opens the provider's console and gives one-click copy for the callback URL and each scope. Paste the client id and secret, press Test, then Finish. Nothing is saved until Finish. Connect opens your system browser.
The redirect port is 43827. If it is taken, Connect stops and nothing is saved. Reset removes the saved id, the keychain secret and the account token.
05
The app has an Inbox, Posts (list and board), Leads, Calendar, Analytics and Connections, plus an agent list with a chat per agent and a ⌘K palette.
Agents draft replies and posts. You approve, edit or discard them. There is no approve tool for agents, so only you can approve.
06
Brand notes and fetched page excerpts are kept in SQLite, and your chosen agent drafts the brand profile. Audience, trend and engagement reads use the networks' official APIs only when credentials are saved; otherwise the screen says what is missing.
07
Settings → Integrations → antiHunt reads antiHunt's SQLite file, read-only. antiPost never writes to it.
Default file locations:
~/.local/share/com.minemylead.antihunt/antihunt.db~/Library/Application Support/com.minemylead.antihunt/antihunt.db%APPDATA%\com.minemylead.antihunt\antihunt.dbPaste another path if yours is elsewhere. Sync now imports leads; the same platform and handle update one lead. Set an interval in hours to sync when Leads is opened, or 0 to sync only by hand. Hot and warm leads can be queued for Engage, where the agent drafts a reply in your brand voice for you to approve.
08
A local MCP server on the loopback address exposes tools for drafts, the inbox, leads and tasks, plus read-only brand, audience, trend and engagement tools. Each agent gets its own bearer token, stored in the OS keychain.
09
Everything is in one SQLite file on your computer. Credentials, OAuth tokens and MCP tokens go to the OS keychain and are never written to SQLite. Secrets are never compiled into the app.
10
Another program uses port 43827. Close it and try again.
antiHunt's database was not found at the default path. Paste the full path to antihunt.db.
Connect that network first; reads use only official APIs.