x-engage

X daily engagement session

Goal: grow @jared_hebb by replying, not broadcasting. Claude drafts; Jared posts by hand.

NO BROWSER AUTOMATION ON X (hard rule, 2026-07-19)

Never drive Jared's logged-in X account through Claude in Chrome (or any browser tool): no opening his feed, no scrolling/harvesting, no auto-posting replies, no clicking Follow. X flagged the account for scripted activity and demoted his reach when a session did this. Every outward action on X is Jared's hands only. Claude's job here is draft-and-hand-off. This holds until we pay for official X API access (the first revenue spend); do not reintroduce browser control before then, and if a session ever seems to need it, stop and ask.

Session flow

1. Start the Engage app (the permanent dashboard at <HOME>\projects\engage). Check http://localhost:3220/api/health; if it is not up, run npm run dev there in the background and wait for the health check to pass. All review, metrics, and history live in this app now.

2. Get the raw material from Jared. He pastes the post URLs (or screenshots) he wants to engage, and tells you his current follower/following counts if he wants them tracked. Claude does not open X to find posts. If he asks for search ideas, offer terms from this pool for HIM to run: "claude code", "built with claude", "build in public" ship, ai agents workflow, indie hacker revenue, "cursor vs claude", astro cloudflare, solo founder ai. WebFetch on a public post URL is fine for reading context; driving his account is not.

3. Vet what he brought. Draft only for posts worth a reply: real author (not a bot/engagement-farm), a post where Jared can add something concrete, ideally not already buried under 50+ replies. Skip the rest and say why in one line.

4. Draft a reply for each following the voice rules below, then present them in the Engage review page (Jared approves in a browser, never in the terminal):

   • POST the session JSON to http://localhost:3220/api/session (shape: {platform:"x", title, replies:[{id,author,age,context,draft}], follows:[{handle,reason}], profile:{bio,link}|null}; omit profile unless a refresh is planned). There is deliberately no post field here, see "This session does not draft posts" below. The response returns reviewUrl; open it in a browser tab for him.
   • He marks each item Drafted/Skip/Redraft, edits drafts inline, then hits the single "Approve and send to Claude" button (here "drafted" means approved-to-copy, not auto-sent). Poll GET http://localhost:3220/api/session/<id>/decisions until saved:true. The decisions tell you which drafts he approved; nothing is posted by Claude.
   • Any item with decision redraft (optional direction note attached): write a fresh draft honoring the note, POST {drafts:[{id,draft}]} to http://localhost:3220/api/session/<id>/redraft (id = your string id from the session JSON or the numeric item id; a 400 means it matched nothing, so fix it and resend rather than assuming it took), then read the drafts back to confirm the new text is live, tell him to refresh, and poll for the next save. Repeat until nothing is marked redraft.