DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find open-access papers and add them to your library with Thesys Core

Search OpenAlex and arXiv in one pool, preview records, and add the useful ones to your Thesys library.

  • Research
  • Beginner
  • 60 minutes
  • From the README
  • Any agent

Who it is forA literature reviewer starting a new topic who needs a quick list of open-access papers without checking several sites.

The problemOpen-access papers are spread across several sources, so building a first reading list takes time.

The outcomeA library of relevant open-access papers, each previewed and ready for chat and citation export.

What you need first

  • Docker, or Python 3.11+ and Node.js 20+ for the local setup
  • An OpenAI API key for chat
  • A contact email for the EMAIL setting used by citation lookup
  • A TypeSafe API key only if you want the Compare feature

Steps

  1. Run cp backend/.env.example backend/.env and set EMAIL in backend/.env. Add OPENALEX_API_KEY only if you have one.
  2. Run docker compose up --build from the repo root and open http://127.0.0.1:5000.
  3. Search for your topic in the Discover section to get OpenAlex and arXiv results in one list.
  4. Preview a record, open its link if you want the source, and add the paper you want to your library.
  5. Run docker compose down to stop the workspace. Added papers stay in the thesys-data volume.

Prompt for your agent

Use the Sreehari05055/thesys-core repo to start the Docker workspace, search Discover for <your topic>, and add the five most relevant open-access papers to the library. Report the titles and links of the papers added. Verify that each added paper appears in the library list.

Caveat. The README describes only open-access sources, OpenAlex and arXiv, so paywalled literature is not covered by this workflow.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page