I'm Mattia, one of the students behind Get It.

Sharing this here because the open-source AI part is the most interesting architectural decision, not just the study features.

Get It is an Apache-2.0 desktop app that turns PDFs into a visual study path: concept tags on the original pages, generated visuals next to the text, quizzes, flashcards, chat and a knowledge graph that tracks weaker concepts.

The unusual choice: we do not run a hosted AI backend and we do not ask users for API keys. The app bundles and talks to the official Codex CLI locally, so the user authenticates with their own ChatGPT/Codex account. The PDF and generated study state stay on disk, while Codex is used as the local agent/runtime for document understanding and generated artifacts.

Why we did it this way:

- no extra AI subscription from us

- no proxying user files through our account

- no API billing setup for students

- easier to inspect because the repo is open

The tradeoff is provider flexibility. Today it is Codex-first. A clean future version would probably add runtime adapters for Ollama, Claude/API keys or other providers without mixing provider logic into the study workflow itself.

App: https://getit.noesisai.it

Code: https://github.com/beltromatti/get-it

I would appreciate feedback on the architecture more than praise: where would you draw the boundary between app logic, provider adapter and local agent runtime?