BibTeX · LaTeX · Literature management
BibTeX Literature Management for LaTeX Workflows
Literature management ends in writing, not in collecting. Reading, organizing, and export should share one library, instead of being reconciled by hand the night before a draft.
Preserve bibliographic context
Import from identifiers, links, the browser connector, or a Zotero library while keeping tags, notes, and attachments. Check title, authors, and year in Paper Info. Keep organizing locally as the project changes.
Export when you write
Export BibTeX or BibLaTeX and keep the editor and build you already know. Agentero is not another LaTeX IDE. It keeps citation records next to the reading context that produced them.
Cite from the library you actually read
An Agent can help summarize and connect context, but the entries that reach a .bib file still come from your Vault. That is safer than letting a web model invent citations, and easier to audit before submission.
Zotero can stay in the mix
If you still use Zotero for a group library or a Word plugin, you do not have to cut over on day one. Import into Agentero for reading and Agent work, then export .bib when you write. The two paths can overlap.
The CLI is for batch work
The desktop app is for reading. The CLI can import papers, write metadata, and drop notes from a script — useful if you already manage a paper repo with Make, just, or a shell.
Frequently asked questions
- Which export formats are supported?
- BibTeX and BibLaTeX, which cover most LaTeX workflows. If you need a journal CSL, export first and convert in the tool you already use.
- Will it rename my citation keys?
- Imports keep bibliographic data where they can. Still check the important keys before you compile, especially after a Zotero migration.