capx café
Choose a range, then find the themes.
A week of commits is a source of material, not a publishing calendar. Some commits represent the same feature. Others are cleanup. Start by asking the agent to review a defined period and identify changes someone outside the codebase would understand.
The build-in-public skill guides this process. It looks for meaningful work, groups related changes, and proposes posts. You should still review whether the changes have shipped and whether their details are public.
Try this with your agent
Review the last seven days of commits. Group the shipped, public-safe changes into up to three themes. For each theme, show the source commits and draft one specific X update. Skip internal cleanup and do not invent metrics. Show all drafts for review; do not schedule or publish.
Give each post its own job.
Consider a hypothetical week with three changes: a draft now survives a refresh, an error message points to a missing setting, and a large export no longer times out. Those are three distinct stories. Five commits implementing the draft fix are still one story.
An illustrative first draft might read:
Fixed the refresh that used to wipe an unsent draft. The words now stay put when the page reloads.
A second post should explain the configuration improvement on its own merits. Rewording the same fix three times makes the queue longer without giving readers anything new. If only one change is worth sharing, one post is a good result.
Review before anything enters the queue.
Ask the agent to show the source behind each claim. Remove details that are not ready for public release. Edit for your voice, and run the drafts through preview. A clean preview is useful feedback, not a reservation of future publishing capacity: conditions can change before a scheduled send.
Also check whether the post will still be accurate on its scheduled date. “Available today” can become confusing in a queue. A concrete description of what shipped often ages better.
Set a small, explicit schedule.
For three approved drafts, an example schedule is Monday, Wednesday, and Friday at 09:00 in your timezone. That is a planning example, not a claim about the best engagement time. Choose a cadence you can keep supplied with useful material.
Try this with your agent
Propose a schedule for these three approved drafts: Monday, Wednesday, and Friday at 09:00 Asia/Kolkata, in the displayed order. Show the exact days, timezone, next send times, and queue before creating anything. Check account eligibility and applicable limits. Wait for my approval.
A capx café loop is a recurring schedule that sends one prepared post per occurrence, in order. Use more than one loop only when you need different schedules. Loops require a verified X account at least 30 days old, with applicable account checks and plan capacity. Short, the upcoming entry creator plan, has no loops.
Keep the queue honest.
After you authorize creation, ask the agent to confirm the schedule with list_loops. The queued posts run on the server, so your laptop can be closed. The server does not write new posts when the queue runs out; your agent must prepare more material.
Use pause_loop when the plan changes and top_up_loop for more approved drafts. Check the audit history to see what actually sent. A sustainable workflow gives you a small amount of maintenance and a clear view of what is going out.