Settings & customization
Help, diagnostics & updates
Find the app version, reproduce an issue, and open the right support resource.
Ce contenu n’est pas encore disponible dans votre langue.
Open Settings → Help & About. This page gathers version information, project links, support, and learning resources.
App version
Section titled “App version”Read the version shown beside Oleafly. Include it when reporting a problem so someone else can test the same build.
Cite Oleafly in a paper
Section titled “Cite Oleafly in a paper”The Cite Oleafly in your paper card contains a ready-to-copy BibTeX entry for the version you are using. Choose Copy BibTeX, paste it into the project’s bibliography, and cite the key oleafly.
With a project open, you can also run Cite Oleafly in this paper from the command palette. Oleafly adds the entry to the bibliography declared by the document and tells you which citation syntax to use. If no bibliography exists, it shows the entry without changing project files.
Check the citation guidance for your venue before submission. The link below the card opens the same software record through GitHub’s citation menu.
Copy Info
Section titled “Copy Info”Choose Copy Info to copy the app version and, where available, platform, architecture, and OS version. Paste it into your issue alongside the steps that reproduce the problem.
Start tour
Section titled “Start tour”Choose Start tour to close Settings and launch the relevant guide: the home tour from the library, or the workspace tour from a project.
Documentation
Section titled “Documentation”Choose Documentation to open these product guides. Start with the guide for the control or workflow you are using.
Choose Learn for LaTeX lessons. The lessons explain the document language; product docs explain where to find its tools in Oleafly.
Report a crash
Section titled “Report a crash”Choose Report a crash (attach logs) to start a crash report. Review the report and attachments before submitting them. Include what you clicked, what happened, what you expected, and whether the issue repeats in a blank project.
Community
Section titled “Community”Choose Discord to join the Oleafly community server. Questions, bug reports, feature ideas, and everyday conversation all happen there, with other researchers and the people building the app. It is free, and you only need a Discord account. Join our Discord at the bottom of the Settings sidebar opens the same invite.
The Discord row shows how many members are online. Oleafly asks Discord for that number only while Help & About or the About window is open. The request carries no account, project, or usage information, and offline mode skips it.
Choose Oleafly, the row with the X logo, to follow releases and development.
What’s new
Section titled “What’s new”Choose What’s new for the project’s change history. The product highlights link features to their guides; app updates explains installing an update.
License
Section titled “License”Choose License to read the terms for the desktop application.
Support the project
Section titled “Support the project”The project and support links open Oleafly’s public pages. A GitHub star helps other researchers discover the app.
Write a useful report
Section titled “Write a useful report”- Copy the app information.
- Repeat the issue with the smallest document that still shows it. For compilation problems a small example file is more useful than a screenshot alone. Remove unrelated manuscript material before you share it.
- List the actions in order, including the engine and layout.
- Include the first relevant compile error or a screenshot of the failing control.
- State whether restarting the app changes the result.
For a build failure, begin with Compiling & logs. For missing AI tools, check the model’s connection and capability state under Model providers.