Project Info

Winner

Letta: Honorable Mention

PaperTrail

Devpost

Inspiration

As a researcher, I find literature review tedious and impersonal. Generic search yields piles of irrelevant results. What if an AI agent learns how you learn, captures your interests and dislikes, reads papers in parallel, and surfaces what matters? I built PaperTrail to bring deep personalization to research discovery.

What it does

PaperTrail uses multi-agent orchestration with persistent memory. Describe a research topic and it: Searches the papers Scores paper relevance against your interests, goals, expertise, and feedback Returns relevant, personalized recommendations Learns from feedback to refine future suggestions and become more personal Reads specific papers on demand and answers questions in real time Sleeptime compute generates insights over previous conversations, further personalizing the agent. All personalized through a memory layer that adapts to your workflow. How I built it Multi-agent orchestration (Letta): supervisor agent generates targeted queries; workers fetch papers via Jina AI and evaluate in parallel. Deep memory architecture (Letta): profiles store interests, dislikes, goals, expertise, explanation style; conversation history; and feedback tables linking votes to preferences. Personalized scoring: workers use memory blocks to align recommendations to your profile. Real-time learning: each vote updates the user model, shaping future recommendations. Challenges Latency: parallel worker evaluations enabled fast, accurate recommendations. Personalization: memory blocks encoding interests, dislikes, expertise, and style lifted precision. Threading fine-grained preferences into agent prompts reliably. Accomplishments Deep personalization with feedback loops. Smooth real-time paper reading and Q&A. Clear UX that hides multi-agent complexity. Results improve with usage. What I learned Modern LLM orchestration frameworks are powerful. Memory matters: persistent user context beats session-only approaches for quality. Multi-agent systems call for careful supervisor–worker coordination and state handling.

What's next

Broader coverage: expand beyond arXiv (Google Scholar, semantic scholar). Fine-tuning with user feedback data. Collaboration features to share recommendations. Read-paper sessions with collaborative learning and notes. Big picture: personalized research that learns with you.

Analysis

Compare with all teams

View

Metric

Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.

Technology

Found in codeClaimed only
  • CSSIn code
  • Next.jsIn code
  • ReactIn code
  • SQLIn code
  • SupabaseIn code
  • Tailwind CSSIn code
  • TypeScriptIn code
  • PostgreSQLClaimed

7 of 8 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.

AI coding agents

No AI coding agent signals were found in this repository.

Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.

Codebase size

Source size

522 KB

Source files

93

Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.

0 stars