# Can Continue share an open-source assistant configuration as a Mastodon post? > Source: https://tareno.co/agents/continue/mastodon > Language: en > Last reviewed: 2026-10-24 > Configure Continue in agent mode with Tareno to turn an assistant configuration from your repo into a Mastodon post with a license note, 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: Mastodon · Hub: [Continue and Tareno](https://tareno.co/agents/continue) ## Short answer **Can Continue turn my assistant configuration into a Mastodon post for open-source communities?** Yes, after Tareno is set up as an MCP server for Continue's agent mode. Continue reads your configuration, removes private values, writes a post within your server's limit that says what it does and which license applies, and stores it as a draft through Tareno. No client test with Continue is finished, and its MCP page is silent on OAuth. Open-source communities on Mastodon like configurations they can copy: a set of rules for an assistant, a prompt that reviews migrations, a snippet that wires a local model. Sharing one takes a few minutes of care, because a configuration file collects private values over time, such as endpoints, project names and keys. The post itself should say what the configuration does, who it is for and under which license it is shared, since the community checks. Continue sits in the editor next to the file and can help with both parts. This page follows a developer sharing a local-model configuration, with the setup steps in Continue's documentation and the secret check that comes before the post. ## Example: a developer shares a configuration for a local code model Imagine a developer who runs a small local model through Continue. In agent mode she asks Continue to read her configuration and list everything in it that is private. It finds an internal hostname and a project name, and an API key stored directly in the file where an environment variable should be. She replaces them, and Continue writes a post of 380 characters that says what the configuration sets up, which model sizes it was tested with, and that it is shared under the MIT license. It saves the draft with `create_drafts` for her Mastodon account, after confirming it with `list_accounts`. ## Step by step 1. **Declare Tareno as a server.** In the workspace's .continue/mcpServers folder, a YAML file with name, version and schema fields declares the server; an mcpServers block in the main config does the same job. 2. **Use the remote transport.** A hosted endpoint calls for streamable-http among the transports that Continue supports. The address comes from the Remote MCP setup page. 3. **Handle authentication.** Because Continue's page says nothing about OAuth, a Tareno API key sent as a bearer header is the fallback. Read it from an environment variable so it stays out of any committed file. 4. **Switch to agent mode and read.** MCP tools are limited to that mode. A call to `list_accounts` that returns your Mastodon account shows the link is good. 5. **Check the configuration for private values.** Ask Continue to list every hostname, project name, path and key in the file. A shared configuration should use placeholders and environment variables. 6. **Write, save and approve.** Continue writes the post 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 my Continue configuration file and list every hostname, project name, absolute path and credential in it, with the line number. Mark any value that looks like a key or token, and show me a version where each is replaced by a placeholder or an environment variable. ``` ### Describe what it does ```text In two sentences, describe what this configuration sets up, which model sizes and context settings it uses and what I tested it with, using only what the file and my notes say. Do not claim performance numbers that I have not given you. ``` ### Write the post ```text Write a Mastodon post of up to 450 characters for Tareno that shares the cleaned configuration, states what it sets up and says that it is shared under the MIT license, with a link to the repository [URL] and two hashtags in capitalized words. Count links as 23 characters. ``` ### Save the draft ```text Use Tareno to confirm my Mastodon account [handle@server] 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. ``` ## Mastodon in Tareno - Mastodon's documentation says character limits are set per server, with 500 characters and 23 per link as the example, which leaves room for a short description and a link. - Tareno's configuration for Mastodon gives links an automatic preview, so a repository link shows its title, which helps people judge what they are about to open. - A configuration is often easier to read as an image than as plain text, and Tareno's configuration allows up to four images, each needing a description that states the key settings. - Tareno does not read posts or replies on Mastodon, so Continue cannot gather people's adaptations; you read them in the app. Official rules ([Mastodon documentation: statuses and instance configuration](https://docs.joinmastodon.org/methods/statuses/), checked 2026-10-24): - Character and media limits are set by each server, not by Mastodon itself. The documentation's example server allows 500 characters and 4 attachments, and counts every link as 23 characters. - A scheduled status must lie at least 5 minutes in the future, and a poll cannot be combined with media attachments. - Visibility can be public, unlisted, private (followers only) or direct, and a content warning can be set with spoiler text. ## Mistakes to avoid - Sharing a file with a key in it. Move credentials to environment variables first. - Leaving out the license. The community checks, and an unlicensed configuration cannot be reused. - Claiming performance numbers. State what you tested and nothing more. - Pasting a key into the configuration you share. Keep it in an environment variable. ## What does not work - Continue cannot decide which values in your configuration are confidential, so the author reads the cleaned file and the post. - It cannot read replies or adaptations on Mastodon through Tareno, because Tareno does not expose posts or replies for Mastodon. - It cannot send the post by itself; every time request waits for your approval in the dashboard. ## Frequently asked questions ### Is the configuration I am sharing the same as the Tareno one? No, they are separate files with separate jobs. The Tareno server definition lives in the mcpServers folder; the configuration you share is the one you publish, after secrets are removed. ### How do I know the cleaned file has no secrets left? Ask Continue to list every hostname, path and key again after the replacement, and read the list yourself. A second pass catches values that were hidden in comments or in default settings. ### Can the post carry an image of the file? Yes, up to four images in Tareno's configuration, each with a description. Make the image from the cleaned file, and have the description state the main settings for readers who cannot see it. ### Is an API key acceptable for Tareno here? Where OAuth is not available in your Continue version, yes. Tareno accepts keys from compatible clients as a bearer header, kept in an environment variable and never in the YAML or a prompt. ### Why state the license in the post? Because open-source communities check before they copy, and a configuration without a license is not safe to reuse. A short mention, such as MIT, answers the question before it is asked. ### Could the post appear without a final look from me? No. The request is held in Tareno as pending, and Mastodon hears about it only after your approval in the dashboard. Continue can tell you that it is waiting. ## 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) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Content boards](https://tareno.co/features/content-boards) - [Remote MCP setup](https://tareno.co/docs/mcp)