Loading...
Continue/TarenoTeams that use Continue write down how they want an assistant to behave: a rule that tests come first, a prompt that reviews a migration, a configuration for a local model.
Continue / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
ContinueIllustrated demo · no live account
Create a YAML file in a .continue/mcpServers folder at the top of your workspace, or add an mcpServers block to the main config, and choose the streamable-http transport with the hosted endpoint. Continue's MCP page does not mention OAuth, so an API key in an environment variable is the fallback. Use agent mode and ask for your connected accounts.
Continue's documentation says a YAML file in the .continue/mcpServers folder defines a server, as does an mcpServers block in the main configuration. Stand-alone files carry name, version and schema fields.
Continue lists stdio, sse and streamable-http. A hosted endpoint calls for streamable-http, with the address from the Remote MCP setup page, as the example on the right shows for the JSON form.
Because the MCP page is silent on OAuth, check whether your version can complete a sign-in for a remote server. If not, Tareno accepts an API key from compatible clients as a bearer header; keep it in an environment variable, never in a committed file.
MCP tools are limited to agent mode. Switch to it and ask for your connected accounts; your account in the answer means the link works. If the tools are absent in plain chat, that is expected.
{
"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.
Continue's configuration is open and lives in your repository, which makes it both a source of content and a risk. These three jobs use the first and manage the second, each with a workflow page.
A team that decided which tools its agents may use and where a human reviews the result has something worth explaining. Continue turns the policy document into a post that states the rule, the exception and the cost, including what the policy slowed down, which is what makes a governance post credible.
A rule such as review migrations for locks, a rollback and data volume fits in 280 characters once names are stripped. Continue lists every service name, path and ticket prefix in the file, rewrites it generically and counts the characters so the post fits without cutting the checks.
Open-source communities copy configurations. Continue reads yours, finds hostnames, project names and any key stored where an environment variable belongs, replaces them and writes a post that says what the configuration sets up and under which license it is shared.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Cursor, GitHub Copilot, Junie and Antigravity also connect to Tareno from an editor. Continue differs in that its configuration is plain files in your repository and that it can run with the models you choose, including local ones. That openness is why a shareable configuration is the natural content, and why a secret check comes first.
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 client test has been completed. The setup follows Continue's own documentation, so confirm the configuration with a read-only call in agent mode before you rely on it for a post you care about.
Streamable-http, among the three that Continue lists, because Tareno's endpoint is hosted. The address comes from the Remote MCP setup page. Stdio and sse apply to local or older server styles and are not what you need here.
Tareno accepts API keys from compatible clients, sent as a bearer header. Store the key in an environment variable and reference it from the configuration, so that it never appears in a committed file or in a prompt.
Continue's documentation says MCP can only be used in agent mode. Switch modes, confirm that the server loaded and ask for the account list. If your account shows up, the rest of the workflow is available.
Ask Continue to list every hostname, path and key after the replacement and read that list yourself. A second pass catches values hidden in comments or defaults. The post and any image of the file get the same check.
A vote is a post that asks for replies, and counting them needs a script. Tareno reads replies on Threads, not on X, so the vote belongs on Threads. Continue can draft the post and help write the counting script.
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. Continue can only report that the action is pending.
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` shows what became of the request.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.