Loading...
×Use Cursor with Tareno to turn a game jam's commits and screenshots into a Bluesky post-mortem thread, hour by hour, saved as one draft you approve in Tareno.
Yes. Cursor reads the commit history with its timestamps, builds a timeline of what happened when, matches your screenshots from the Tareno library and writes a post-mortem thread within 300 characters per post. It saves the whole thread as one draft. Scheduling stays pending until you approve it in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
A game jam gives you two days and a repository, and afterwards the best story is in the commit log: the feature that arrived at hour thirty, the bug that ate the night, the cut that saved the build. People like post-mortems, and Bluesky's thread format lets the story run in order. The usual problem is memory, because by the next afternoon nobody recalls the sequence. Cursor can read the timestamps and rebuild the timeline, and Tareno saves the thread as one draft. This page follows a two-person jam team through a post-mortem, with the honest timeline, the screenshots in order and the credit rules for a team.
Imagine a team that finished a puzzle game at 03:00 on the last night. The next day one of them asks Cursor to read the commit history and build a timeline. Cursor groups the 94 commits into phases, finds that the core mechanic landed at hour nine and that 31 commits in the last six hours were fixes. It proposes a post-mortem of seven posts: the idea, the first playable, the pivot, the crunch, the cut, the result and what they would change. It matches six screenshots from the library with list_media and saves the thread with create_drafts. His teammate approves the wording before the request.
Ask it to group commits by hour into phases and to report the largest commits and the last six hours. The timeline should come from timestamps, not from memory.
Ask Cursor to verify statements such as the mechanic landed at hour nine against the commit that introduced it. A post-mortem with a wrong timeline loses its point.
Decide who is named and how. Cursor can see commit authors, but a teammate who did sound or art may not appear in the history, so add them yourself with their agreement.
Cursor finds the screenshots with list_media and orders them by the phase they show. Bluesky posts in Tareno take up to four images each.
Cursor writes seven posts within 300 characters, confirms the account with list_accounts and saves the thread as one draft through create_drafts.
Give a day, a time and an IANA time zone. The request becomes a pending action, and you approve it in the Tareno dashboard after your teammate has read it.
Read the commit history of this repository for the jam weekend and group the commits by hour into phases. Report when the core mechanic first appears, which hours had the most commits and how many of the last six hours were fixes, with the commit hashes that support each claim.I want to say that the core mechanic landed at hour nine and that we cut the multiplayer mode on Saturday night. Verify both against the commits and tell me which statement the history supports, which it contradicts and which it cannot show.Write a seven-post Bluesky thread for Tareno: the idea, the first playable, the pivot, the crunch, the cut, the result and what we would change. Use only claims you verified, keep each post within 300 characters and mention my teammate only as [name, with their permission].Use Tareno to find the screenshots [jam-01 to jam-06] in my media library, confirm my Bluesky account [handle] and save the approved thread as one draft with each screenshot on the post that matches its phase. Return the draft ID, and request no time yet.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: AT Protocol lexicons: app.bsky.feed.post and app.bsky.embed, read on 2026-10-25. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
Accurate for when code was committed, not for when it was written or when ideas happened. Cursor reports what the history shows and where it cannot say, so you add context from memory and label it as yours.
It sees commit authors, but contributions like art, music or design may not appear in the history. Name those people yourself, and only with their agreement, before the thread is requested for a time.
Yes. Tareno's configuration allows one video of up to 180 seconds on Bluesky, up to 100 MB. A short clip in the root post gives readers a reason to continue into the post-mortem.
State what happened: the number of fix commits, what was cut and why. Cursor can quote the counts from the history, and the account of how it felt is yours to write.
No. The same Tareno connection serves every network, so once your Bluesky account appears when you ask Cursor to list your accounts, the workflow needs only the screenshots in your library.
No. A scheduling request becomes a pending action in Tareno, and Bluesky receives the thread only after you approve it in the dashboard. `get_action_status` shows what happened afterwards.