Feedback dies in Google Docs.
Remarq closes the loop.

Drop-in annotations for any HTML page. Your reviewers highlight text and comment. Your AI agent revises the document and resolves feedback automatically. It doesn't just sit there for weeks.

The feedback loop isn't just faster — it's closed.

Get Started View on GitHub

Quick Start

$ git clone https://github.com/cass-clearly/remarq.git

$ cd remarq

$ echo "POSTGRES_PASSWORD=remarq" > .env

$ docker compose -f docker-compose.remarq.yml up --build

# Server running at http://localhost:3333

Embed in any page

<script

src="https://your-server.com/feedback-layer.js"

data-api-url="https://your-server.com"

data-content-selector="article"

></script>

The Problem

Google Docs is a word processor cosplaying as a collaboration tool.

It was built in 2006. The iPhone didn't exist yet. "AI" meant Clippy. And somehow, in 2026, we're still using the same broken feedback workflow:

1. Reviewer highlights text in Google Docs
2. Leaves a comment that says "this is confusing"
3. Author gets an email notification 4 hours later
4. Author reads the comment, tries to figure out what "confusing" means
5. Author manually rewrites the paragraph
6. Author clicks "Resolve"
7. Repeat 47 more times
8. Question your career choices

Or worse — the Slack workflow:

Screenshot the doc → paste in Slack → "hey can you look at the comments?" → wait 3 days → "oh I didn't see those" → manually copy feedback into the doc → resolve each comment one by one → miss two of them → get a passive-aggressive follow-up

This is not collaboration. This is suffering.

The Solution

Feedback that actually gets acted on.

Here's how it works in the agent era:

1 Your AI agent writes the first draft
2 You drop a single <script> tag onto the page
3 Your team highlights text and leaves comments — no accounts needed
4 Your agent calls GET /comments?status=open
5 Agent revises the document
6 Agent resolves the comments
7 Done.

No copy-paste. No screenshots. No Slack messages. No "can you look at the comments?"
The feedback loop isn't just faster — it's closed.

Two Ways to Use It

Same tool. Solo or team.

Just you and your AI, iterating on a document. Annotations are the shared language — more natural than chat because you're pointing at exact text.

1 Your agent writes a first draft and publishes it to a page
2 You read it, highlight what needs work — "too formal," "add an example," "cut this"
3 You tell your agent: "feedback's ready, go revise"
4 Agent calls GET /comments?status=open, rewrites, resolves
5 Read the new draft. Repeat until you're happy.

Key insight: Pair-writing where annotations are the shared language. Your agent doesn't autonomously poll — you tell it when feedback is ready.

Why Remarq

Built for the agent era. Google Docs was built for 2006.

One script tag. Any HTML page.

Not trapped in a proprietary editor. Not locked into Google's ecosystem. Your blog post, your documentation, your marketing page, your contract — if it's HTML, it's annotatable.

data-api-url="https://your-server"

data-content-selector="article">

</script>

No accounts. Zero friction.

Google makes you sign in with your entire digital identity just to say "this paragraph sucks." Remarq? Type your name and start highlighting. Your reviewers shouldn't need a Google account to give you feedback.

Self-hosted. Your data.

Your feedback lives on YOUR server. Not Google's. Not some VC-funded startup that'll pivot to crypto in 18 months. You own it. Full stop.

The Superpower

The Agent API.

Every comment is anchored to exact text. Every reply is threaded. Your agent knows precisely what to fix, where it is, and what the team said about it. No interpretation needed.

# Your agent checks for open feedback

GET /comments?status=open&document=doc_123

# Gets back structured, actionable annotations

{

"object": "list",

"data": [{

"object": "comment",

"body": "Too technical for our audience",

"quote": "quantum entanglement enables...",

"author": "Sarah",

"status": "open"

}, {

"object": "comment",

"body": "Aim for 8th grade level",

"parent": "cmt_abc123",

"author": "Mike"

}]

}

# Agent revises. Agent resolves. Done.

The Before / After

❌

The Google Docs Way

Reviewer leaves comment

↓

Author gets email

↓

Author reads 47 comments

↓

Author manually edits each one

↓

Author resolves each one

↓

Author misses 3

↓

Gets follow-up email

↓

Repeat

Time: Hours. Sanity: Gone.

✅

The Remarq Way

Reviewer highlights & comments

↓

Agent polls API

↓

Agent revises

↓

Agent resolves

↓

Team reviews next draft

Time: Minutes. Sanity: Intact.

You're not crazy. Everyone hates this.

We didn't have to make up the pain. Just search Reddit.

"The lag on documents with a high number of comments is an EMBARRASSMENT... I need to find something that can fulfill the same role as google docs but actually fucking works."
— r/googledocs

"Once you put something in Google Docs or in Google Drive, you don't own it. They do."
— r/googledocs

"I give people Commenter access for proofreading and feedback... each comment they add is also added into the text itself. It makes the document pretty messy."
— r/googledocs

Google has known about these problems for years. They don't care. You're not a customer — you're the product.

Remarq gives your feedback a place to live where it actually gets acted on, on a server you control, in a format your AI agent can read.

Stop torturing yourself with Google Docs comments.

Your team's feedback deserves better than a graveyard. Build the agent loop. Close the feedback cycle. Ship faster.

Terminal