The AI That's Changing Academia? Must-See for Researchers!

A new wave of research-focused AI is moving beyond “one task at a time” tools and toward a single workspace that can ingest papers, organize a library, and answer questions across documents. One example highlighted here—Petal (spelled “petal” / “P Al Al” in the transcript)—positions itself as generative AI for researchers: upload PDFs or import citations, store and manage a research library, and then chat with either entire collections or specific documents to extract summaries, limitations, and even data-driven details.

The workflow starts with building a document library. After signing up on a free plan for testing, the pricing shown for an edu account is $255 per month (with a student account described as cheaper). The dashboard supports multiple ingestion paths: uploading from a computer, importing via BibTeX, importing via DOI/identifiers, and a web importer (with cloud-drive import described as “coming soon”). Once documents are in place, the interface separates core functions into tabs: a Documents tab for the library, an “AI table” for structured extraction and comparison, and “multi doc chat” for asking questions across selected sources.

A key feature is document-level interaction. Selecting an individual paper opens a side panel with properties and annotation tools, including the ability to highlight specific text and attach comments. From there, the AI can generate responses tied to the highlighted sections. In practice, the transcript shows mixed results: when asked for limitations, the AI returned that the provided document did not mention specific limitations—suggesting it may not infer beyond what’s explicitly present in the selected text. When asked for key points, it produced notes based on the highlighted excerpts rather than the full study, reinforcing that what the user selects can constrain what the AI summarizes.

For cross-paper synthesis, the “AI table” feature is presented as a way to emulate tools like illicit.org (mentioned as a comparison point). Users can create a table with custom columns—such as “main conclusions” or “further work”—and run AI queries per document. The transcript notes a limitation: answers appear to be generated per paper rather than in one “run everything” batch, with a suggestion that credit usage may be part of why bulk generation isn’t immediate.

The multi-document chat is where the tool’s promise becomes most tangible. Using a set of solar-cell papers, it generated research directions and categorized solar-cell types. At first, it struggled to interpret a question about “best” solar cells and didn’t extract efficiencies. After follow-up prompting for efficiencies, it returned numeric ranges (power conversion efficiency from 0.0039 to 3.9) and pulled specific values associated with device variants (e.g., 0.4 for devices with an aluminium cathode and 0.8 for a calcium aluminium cathode). The overall takeaway is that Petal is already useful for structured extraction and targeted synthesis, but performance depends heavily on how precisely questions are framed—especially when pulling quantitative data from dense, multi-document research collections.

The transcript closes by framing this as part of a broader shift: researchers are starting to see AI systems that combine ingestion, organization, annotation, and multi-source Q&A in one place, with expectations that such “single assistant” workflows could substantially boost productivity across fields in the near term.