Your Editor-in-Chief stays on when you close the tab.
Content Agents Bot is the same Editor-in-Chief on your Mac: it comments, likes, reshares, and uploads from your own logged-in browser. Propose drafts the work. Act finishes it. Nothing fires if the Mac is off — that is honest, not a bug.
Official APIs where they exist.
Publishing your posts still goes through LinkedIn, Meta, and the rest of the official connections. Content Agents Bot is for the actions those connections are not allowed to take: commenting on someone else’s post, joining a Reddit thread while commercial API access is pending, and uploading a finished article video to YouTube without standing up a Google Cloud OAuth app.
- Runs on your Mac, in your session — Playwright opens the Chrome profile you already use. There is no Content Agents-controlled login, no proxy, no throwaway account. If you can do it in that browser, the Bot can do it after you say yes.
- Approval first, always — On Propose, nothing leaves until you say so. On Act, the Editor-in-Chief may enqueue and execute enabled jobs itself. Login walls still pause for you.
- LinkedIn comments the API cannot send — Company Page publishing is already in the product. Commenting on someone else’s post is partner-gated. Pair the Bot and those approved replies leave from your real profile.
- Reddit without waiting on Reddit — Commercial API access is still pending their written approval. Until that exists, approved comments and upvotes go out through your logged-in Reddit session — not a scraped farm.
- YouTube upload, no Cloud console — Article Video already renders the file. The Bot opens YouTube Studio and uploads it from the account you signed into at setup. You do not file a Google Cloud OAuth app to ship a trailer.
- Not a pod, not a scraper — No members, no reciprocal likes, no silent browsing of strangers’ feeds. If a page does not match what the Bot expects, it stops and reports failure instead of guessing.
What it looks at
- LinkedIn — Like, comment, and reshare on posts you approved — from your own profile, for the actions the Community Management API still withholds.
- Reddit — Comment and upvote in communities you already participate in, while Reddit’s commercial API remains closed.
- YouTube — Upload rendered article videos to YouTube Studio. Spotify listings stay a one-time Yourself paste of your RSS URL — that ceiling is industry-wide, not ours.
- The desk — Pair and download live on Editor-in-Chief. Queue from Conversations or MCP. Directories stay human-submitted on purpose.
The last mile is not another scheduler.
Engagement pods and ghost writers
- A ring of people (or bots) liking whatever you post
- A Chrome extension driving your session without you seeing the words
- Volume first, relevance never
- Account risk the moment the platform notices
- YouTube uploads stuck behind a Google Cloud OAuth consent screen
Content Agents Bot
- Your Mac, your Chrome profile, your real accounts
- Propose: it queues. Act: it decides and ships, still paused for login and spend
- The same Editor-in-Chief you brief on the desk
- LinkedIn comments, Reddit replies, YouTube uploads — the jobs APIs will not do
- Asleep vs working is visible. A closed lid is waiting, not failure.
How it works
- Meet it on the desk — Editor-in-Chief holds the queue and the status light. Conversations is the job board for threads worth joining.
- Pair a Mac, once — Download below, open the Content Agents Bot app, sign in with Google, then sign into LinkedIn, Reddit, and YouTube Studio in a visible browser. No terminal, no token to paste.
- It keeps going — While that Mac is on, the Editor-in-Chief notices work within seconds and performs it in your session. Propose waits for you. Act finishes the job.
The Editor-in-Chief on your computer.
The Mac companion is included. Pair it from the desk. Propose vs Act is the dial — not a second product.
Open the desk. Pair this Mac.
Your Editor-in-Chief is already there. Give it a computer so it can keep working when you close the tab.
Frequently asked questions
Is this an engagement pod?
No. A pod is a reciprocity ring — people agree to engage with each other’s posts regardless of relevance, usually through an extension. Content Agents Bot has no members and no trade. It only performs an action you already judged worth doing, in communities you already belong to, from the account that is actually yours.
Will this get my account restricted?
You are acting as yourself, at a volume you already approved, on a machine you control. That is closer to you clicking than to a farm. The Bot refuses to proceed if the page does not look like the action you queued. Keep daily ceilings honest. We will not automate directory form-fills or burner accounts.
Why not just use the official APIs?
We do, everywhere they exist. LinkedIn will not let a normal app comment on other people’s posts. Reddit has not granted commercial API access. YouTube Data API upload wants a verified Google Cloud OAuth app. Content Agents Bot is the last mile for those three jobs — not a replacement for Social Publishing.
What do I need to set up?
A dedicated Mac that stays on, Setup installs what it needs, including its own Node.js, and a few minutes to sign into each platform in a visible window. Download the app, open it, and sign in with Google — nothing to paste. After that it polls in the background.
Does the Bot see my Content Agents login or customer data?
No. Its only credential is a device token scoped to claim and report the actions you approved for that brand. It never receives a Supabase key, and it never sees another tenant.
What if my Mac is asleep?
Queued actions wait. Nothing publishes from the cloud as you. That is the honest trade: last-mile reach in exchange for a machine that is actually on.