Loading...
×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.
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.
Last reviewed 2026-10-24 · Markdown version for AI agents
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.
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.
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.
A hosted endpoint calls for streamable-http among the transports that Continue supports. The address comes from the Remote MCP setup page.
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.
MCP tools are limited to that mode. A call to list_accounts that returns your Mastodon account shows the link is good.
Ask Continue to list every hostname, project name, path and key in the file. A shared configuration should use placeholders and environment variables.
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.
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.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 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.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.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: Mastodon documentation: statuses and instance configuration, read on 2026-10-24. 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_accountsNo, 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.
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.
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.
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.
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.
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.