# Write social media posts directly in Continue

> Source: https://tareno.co/agents/continue
> Language: en
> Configure Tareno as an MCP server for Continue's agent mode, then share governance rules, configurations and vote posts on LinkedIn, X and Mastodon, approved by you in Tareno.

Teams 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. Those files are small, useful and shareable. With Tareno configured as an MCP server in agent mode, Continue can help you clean such a file and turn it into a post for LinkedIn, X or Mastodon, and Tareno holds every request until you approve it. Tareno has not completed a client test with Continue.

## 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.

## How do I connect Tareno to Continue?

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 `list_accounts`.

## Connect Continue in four steps

1. **Declare the server.** 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.
2. **Choose the remote transport.** 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.
3. **Settle authentication.** 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.
4. **Test in agent mode.** MCP tools are limited to agent mode. Switch to it and ask for `list_accounts`; your account in the answer means the link works. If the tools are absent in plain chat, that is expected.

Server entry shape (JSON form):

```json
{
  "mcpServers": {
    "tareno": {
      "url": "https://tareno.co/api/mcp"
    }
  }
}
```

## Where Continue helps with Tareno

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 governance policy becomes a LinkedIn post

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 file becomes a post on X

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.

### A configuration becomes a Mastodon post with a license

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.

## Prompts to copy

### Check the connection

```text
Use Tareno to list my connected social accounts with platform and account name. Read only: do not create, schedule or publish anything. Tell me which account you would use for a governance post and which for sharing a configuration.
```

### Governance post

```text
Read the policy document [path] and write a LinkedIn post of about 200 words that states the rule, the one exception and what the policy cost us in speed. Do not claim benefits the document does not support, and save the approved text as a draft through Tareno.
```

### List what is private

```text
Read the rule file [path] and list every service name, path, ticket prefix and person it mentions. Show me the rule rewritten without them, keeping the checks unchanged, so that I can turn it into an X post for Tareno within 280 characters.
```

### Clean the configuration

```text
Read my Continue configuration and list every hostname, project name, absolute path and credential in it with the line number. Mark anything that looks like a key, and show a version with placeholders. Then draft a Mastodon post for Tareno that names the license [MIT].
```

### Request the slots

```text
Take the approved drafts [draft IDs] and ask Tareno to schedule them for [Thursday 09:30] in [Europe/Berlin]. Return the action IDs and remind me that each request still waits for my approval in the Tareno dashboard.
```

## Guides by network

- X: [Can Continue share a reusable prompt rule from your repo as an X post?](https://tareno.co/agents/continue/x) ([Markdown](https://tareno.co/agents/continue/x.md))
- LinkedIn: [Can Continue publish a LinkedIn post about your governed agent workflow?](https://tareno.co/agents/continue/linkedin) ([Markdown](https://tareno.co/agents/continue/linkedin.md))
- Mastodon: [Can Continue share an open-source assistant configuration as a Mastodon post?](https://tareno.co/agents/continue/mastodon) ([Markdown](https://tareno.co/agents/continue/mastodon.md))

## Good to know before you start

- Tareno has not completed a client test with Continue, and Continue's MCP page does not mention OAuth. If sign-in does not work in your version, use an API key from an environment variable.
- MCP tools work in agent mode only. Plain chat and edit modes do not show the Tareno tools.
- A file in the .continue folder can hold secrets by accident. Read the cleaned file again before you publish anything derived from it.
- Scheduling, publishing, edits to scheduled posts and deletions create approval actions. Continue can request them but cannot approve them.
- A shared configuration without a license cannot be safely reused. State the license in the post, and make sure you have the right to apply it.

## Continue compared with other editor agents

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.

## Frequently asked questions

### Is Tareno tested with Continue?

No 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.

### Which transport should I use?

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.

### What if my Continue version cannot do OAuth?

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.

### Why are the tools missing in chat?

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.

### How do I make sure a shared file has no secrets?

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.

### Can I run a vote on X or Threads through Continue?

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.

### Will Continue publish without my approval?

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.

### Which Tareno tools will Continue call first?

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.

## Tareno tools used

- `list_accounts`
- `create_drafts`
- `schedule_posts`
- `get_action_status`

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

- [A governed agent workflow on LinkedIn](https://tareno.co/agents/continue/linkedin)
- [A shared rule on X](https://tareno.co/agents/continue/x)
- [A configuration on Mastodon](https://tareno.co/agents/continue/mastodon)
- [Remote MCP setup](https://tareno.co/docs/mcp)
- [Cursor × Tareno](https://tareno.co/agents/cursor)
- [Approval workflows](https://tareno.co/features/approval-workflows)