Extract the rules
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.Loading...
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.
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.
Last reviewed 2026-10-24 · Markdown version for AI agents
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.
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.
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.
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.
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.
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.
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.
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.
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.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.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.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.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: Microsoft Learn: LinkedIn Posts API, 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_accountsYes, 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.
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.
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.
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.
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.
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.