# Can Devin turn a week of finished tickets into a shipped-this-week post on X? > Source: https://tareno.co/agents/devin/x > Language: en > Last reviewed: 2026-10-24 > Connect Devin to Tareno to turn the week's finished sessions into an honest shipped-this-week post for X within 280 characters, with limits stated and approval in Tareno. ## Connection facts | Field | Value | | --- | --- | | Product surface | Devin Desktop (devin) | | Available connection | Custom MCP connection | | Connection evidence | documented | | Methods | mcp | | Authentication | oauth | | Setup | [Setup guide](https://tareno.co/docs/mcp) | | Install or connect | [Open setup](https://tareno.co/docs/mcp) | | Evidence observed | No dated observation recorded | | Facts reviewed | 2026-10-27 | Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface. Agent: Devin Desktop · Network: X · Hub: [Devin Desktop and Tareno](https://tareno.co/agents/devin) ## Short answer **Can Devin summarize what shipped this week and prepare the X post?** Yes, once Tareno is connected as an MCP server. Devin can list the sessions and tickets that finished this week, separate what customers can use from what is internal, and save a post within 280 characters through Tareno. Tareno has not completed a client test for Devin, so setup follows Cognition's documentation. Approval happens in Tareno. A product that ships every week and says nothing looks dead from the outside. A short post every Friday fixes that, but only if someone gathers what shipped, and that is the part that gets skipped. Devin works through tickets and keeps a record of finished sessions, so it can list what was completed and what changed for users. The difficulty is honesty: a ticket that was closed is not a feature that works for everyone. This page follows a small product team that posts every Friday, with the connection steps Cognition documents and with a check that separates shipped from finished. ## Example: a project-management tool posts every Friday Imagine a team whose Devin sessions closed seven tickets this week. On Friday morning the product manager asks Devin to list them with what each changed for users. Devin separates three user-visible changes from four internal ones, and notes that one of the visible changes, bulk-archive, is behind a flag for new accounts only. The post it drafts says bulk-archive is rolling out to new workspaces first. It saves the text through `create_drafts` for the product's X account after confirming it with `list_accounts`, and the product manager requests a Friday 16:00 slot. ## Step by step 1. **Add the server in Devin.** Cognition documents two ways in: the MCP marketplace inside Devin, with an OAuth sign-in during the first session, or the CLI, which has its own login command. They recommend streamable HTTP. 2. **Keep the access personal.** An OAuth connection can be organization-wide or per person, according to Cognition. An X account has one owner, so let that person sign in rather than sharing the link with the team. 3. **Prove the link first.** Before writing anything, have Devin call `list_accounts`. Your X account in the reply confirms it; otherwise connect the account in Tareno. 4. **List finished work.** Ask Devin for this week's finished sessions and tickets with what each changed for a user. Tickets closed and features live are different things. 5. **Separate shipped from finished.** For each user-visible change, ask Devin to state whether it is behind a flag, limited to some accounts or still in review. The post says only what customers can use. 6. **Save, request and approve.** Devin saves the post through `create_drafts`. Give a day, a time and an IANA time zone, and approve the pending request in the Tareno dashboard. ## Prompts to copy ### List what finished ```text List the tickets and sessions that finished this week, with one sentence on what each changed for a user of the product. Mark each as user-visible or internal, and say whether you saw evidence that it is live, such as a merged and deployed change. ``` ### Check what is actually live ```text For each user-visible change, state whether it is behind a flag, limited to certain accounts or waiting for review, and where you found that. If you cannot tell, say so rather than guessing, and do not write any post before I have confirmed the list. ``` ### Write the Friday post ```text Write an X post for a Tareno draft within 280 characters that lists the three user-visible changes of the week as the product team would say them, states the rollout limit of the flagged change plainly, and avoids the words revolutionary and game-changing. Give me the character count. ``` ### Save for the product account ```text Use Tareno to confirm the X account [product handle] and save the approved text as a draft. Return the draft ID and the text, and do not request a time until I give you the day and the time zone. ``` ## X in Tareno - Tareno's configuration for X allows 280 characters, so three changes and one limit fit if each is a short phrase. - Tareno saves single posts for X and has no thread tool, so a longer changelog should live on a page that the post links to. - Tareno does not read posts or replies on X, so Devin cannot see responses to earlier weekly posts or ask which change interested users. - X allows up to four photos or one video per post according to its API documentation, so a short screen recording of one feature can replace a sentence. 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 - Announcing a feature that is behind a flag. State the rollout, or the replies will ask where it is. - Counting closed tickets as shipped. Closed means the work finished, not that customers can use it. - Using personal access in the wrong way. Sign in with the person who owns the X account. - Padding the post with internal work. Customers do not need to know about a dependency upgrade. ## What does not work - Devin cannot tell whether a change is live for customers unless there is evidence in the work it can see, so the product manager confirms. - It cannot read replies to the weekly post, because Tareno does not expose replies for X. - It cannot publish by itself, since scheduling requests wait for your approval in the Tareno dashboard. ## Frequently asked questions ### Does Devin work with Tareno out of the box? Devin can use remote MCP servers per Cognition's documentation, but Tareno has not finished a client test with it. Expect to complete an OAuth sign-in in the first session and verify with a read. ### Why not share the connection with the whole team? A shared link would let anyone using Devin in the organization draft for the product's X account. Personal access ties the connection to the person who owns it, and approval still happens in Tareno either way. ### How does Devin know what is live? Only from what it can see: merged changes, deployment records and flags in the work it handled. When it cannot tell, it should say so, and the product manager confirms before the post is approved. ### Can the weekly post include a screen recording? Yes. X allows one video per post, and Tareno's configuration limits it to 140 seconds. A short recording of one feature in the library can go with the text, replacing a sentence. ### How many changes should one post list? Three at most within 280 characters. If more shipped, link to a changelog page, and let Devin put the biggest user-visible one first so that a preview still shows it. ### Does anything go out before I approve it? No. A scheduling request becomes a pending action in Tareno, and X receives the post only after you approve it in the dashboard. Devin can only report that it is pending. ## Tareno tools used - `list_accounts` - `create_drafts` 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 - [Devin × Tareno overview](https://tareno.co/agents/devin) - [X with Tareno](https://tareno.co/channels/twitter) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Remote MCP setup](https://tareno.co/docs/mcp)