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 #6,573 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Science/Retrace is a self-reported AI research workspace built using GPT-5.6 and subagents (specifically Luna medium), designed to support structured workflows for learning, reviewing, researching, experimenting, and writing with retraceable evidence and reproducible loops. It operates as a local workspace with five modes: Chat, Learn, Review, Deep Research, and Auto Research.
What changed
The project was submitted to the OpenAI 2026 hackathon, indicating an early-stage development effort focused on exploring agentic AI workflows for research tasks. The author describes it as a large project that exceeded initial scope, suggesting iterative experimentation and feature expansion during development.
Single most important open question
Is there any evidence of actual usage or adoption beyond the developer's own testing? The description lacks any mention of users, customers, or real-world impact — all claims are self-reported and unverified.
What The Product Actually Is
The description states that Science/Retrace is a local workspace built with GPT-5.6 and subagents (Luna medium), offering five distinct modes:
- Chat: For project-aware discussion and inspection, keeping files read-only.
- Learn: Turns up to ten local source files into items for questions, presentations, and quizzes.
- Review: Runs structured reviews of PDF, DOCX, TXT, or LaTeX documents, producing findings, annotations, and revised outputs.
- Deep Research: Creates editable LaTeX source and compiled PDF reports on a topic.
- Auto Research: Allows users to define objectives, budgets, permissions, workflows, and stopping conditions for agentic research loops.
It is built using Codex CLI and integrates tools like Git, GitHub, Playwright, Python, Node.js, SQLite, and others. The author notes that no manual coding was done; everything was built with the help of GPT-5.6 and subagents.
Evidence
- Self-reported by the author.
- No independent verification or demonstration provided.
Positioning & Claim Evolution
The author positions Science/Retrace as an alternative to traditional AI research tools that rely solely on chat interfaces, which they claim are inconvenient for serious work due to lack of traceability and file management. The goal is to provide a guided approach that is accessible to non-coders but still supports advanced features like LaTeX integration.
They describe it as:
- A local workspace
- Approachable for non-coders
- With tools like LaTeX contained inside
- Designed for learning, reviewing, researching, experimenting, and writing with retraceable evidence
This positioning implies a shift from generic chat-based AI tools toward more structured, reproducible research environments.
Evidence
- Self-reported by the author.
- No external validation or market positioning data.
Target Customer & ICP
The description does not clearly identify a specific customer segment or ideal customer profile (ICP). However, it suggests:
- Users who engage in serious AI research
- Individuals who need to learn from source material, review papers, or develop research documents
- People working with LaTeX, PDFs, and structured workflows
There is no indication of whether the tool targets students, researchers, academics, or professionals.
Evidence
- Self-reported by the author.
- No evidence of target personas, user types, or segmentation.
Business Model & Pricing Evidence
No information about pricing, monetization strategy, or business model is provided in the description. The project appears to be a hackathon submission with no commercial intent evident.
Evidence
- Not evidenced.
- No mention of revenue streams, subscriptions, licensing, or paid features.
Technical & Delivery Signals
The system is built using:
- GPT-5.6 and Luna subagents
- Codex CLI
- Tools like Git, GitHub, Playwright, Python, Node.js, SQLite, LaTeX, Markdown, JSON-RPC, YAML, TOML, CSS3, HTML5, JavaScript
- A package manager called Pixi
The author claims:
- No manual coding was involved.
- The system uses loops and automation via Codex and GPT-5.6.
- It supports multiple output formats (LaTeX, PDF, etc.)
Evidence
- Self-reported by the author.
- No technical architecture diagrams or documentation shared.
Traction & Maturity Signals
There is no evidence of traction, adoption, or user engagement beyond the developer’s own testing. The project was submitted to a hackathon and described as being larger than initially anticipated. It has not yet reached a production-ready state.
Evidence
- Not evidenced.
- No customers, usage metrics, or product maturity indicators.
Competitive Context
The author does not reference any competitors or existing solutions in the AI research space. The project is positioned as an alternative to chat-first tools, but no comparison with other platforms or tools is made.
Evidence
- Not evidenced.
- No competitive analysis or market positioning provided.
Key Risks & Red Flags
- No real-world usage: The tool appears to exist only in prototype form and lacks any evidence of actual use by others.
- Unverified claims: All functionality is self-reported without external validation.
- Lack of commercial clarity: No pricing, monetization, or business model described.
- Dependency on unproven AI agents: Reliance on GPT-5.6 and subagents implies potential instability or unreliability in execution.
- No team or structure: The team size is listed as zero, indicating no formal development team.
Evidence
- Self-reported by the author.
- No third-party confirmation or traction data.
Diligence Questions To Ask The Founders
- What specific research tasks have you used this tool for? Can you walk us through a concrete example?
- How does the system handle data privacy and security, especially when working with local files?
- Are there any known limitations or edge cases in how the different modes interact?
- Have you tested the tool across different operating systems beyond Ubuntu?
- What are your plans for scaling beyond the current prototype stage?
Investment/Partnership Verdict
At this stage, Science/Retrace is a self-reported hackathon prototype with no verified traction, revenue, or customer base. It shows potential in concept but lacks evidence of viability or market readiness.
Confidence Level Low
Next Steps
If the founder intends to build out the tool further, it would be worth revisiting once there's more concrete development, testing, and early user feedback. As a standalone project, it currently offers no clear commercial or investment opportunity.
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.
