# Can Continue share a reusable prompt rule from your repo as an X post? > Source: https://tareno.co/agents/continue/x > Language: en > Last reviewed: 2026-10-24 > Configure Continue in agent mode with Tareno to turn a rule or prompt recipe from your repository into an X post within 280 characters, checked for secrets and approved in Tareno. ## Connection facts | Field | Value | | --- | --- | | Product surface | Continue (continue) | | 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-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: Continue · Network: X · Hub: [Continue and Tareno](https://tareno.co/agents/continue) ## Short answer **Can Continue turn a rule file from my repo into a post for X?** Yes, once Tareno is configured as an MCP server in Continue's agent mode. Continue reads the rule or prompt recipe you want to share, strips anything private, writes a post within 280 characters and saves it through Tareno. Tareno has not completed a client test for Continue, and its MCP page does not mention OAuth. Approval happens in Tareno. Teams that use Continue write down how they want the assistant to behave: a rule that says tests come first, a prompt recipe that reviews a migration. Those files are small, useful and shareable, and developers on X like a recipe they can copy. The risk is what else is in the file: an internal service name, a path, a note about a customer. Continue can read the file and help you separate the general rule from the specific, and Tareno saves the draft. This page follows a platform engineer who shares one rule, with the configuration steps in Continue's documentation and a plain statement of the authentication question that the documentation leaves open. ## Example: a platform engineer shares a migration-review rule Imagine an engineer whose team keeps a rule file that tells Continue how to review a database migration: check for locks, check for a rollback, ask about data volume. She asks Continue to read the file and describe the general rule without names. Continue finds two lines that mention the company's billing service and one internal ticket prefix, and proposes a generic version. It writes a post of 260 characters with the three checks as a short list, and saves it with `create_drafts` for her X account after confirming it with `list_accounts`. She checks the final text for anything that identifies the team and requests a Thursday slot. ## Step by step 1. **Write the server definition.** Per Continue's docs, a YAML file inside a .continue/mcpServers folder at the workspace root defines a server, as does an mcpServers block in the main config. Stand-alone files carry name, version and schema fields. 2. **Pick streamable-http.** Of the three transports Continue lists, stdio, sse and streamable-http, the last suits a hosted endpoint. Point it at the address on the Remote MCP setup page. 3. **Settle the sign-in method.** Continue's MCP page is silent on OAuth. Where a remote sign-in is not possible, a Tareno API key works as a bearer header read from an environment variable, and it must never land in a committed file. 4. **Use agent mode for the first call.** MCP tools only work there, per the documentation. Request `list_accounts`; your X account in the answer means the link is good. 5. **Generalize the rule.** Ask Continue to list every name, path and ticket reference in the rule file and to rewrite it without them. A rule is easier to copy when it does not mention your systems. 6. **Write, save and approve.** Continue writes the post within 280 characters and saves it 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 is private ```text Read the rule file [.continue/rules/migration-review.md] and list every service name, path, ticket prefix and person it mentions. Then show me the rule rewritten without any of them, keeping the checks themselves unchanged, so that I can turn it into a post for Tareno. ``` ### Write the post ```text Write an X post within 280 characters that shares the three checks from the generalized rule: locks, rollback and data volume. Use plain text because X has no formatting, put each check on its own line, and give me the character count and the number of line breaks. ``` ### Check for secrets ```text Before anything is saved to Tareno, read the final post and the original rule once more and tell me whether the post reveals anything about our systems, such as a naming pattern or a tool we use. Quote the phrase that worries you. ``` ### Save the draft ```text Use Tareno to confirm the X account [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 has no formatting, so a three-item list is written as plain lines, and line breaks use characters inside the 280. - A rule or prompt recipe often fits in a screenshot, and X allows up to four photos, so a rule that is too long for the text can become an image of the generalized file. - Tareno does not read posts or replies on X, so Continue cannot see whether other developers adapted the rule or what they changed. - Tareno saves single posts for X, so a longer rule has to be linked, for example from a public gist, instead of being split into a thread. 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 - Sharing the file as it is. Internal names and ticket prefixes are easy to miss, so generalize first. - Expecting the same sign-in as other clients. If Continue cannot do OAuth, use an API key from an environment variable and never commit it. - Forgetting agent mode. MCP tools are not available in plain chat. - Posting a rule that your own team does not follow. Share what you actually use. ## What does not work - Continue cannot know which details in your rule file are confidential, so the author reads the draft for anything that identifies the team. - It cannot read replies or adaptations on X, since 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 ### Has Tareno been tested with Continue? No client test has been completed. The configuration here follows Continue's own documentation, so confirm it with a harmless read before you rely on it for a post you care about. ### Which file should hold the server definition? Either a YAML file in the workspace's .continue/mcpServers folder or a block in the main config. A rule file you plan to share belongs elsewhere, so keep the two apart. ### Why are the tools missing in plain chat? Agent mode is the only place Continue uses MCP. Switch modes, confirm the server loaded and ask for the account list; if the account shows up, the rest of the workflow is available. ### Can I use a key instead of OAuth? Where Continue cannot complete OAuth, yes: Tareno accepts API keys from compatible clients as a bearer header. Store the key in an environment variable, not in the YAML and not in a prompt. ### Can I post the rule as an image? Yes, if the text is too long. X allows up to four photos, and Tareno's configuration accepts png and jpg. Make the image from the generalized file, never from the original with internal names. ### Does anything go live 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. Continue 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 - [Continue × Tareno overview](https://tareno.co/agents/continue) - [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)