Documentation
AI-generated documentation that stays in sync with what was actually built. User docs, release notes, and technical documentation — all created automatically from the cycle's context.
The documentation phase is an optional stage between review and cycle completion. When enabled, the AI generates three types of documentation based on what was actually built, reviewed, and accepted in the cycle — not from aspirational specs, but from real implementation outcomes.
Generated docs are fully editable in a rich-text editor before the cycle completes. They can be included as links in the GitHub PR or uploaded as public PDFs.
Documentation is the first thing to be cut when teams are under pressure, yet it is critical for onboarding, support, and compliance. By generating it automatically from actual build outcomes, Bynary ensures documentation exists without adding to anyone's workload.
- •Always accurate — Generated from what was actually built, not what was planned
- •Three perspectives — End-user docs, stakeholder release notes, developer technical docs
- •Editable before shipping — Full WYSIWYG editor for refinement
The documentation editor with tabs for each doc type and auto-generated content.
Configure Per-Project
Automatic Generation
Edit and Refine
Regenerate if Needed
Complete or Skip
Three document types, each independently configurable per project:
End-user facing documentation describing new features, how to use them, and done whens outcomes.
Stakeholder-facing changelog categorizing changes, summarizing review outcomes, and including build statistics.
Developer-facing documentation covering architecture impact, file changes, implementation details, and technical decisions.
Documentation behavior is configured per-project in project settings:
Each of the three doc types can be independently set to mandatory, optional, or never.
Choose between private links (require app login) or public links (docs uploaded as PDFs to Supabase Storage with unguessable URLs).
Is the documentation phase required?
No. If all three document types are set to 'never' in project settings, the cycle skips the documentation phase entirely and goes directly from review to completed.
Can I edit the generated docs?
Yes. The documentation opens in a full WYSIWYG markdown editor. You can edit freely, and changes auto-save. You can also regenerate any document type for a fresh AI-generated version.
Can two people edit the same document?
Not at the same time. A lock stops two people editing the same document type at once, and admins can release a stale lock.
How are docs included in the PR?
When completing the cycle, the GitHub PR body includes a Documentation section with links to each generated document. The link format depends on your 'doc link visibility' setting.
What model generates the documentation?
Bynary selects the Claude model automatically, using adaptive thinking for higher quality output.
We've thought carefully about these areas. Some are intentional design choices, others are on our roadmap.
Documentation is generated and stored as markdown. The WYSIWYG editor provides a visual editing experience, but the underlying format is markdown.
Edits to generated docs overwrite the previous version. There is no built-in version history. The original AI-generated version can be recovered by using the regenerate feature.
When using public link mode, docs are converted to PDF using pdfkit. The PDF rendering covers common markdown elements but may not perfectly render complex tables or nested structures.