# Can Continue publish a LinkedIn post about your governed agent workflow?

> Source: https://tareno.co/agents/continue/linkedin
> Language: en
> Last reviewed: 2026-10-24
> Connect Continue to Tareno to turn an approved agent policy, its permitted tools and its review checkpoint into a LinkedIn post, approved by you 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: LinkedIn · Hub: [Continue and Tareno](https://tareno.co/agents/continue)

## Short answer

**Can Continue write a LinkedIn post about how our team governs its coding agents?**

Yes, once Tareno is configured as an MCP server in Continue's agent mode. Continue can turn your approved policy, the tools agents may use and the review checkpoint into a LinkedIn draft and save it through Tareno. Tareno has not completed a client test for Continue, and Continue's MCP page does not mention OAuth. Scheduling needs your approval.

Platform teams that let developers use coding agents usually write a policy: which tools an agent may call, which actions need a human and where the review sits. Those rules are exactly what other teams want to see, and they make a convincing LinkedIn post because they are specific. Continue is open source and configured in files you control, so the setup itself fits a team that cares about governance. This page follows a platform team publishing its agent policy, covering how Continue loads MCP servers, why it only works in agent mode and what to check when authentication is not OAuth.

## Example: a platform team shares its agent policy

Imagine a platform team of six that wrote a one-page policy for coding agents: read-only by default, write access only through pull requests, and a human check before anything leaves the company. The lead asks Continue in agent mode to read the policy document and turn it into a 220-word LinkedIn post for engineering leaders. Continue lists the three rules, the one exception the team allowed and the cost of the policy, which was slower merges. It marks a sentence about "zero incidents" as unsupported by the document. The lead removes it, Continue confirms her profile with `list_accounts` and saves the draft through `create_drafts`, and she requests a Monday 08:30 slot that waits as a pending action.

## Step by step

1. **Create the MCP server file.** Continue's documentation says to create a .continue/mcpServers folder at the top of your workspace and add a YAML file, or put an mcpServers block in the main config. Standalone block files need name, version and schema metadata.
2. **Use a supported transport.** The documentation lists stdio, sse and streamable-http as supported transports. Tareno's hosted endpoint is a remote server, so choose streamable-http and give it the endpoint from the Remote MCP setup page.
3. **Check authentication.** The page does not mention OAuth. If your Continue version cannot complete an OAuth sign-in for a remote server, Tareno also supports API keys for compatible clients, sent as a bearer header and kept in an environment variable, never in a file you commit.
4. **Switch to agent mode.** Continue's documentation says MCP can only be used in agent mode. Switch modes, then ask for `list_accounts` as a read-only test; if your LinkedIn profile appears, the connection works.
5. **Give the policy and the cost.** Share the policy document and ask Continue for the rules, the exception and the cost. A governance post that admits what the policy slowed down is more credible than one that lists only benefits.
6. **Save, request and approve.** Continue saves the post through `create_drafts`. Give a date, a time and an IANA time zone, and approve the pending request in the Tareno dashboard.

## Prompts to copy

### Extract the rules

```text
Read docs/agent-policy.md and list the rules agents must follow, the one exception we allow and the cost the policy has for developers. Use only what the document states and mark anything you had to infer.
```

### Draft the post

```text
Write a 220-word LinkedIn post for [engineering leaders] about our agent policy: read-only by default, writes only through pull requests, a human check before anything leaves the company. Include the cost, slower merges, and flag every claim that the policy document does not support.
```

### Save the draft

```text
Use Tareno to confirm my LinkedIn profile [name] and save the approved text as a draft. Return the draft ID and the text, and do not request a publishing time until I give you the day and the time zone.
```

### Request the slot

```text
Ask Tareno to schedule draft [draft ID] for [Monday 08:30] in the [Europe/Vienna] time zone. Return the pending action ID and remind me that I must approve it in the Tareno dashboard before it can publish.
```

## LinkedIn in Tareno

- Tareno cannot read LinkedIn posts published outside Tareno or comments on them, so Continue cannot see how other teams described their agent policies.
- LinkedIn's documentation says posting as a member needs the w_member_social permission, granted when you connect your own profile in Tareno.
- Tareno's configuration allows up to 3,000 characters on LinkedIn, so a 220-word post can include a short list of rules and a link to the full policy.
- LinkedIn offers no transcripts through Tareno, so a recorded internal talk about the policy has to be summarized in writing first.

Official rules ([Microsoft Learn: LinkedIn Posts API](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api), checked 2026-10-24):

- Organic posts can contain text, images, videos, documents, articles, several images or polls. Organic carousels are not supported by the Posts API; they exist only as sponsored content.
- Posting for a company page requires one of the page roles administrator, direct sponsored content poster or content admin. Posting as a member needs the w_member_social permission.
- An article post needs its title, description and thumbnail set explicitly, because the API does not scrape the link for a preview.
- Reading a member's own posts needs r_member_social, a restricted permission that is available to approved users only.

## Mistakes to avoid

- Claiming that governance prevented incidents. Without a baseline, say what the rules require, not what they have avoided.
- Publishing the exact permission list of internal tools. Describe the principle, not the inventory, so the post does not map your systems.
- Forgetting agent mode. In plain chat the Tareno tools will not appear, which looks like a broken connection.
- Putting an API key into a committed YAML file. Use an environment variable, and keep the file free of credentials.

## What does not work

- Continue cannot use the Tareno tools outside agent mode, so a plain chat will not show them however the server is configured.
- It cannot decide which parts of your policy are safe to publish, so a person has to read the draft before approval.
- It cannot publish by itself, since scheduling and publishing requests wait for your approval in the Tareno dashboard.

## Frequently asked questions

### How does Continue talk to the Tareno MCP server?

Yes, as a remote MCP server using the streamable-http transport that Continue's documentation lists. Tareno has not completed a client test for Continue, and the page does not mention OAuth, so check how your version authenticates.

### Where does Continue load MCP servers from?

From a .continue/mcpServers folder in your workspace, where each YAML file defines a server, or from an mcpServers block in the main config. Standalone files need name, version and schema fields at the top.

### Why don't I see the Tareno tools in chat?

Continue's documentation says MCP can only be used in agent mode. Switch to agent mode, check the server loaded and ask for `list_accounts` as a read-only test before any draft.

### What if my Continue version has no OAuth for remote servers?

Tareno also supports API keys for compatible clients, sent as a bearer header. Keep the key in an environment variable, never in a committed file or a prompt, and replace it in Tareno if it ever leaks.

### Will the post publish without my approval?

No. A scheduling request becomes a pending action in Tareno. LinkedIn receives the post only after you approve it in the dashboard, and Continue can only report that it is pending.

### Can Continue read our policy from the repository?

Yes, it can read the policy file you point it at, and the post will rest on that document. Ask it to mark anything inferred, and keep the permission inventory out of the public text.

## 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)
- [LinkedIn with Tareno](https://tareno.co/channels/linkedin)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Content boards](https://tareno.co/features/content-boards)
- [Remote MCP setup](https://tareno.co/docs/mcp)