Loading...
Devin Desktop/TarenoUse Devin with Tareno to write social media posts, adapt existing content and prepare posting times.
Devin Desktop / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
Devin DesktopIllustrated demo · no live account
In Devin Desktop, first check which agent you use. The default Devin Local agent uses Devin CLI MCP configuration; legacy Cascade uses its own mcp_config.json. Add https://tareno.co/api/mcp as a remote HTTP server, complete the supported OAuth flow and ask for your connected accounts. Tareno has not completed a Devin Desktop client test.
Devin Desktop has two agents with different settings. Devin Local uses the Devin CLI configuration files. Legacy Cascade uses mcp_config.json, opened from its Actions menu; Cascade has no MCP marketplace or one-click install. The example below is a Cascade configuration.
Use the Tareno account that owns the intended social profiles and review the permissions before authorizing. Follow the OAuth controls for the selected Desktop agent. Cloud organization settings are a separate product surface.
The hosted address appears in the entry on the right. If you manage servers through a configuration file, it is the same address that other clients use; no key needs to appear in it when you sign in with OAuth.
Ask Devin for your connected accounts before it drafts anything. The account you want in the answer confirms the connection; an empty answer means the account still has to be connected inside Tareno.
{
"mcpServers": {
"tareno": {
"url": "https://tareno.co/api/mcp"
}
}
}Input
Provide the approved source and audience.
Review-ready drafts
Use Tareno and compare the returned draft IDs.
Approval in Tareno
Review text, media, account, and time in Tareno and approve.
Devin's record of completed work is the asset. These three jobs turn it into public writing without inflating it, and each has a workflow page with its own checks.
A consultancy that delegates work to Devin can summarize what was delivered, the test results the client has seen and the limits of the work, without naming the client. The brief goes to LinkedIn only after the client has seen the wording and agreed, which is a step Devin can prompt for but cannot perform.
Devin lists the tickets that finished and separates changes a customer can use from internal work. It reports which changes sit behind a flag or reach only some accounts, so the Friday post on X says what is live rather than what is closed, and fits in 280 characters.
Self-hosting administrators read release posts for what they must do. Devin finds the sessions that changed schemas, configuration keys or minimum versions and puts those actions first in the post, leaving you to test the upgrade steps on a copy before approving anything.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Codex and Claude Code run in a terminal, Cursor and Copilot in an editor. Devin works as a delegated engineer with its own sessions, which is why its record is useful for delivery updates: the sessions already describe what was done and what was tested. If your content comes from commits in an editor, those other agents sit closer to the code.
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_accountsNot yet; no client test has been completed on our side. Devin can use remote MCP servers according to Cognition's documentation, so expect an OAuth sign-in in the first session and confirm the connection with a read-only call.
For an account with one owner, personal access. A shared connection would let anyone using Devin in the organization draft for that account. Approval still happens in Tareno either way, but the drafts should come from the person who owns the account.
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.
It can draft a brief that omits the client and lists the evidence behind each statement. Whether it may be published is the client's decision, so show them the wording and record their agreement first.
Yes, on networks that take video. X allows one video per post and Tareno's configuration limits it to 140 seconds. Upload the clip to the library first, and Devin can find it by name.
No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches LinkedIn, X or Mastodon until you approve it in the dashboard. Devin can only report that the action is pending.
Tell Devin to describe changes as a customer would see them and to leave out ticket numbers, service names and internal tooling. Then read each draft in Tareno, because the check for what is sensitive is still a human one.
Usually `list_accounts` to confirm the destination and `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, and `get_action_status` tells you what became of the request.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.