Analysis
Full semantics & scene coverage
Discover unreachable scenes, broken branches, and script anomalies before your players do. Phase E coverage views sit on top of the Semantics V2 engine.
Revolution in Ren'Py workflow
Finally, a tool that actually helps you build better visual novels.
BranchPy gives Ren'Py creators static analysis, AI-assisted diagnostics, scene coverage, CFG visualization, and media intelligence in one coherent toolbox. The v1.0.0 RC Testing Program is a closed, invitation-only phase before public launch.
Media Intelligence
Media & asset consistency
Track which images, voices, and assets are actually used. Ren'Py adapters with Phase C resolved files help you spot orphaned or broken references.
AI Assist
AI-powered diagnostics
Let BranchPy's AI explain complex warnings, propose fixes, and surface non-obvious issues in your branching logic and pacing.
Tooling
VS Code & CLI workflow
Use BranchPy from the CLI or inside VS Code with QuickFixes, diagnostics, and graphs that fit into your daily dev workflow.
In short:
- RC access is closed and invitation-only. Submission does not guarantee acceptance.
- RC testers get full Pro features with commercial use, excluding Team features.
- RC telemetry is recorded locally during testing. You export and review it manually, then choose whether to upload it. No auto-sends, no opt-out from local collection.
- Installers are unique and non-transferable. Sharing is forbidden and will revoke access.
Status – Editor & OS Support
RC1 focus: First-class support right now is Visual Studio Code.
- ✅ VS Code on Windows & Linux – fully supported (extension + CLI).
- ✅ VS Code on macOS – supported; we're looking for early Mac testers.
- ⚙️ Other editors (PyCharm, Rider, Sublime, Neovim, etc.) – use the BranchPy CLI. We provide documented recipes to wire it into your editor or workflow.
- 🔜 JetBrains / Godot / others – planned for future versions and will appear on the public roadmap.
If you don't use VS Code but still want to help, you're very welcome as an RC tester. Just mention your OS and editor in the form so we can send you the right instructions.
📊 Telemetry for RC Testers
During the RC phase, BranchPy records technical telemetry locally on your machine — things like which commands you run, how long they take, and when errors occur.
- Telemetry is never auto-sent anywhere.
- You can export it yourself via:
branchpy telemetry export --output rc-metrics.json - You can open that JSON file and see exactly what's inside.
- If you're comfortable with what it contains, you can upload it through your Profile → RC Testing portal to help improve BranchPy.
✅ What telemetry collects: Command usage, performance data, error types, platform info
❌ What telemetry NEVER collects: Story text, dialogue, assets, file contents, or PII
Telemetry is focused on metadata only — not your story, not your script content, not your assets. Sharing your metrics is voluntary but extremely helpful for making BranchPy faster, more stable, and more useful for everyone.