OpenAI 2026 hackathon

Lumeni

Your AI-powered research assistant agent who learns with you. Making your research process more efficient and allowing you to explore the latest ideas in less time.

Team of 2 · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,090 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

Lumeni is described as an AI-powered research assistant agent that claims to learn with users and automate parts of the research process—specifically in browsing, reviewing, and researching academic papers. The project was built by two individuals (Feiran Wang and Vickie Chen) for the OpenAI 2026 hackathon, using technologies like React, Flask, Python, and OpenAI's Codex model.

The description states that Lumeni supports a full research workflow: fetching papers from arXiv or Google Scholar, helping with note-taking and clarifying questions during review, and enabling in-depth exploration of ideas through conversation. It also claims to remember user preferences and interactions for better recommendations and context-aware assistance.

However, no evidence of revenue, customers, traction, or commercial adoption is provided beyond the authors' own account. The project is presented as a prototype built in a hackathon environment, with no indication of ongoing development or market presence.

The single most important open question: Is there any evidence that Lumeni has moved beyond a proof-of-concept into actual usage by researchers?

Back to contents

What The Product Actually Is

The description states that Lumeni is an AI-powered research assistant agent designed to help users navigate academic literature. It claims to support three core phases of the research process:

  • Browse: Fetching papers from arXiv or Google Scholar, with assistance in recommendations.
  • Review: Helping users take notes and answer questions about selected papers.
  • Research: Allowing users to organize papers in an Archive, chat with Lumeni about each paper, and store conversations and documentation.

Lumeni is described as a self-learning agent that remembers user preferences and interactions to improve future recommendations and context-aware responses.

It also claims to integrate with tools like Codex (GPT-5.6), support a frontend built with React 18 + TypeScript, and a backend using Python + Flask.

Inference: Based on the description, Lumeni appears to be an early-stage prototype focused on automating parts of academic research workflows through AI agents.

Back to contents

Positioning & Claim Evolution

The authors state that Lumeni is positioned as an AI-powered research assistant agent who learns with you, aiming to make the research process more efficient by removing "brute work" and allowing users to explore ideas faster.

They claim Lumeni can go beyond simple chatbots, offering meaningful interaction and memory across user sessions. The positioning evolves from a tool for paper discovery to one that supports full research lifecycle management—browse, review, and research—with context-awareness and self-improvement capabilities.

Inference: The positioning suggests an ambition to become a personal AI assistant tailored to researchers' needs, evolving from a basic agent into a more sophisticated knowledge management system.

Back to contents

Target Customer & ICP

The description states that Lumeni is intended for researchers, particularly those who spend time hunting for papers and rebuilding experiment environments. It targets individuals looking to streamline their research workflow by automating routine tasks like paper discovery, note-taking, and idea exploration.

There is no explicit segmentation beyond "researchers", nor any indication of specific user personas or use cases beyond general academic research.

Inference: The ICP likely includes graduate students, postdocs, or researchers working in fields with heavy literature review requirements. However, the description does not define a clear customer profile or niche.

Back to contents

Business Model & Pricing Evidence

There is no evidence of pricing, monetization strategy, or business model in the provided description. The authors do not mention any plans for paid features, subscriptions, or revenue streams.

The project is presented as a hackathon submission and lacks any indication that it has moved into commercial development or customer acquisition.

Inference: No business model or pricing information is evident; this remains unaddressed in the self-reported description.

Back to contents

Technical & Delivery Signals

The authors state that Lumeni was built using:

  • Frontend: React 18 + TypeScript, bundled with Vite
  • Backend: Python + Flask
  • AI models: OpenAI's Codex (GPT-5.6)
  • Other tech: Git, bash, CUDA, JSONL, REST API, prompt engineering, RAG, SPA

They also describe challenges such as:

  • Silent proxying of chat messages to a non-functional external agent service
  • Misconfigured third-party model backends requiring fallback to Codex CLI
  • Context loss between frontend and backend that was later fixed by threading paper context into system prompts

These indicate a prototype built under time constraints, with some technical limitations and debugging issues.

Inference: The technical stack suggests a functional but early-stage product, likely not production-ready. The presence of known issues implies limited testing or iteration beyond the hackathon phase.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, adoption, or user engagement beyond the authors' own account. No data on active users, retention, usage frequency, or feedback from real-world users is provided.

The project is explicitly described as a hackathon submission, and there are no references to deployment, customer interviews, or product-market fit validation.

Inference: The product shows no signs of maturity or traction beyond its initial development phase. It is likely in an experimental or prototyping stage.

Back to contents

Competitive Context

There is no mention of competitors or competitive landscape in the provided description. No references to existing tools for academic research automation, literature review platforms, or AI agents in research are included.

The authors do not discuss how Lumeni compares to other solutions in the market.

Inference: No competitive context is evident; this leaves open questions about differentiation and positioning relative to similar tools.

Back to contents

Key Risks & Red Flags

  • No evidence of commercial viability or traction: The project is described as a hackathon submission with no indication of real-world usage.
  • Prototype limitations: Technical issues such as silent failures, misconfigured APIs, and context loss suggest the product is not yet stable or scalable.
  • Unclear business model: No mention of monetization, pricing, or revenue paths.
  • Self-reported only: All claims are unverified; no third-party validation or external data supports the stated functionality.

Inference: The lack of traction, commercial clarity, and technical robustness raises significant concerns about whether Lumeni is ready for product-market fit or investment consideration.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific research workflows does Lumeni currently automate? How do you measure success in those areas?
  2. Have you tested Lumeni with actual researchers? If so, what feedback did they provide?
  3. Is there a plan to move beyond the hackathon prototype into a scalable product or service?
  4. How do you intend to monetize Lumeni? Are there any early adopters or pilot programs?
  5. What are your plans for improving reliability and performance after the initial prototype phase?

Back to contents

Investment/Partnership Verdict

Not evidenced: There is no evidence of revenue, customers, traction, or commercial viability beyond the authors' own description.

The project is described as a hackathon prototype, with no indication of ongoing development, user adoption, or product-market fit. The self-reported claims are aspirational but unproven.

Confidence level: Low

This is not a product ready for investment or partnership consideration based on the information provided. Any further diligence would require evidence of real-world usage, customer feedback, and business model validation.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.