Share what Continue produced
Continue is open source, model-agnostic and runs in both major editor families, which means the thing it produces has the same problem everywhere: a good long answer sitting in an assistant panel that only the person who ran it can see.
The document might be a dependency review, a walkthrough of an unfamiliar service, or an argument for one of three refactor strategies. All of them are worth circulating. None of them circulate from a side panel.
Add the server, add the rule
Comma is a remote MCP server — a URL plus a Bearer header in Continue's assistant config. The shape matches VS Code setup, and the token comes from API tokens.
Then add a rule so the behaviour is standing rather than something you ask for:
When the deliverable is a document — a review, a comparison, an
investigation — publish it to Comma as an HTML report and reply with the URL.
Do not paste the document into the chat.
Because Continue is model-agnostic, the rule matters more
You will switch models. The assistant that wrote last month's review may not be the one writing this month's. A rule in the configuration is what keeps the output landing in the same place regardless of which model is behind it — which is the difference between a habit and an accident.
What the page gives you
- Faithful rendering. Tables, code blocks and charts arrive as written, in a sandboxed iframe.
- Readers need no editor. Not VS Code, not JetBrains, not a licence.
- Anchored comments. Feedback attaches to the specific claim — see commenting on HTML.
- A stable URL across revisions, so the link in the ticket keeps working.
Worth knowing
- Scope the token to
reports:write— see scoped tokens. - 5 MB per report body.
- Snapshots only. Nothing re-runs when a reader opens the page; for a refresh, use a routine.
Try it
Free — unlimited reports, commenters and revisions.