# Can Cursor draft an X post with up to four screenshots from your latest build? > Source: https://tareno.co/agents/cursor/x > Language: en > Last reviewed: 2026-10-24 > Use Cursor with Tareno to turn this week's commits and four app screenshots into an X post within 280 characters, with alt text, saved as a draft you approve in Tareno. ## Connection facts | Field | Value | | --- | --- | | Product surface | Cursor (cursor) | | Available connection | Available in Cursor Directory | | Connection evidence | documented | | Methods | mcp, skill | | Authentication | oauth | | Setup | [Setup guide](https://tareno.co/docs/plugins) | | Install or connect | [Open setup](https://cursor.directory/plugins/tareno) | | Evidence observed | 2026-10-19 | | Facts reviewed | 2026-10-25 | Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface. Agent: Cursor · Network: X · Hub: [Cursor and Tareno](https://tareno.co/agents/cursor) ## Short answer **Can Cursor write an X post from my commits and attach screenshots?** Yes. Cursor reads the week's commits, writes a post within 280 characters, picks up to four screenshots from your Tareno library and writes alt text for each, then saves a draft for your X account. It cannot capture the screenshots, and scheduling stays pending until you approve it in Tareno. Solo developers who share progress on X know the pattern: the best posts are a screenshot and one sentence, and the cost is the ten minutes of remembering what changed. Cursor already knows, because it has just helped write the commits. The part it cannot do is take the screenshots, which you do while the app is running, but it can match them to the changes, write alt text and keep the post inside the limit. This page follows an indie developer working on a habit-tracking app, covering the commit-to-post step, the four-image limit and the alt text that most progress posts skip. ## Example: an indie developer shows this week's habit-tracker build Imagine a developer who added a streak calendar and a dark theme this week. In Cursor she asks for a post based on the week's commits. Cursor lists the user-visible changes, ignores a refactoring, and asks which screenshots she took. She has four in the library. Cursor looks them up with `list_media`, matches two to the calendar and two to the theme, writes a post of 190 characters and a description for each image, and saves the draft with `create_drafts` for her X account. She notices that one screenshot still shows the old icon, replaces it and requests a Friday 17:00 slot. ## Step by step 1. **Let Cursor read the week's commits.** Ask it to separate user-visible changes from refactoring and tooling. A progress post that mentions a build system nobody sees loses its reader. 2. **Take the screenshots yourself.** Cursor cannot run your app on a device, so capture one screenshot per visible change and upload them to the Tareno library with names that say what they show. 3. **Match screenshots to changes.** Cursor finds the files with `list_media` and tells you which change has no screenshot. X takes up to four photos per post, so choose which changes make the cut. 4. **Write alt text with the post.** Ask for a short description of each image that says what a person who cannot see it would need to know. Tareno takes alt text per media item. 5. **Save the draft.** Cursor confirms the account with `list_accounts` and saves the text and images through `create_drafts`. Open the draft in Tareno and look at the image order. 6. **Request a time and approve.** Give a day, a time and an IANA time zone. The request becomes a pending action, and you approve it in the Tareno dashboard before X receives anything. ## Prompts to copy ### Summarize what users can see ```text Read this week's commits on the main branch and list the changes a user of the habit-tracking app would notice, in one plain sentence each. Name the internal changes you left out, and tell me which visible changes still need a screenshot. ``` ### Match the screenshots ```text Use Tareno to find my screenshots in the media library folder [habit-tracker-week-41] and match them to the visible changes. Tell me which change has none, which screenshot looks out of date, and which four you would use if only four fit in the post. ``` ### Write post and alt text ```text Write an X post within 280 characters about the streak calendar and the dark theme, in first person and without hashtags. Then write a one-sentence description for each of the four chosen screenshots, saying what is visible and not what the feature does. ``` ### Save the draft ```text Use Tareno to confirm the X account [handle] and save the approved post with the four screenshots in the agreed order as a draft. Return the draft ID, and request no time until I give you the day and the time zone. ``` ## X in Tareno - X allows up to four photos in a post according to its API documentation, and Tareno's configuration for X sets the same limit, so a build update has to choose its best four. - Tareno takes alt text of up to 1,000 characters per media item, which is far more than a screenshot needs, so a short description is enough. - Tareno's configuration for X lists jpg, png, gif and webp images up to 5 MB, so full-resolution phone screenshots may need exporting at a smaller size. - Tareno does not read posts or replies on X, so Cursor cannot tell which earlier build post drew most interest. Official rules ([X API documentation: create a post](https://docs.x.com/x-api/posts/creation-of-a-post), checked 2026-10-24): - A post may include up to 4 photos, 1 animated GIF or 1 video. - The allowed video length depends on the posting account, not on the API plan: 20 minutes and 8 GB by default, 125 minutes and 16 GB with X Premium or verified status. Tareno's configuration for X stops at 140 seconds. - Quote-posting through the API requires an Enterprise plan and is not available on self-serve tiers. ## Mistakes to avoid - Showing an outdated screenshot. Check each image against the current build before you request a time. - Using four images that show the same screen. Each image should prove a different change. - Skipping alt text because the post is informal. People who use screen readers follow indie developers too. - Exporting a screenshot above the size limit. Check the file in the library before the draft is saved. ## What does not work - Cursor cannot take screenshots of your running app, so you capture and upload them before it can match anything. - It cannot read replies or earlier posts on X through Tareno, because Tareno does not expose them for X. - It cannot publish by itself, since a time request becomes a post only after you approve it in the Tareno dashboard. ## Frequently asked questions ### Can Cursor take the screenshots for me? No. It works in the editor and the repository, not on your device. You capture one screenshot per change, upload them to the Tareno library, and Cursor matches them to the commits and writes the alt text. ### How many screenshots can one X post have? Up to four photos, according to X's API documentation and Tareno's configuration. Cursor can tell you which change has no image and which four to keep if you have more. ### Is alt text necessary? Not required, but worth the few words. Tareno takes alt text per image, and Cursor can write a plain description of what is visible, which helps readers who cannot see the screenshot. ### Can Cursor post the same update to LinkedIn? It can prepare a separate draft for another connected account with different limits, but each network needs its own text and approval. Ask it to name the account for every draft. ### Does Cursor need a special setup for X? No. The same Tareno connection serves every network, so once your X account appears when you ask Cursor to list your accounts, the workflow needs only the images in your library. ### Will the build post go out without my approval? No. A time request is a pending action in Tareno, and X receives the post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards. ## Tareno tools used - `list_media` - `list_accounts` - `create_drafts` - `get_action_status` Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them. ## Related - [Cursor × Tareno overview](https://tareno.co/agents/cursor) - [X with Tareno](https://tareno.co/channels/twitter) - [Media library](https://tareno.co/features/media-library) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Plugin setup guides](https://tareno.co/docs/plugins) - Use case: [Publish photos and slides with image descriptions that are checked](https://tareno.co/agents/use-cases/photos-with-image-descriptions)