Stop reading agent slop
Every agent draft lands as a pending proposal next to the original block. No silent rewrites, no losing the wording you trusted to a hallucinated edit.
Block-level provenance. Draft-review primitives. One-click publish to GitHub. Let Claude and Codex draft your PRDs, RFCs, and runbooks while you stay in control of every paragraph.
2 agent drafts in carousel · click to expand diff
3 conflicting drafts — Synthesize via Groq ready
0%
Of edits across pilot teams come from AI agents
0h
Median time-to-review on docs co-edited with agents
0%
Of approved blocks ship with provenance preserved in Git
Every agent draft lands as a pending proposal next to the original block. No silent rewrites, no losing the wording you trusted to a hallucinated edit.
When two agents propose competing rewrites, the smart-merge button calls Groq llama-3.3-70b and replaces the block with a unified draft you still get to approve.
Every verdict — approve, reject, edit — is recorded against the block, the reviewer, and the proposing author kind. Compliance teams stop chasing screenshots.
Why teams pick Quillstream
Quillstream is the missing layer between Notion-style co-editing and Git-style review. Built specifically for docs that humans and agents both touch.
FAQ
Everything teams ask before they let an agent into a shared doc.
Quillstream is a markdown workspace where humans and AI agents co-edit docs — PRDs, RFCs, specs, runbooks, changelogs. Every paragraph carries ownership and review state, so you can let Claude or Codex draft sections without losing control of what ships.
Notion and Google Docs treat AI as a passive autocomplete inside one user’s session. Quillstream treats agents as first-class authors with their own REST identity, drafts that survive across sessions, and a review queue that escalates to a human verdict.
A PR review is repo-wide and once-per-merge. Quillstream gives you block-level review inline as the doc evolves: drafts carousel per paragraph, threaded notes anchored to a block, critique state machine, and one-click smart-merge for conflicting proposals.
Any HTTP client. Quillstream ships POST /v1/docs, PATCH /v1/docs/:id/sections/:section_id, GET /v1/docs/:id/feedback plus webhook events (section.approved / section.rejected / document.published). Claude, Codex, and in-house agents all work the same way.
Your Git repo. Quillstream connects to the GitHub repos you select, edits markdown in place, and writes a sibling provenance file alongside each doc. If you uninstall Quillstream tomorrow, every approved block stays in your repo as plain markdown.
When a block has two or more conflicting drafts, a Synthesize button calls Groq llama-3.3-70b with all the drafts plus the original. The model returns a unified rewrite that lands as a new pending draft — you still approve before it replaces the body.
Yes — one connected GitHub repo, three active documents, single user, public repos only. The Pro tier (€15/mo) unlocks unlimited repos, unlimited docs, one agent API token, and AI smart-merge.
Yes. The /demo route is fully clickable as either a Lead reviewer (Maya), an Editor (Theo), or an Agent token (Codex) — three pre-seeded personas with role-aware capabilities and persona-switch without re-auth.
Still have questions? Contact us
Block-level provenance. Draft-review primitives. One-click publish to GitHub. Let Claude and Codex draft your PRDs, RFCs, and runbooks while you stay in control of every paragraph.
2 agent drafts in carousel · click to expand diff
3 conflicting drafts — Synthesize via Groq ready
0%
Of edits across pilot teams come from AI agents
0h
Median time-to-review on docs co-edited with agents
0%
Of approved blocks ship with provenance preserved in Git
Every agent draft lands as a pending proposal next to the original block. No silent rewrites, no losing the wording you trusted to a hallucinated edit.
When two agents propose competing rewrites, the smart-merge button calls Groq llama-3.3-70b and replaces the block with a unified draft you still get to approve.
Every verdict — approve, reject, edit — is recorded against the block, the reviewer, and the proposing author kind. Compliance teams stop chasing screenshots.
Why teams pick Quillstream
Quillstream is the missing layer between Notion-style co-editing and Git-style review. Built specifically for docs that humans and agents both touch.
FAQ
Everything teams ask before they let an agent into a shared doc.
Quillstream is a markdown workspace where humans and AI agents co-edit docs — PRDs, RFCs, specs, runbooks, changelogs. Every paragraph carries ownership and review state, so you can let Claude or Codex draft sections without losing control of what ships.
Notion and Google Docs treat AI as a passive autocomplete inside one user’s session. Quillstream treats agents as first-class authors with their own REST identity, drafts that survive across sessions, and a review queue that escalates to a human verdict.
A PR review is repo-wide and once-per-merge. Quillstream gives you block-level review inline as the doc evolves: drafts carousel per paragraph, threaded notes anchored to a block, critique state machine, and one-click smart-merge for conflicting proposals.
Any HTTP client. Quillstream ships POST /v1/docs, PATCH /v1/docs/:id/sections/:section_id, GET /v1/docs/:id/feedback plus webhook events (section.approved / section.rejected / document.published). Claude, Codex, and in-house agents all work the same way.
Your Git repo. Quillstream connects to the GitHub repos you select, edits markdown in place, and writes a sibling provenance file alongside each doc. If you uninstall Quillstream tomorrow, every approved block stays in your repo as plain markdown.
When a block has two or more conflicting drafts, a Synthesize button calls Groq llama-3.3-70b with all the drafts plus the original. The model returns a unified rewrite that lands as a new pending draft — you still approve before it replaces the body.
Yes — one connected GitHub repo, three active documents, single user, public repos only. The Pro tier (€15/mo) unlocks unlimited repos, unlimited docs, one agent API token, and AI smart-merge.
Yes. The /demo route is fully clickable as either a Lead reviewer (Maya), an Editor (Theo), or an Agent token (Codex) — three pre-seeded personas with role-aware capabilities and persona-switch without re-auth.
Still have questions? Contact us