OpenAI 2026 hackathon

Osmosis

Turn your AI agent's working time into your learning 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,770 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

What the company appears to be

Osmosis is a learning companion tool designed to help non-programmers understand the technical concepts behind AI-assisted coding projects. The product runs alongside an AI agent (such as Codex) during project development, delivering contextual lessons and quizzes while the agent works.

What changed

The author describes a shift in their own experience with AI-assisted coding — moving from "shipping more and understanding less" to a model where the time spent waiting for AI agents can be turned into learning time. This is framed as an evolution of how people interact with AI tools, especially in developer education or onboarding contexts.

Single most important open question

Is there evidence that non-programmers are actively using this tool, or that they would pay for it? The description does not indicate any user base, revenue, or adoption beyond the author’s own use case.

Back to contents

What The Product Actually Is

The description states:

  • Osmosis is a learning companion that runs beside a coding agent (e.g., Codex).
  • It maps projects into a knowledge tree and delivers plain-language explanations with quizzes.
  • It uses a 3D visualization layer to explain technical concepts like Three.js → WebGL → scenes, cameras, meshes, lighting.
  • It includes a skill tree that tracks mastery and avoids re-presentation of known topics.
  • It is built using Node.js MCP server + SSE + a single-file web UI; GPT-5.6 generates knowledge trees and lesson cards at runtime.

Inference The product appears to be an experimental educational tool, likely built for a hackathon or prototype phase. It integrates AI-generated content with interactive UI elements to support learning during coding tasks.

Back to contents

Positioning & Claim Evolution

The description states:

  • The author is a product manager who "can't really read code" and has shipped 60+ projects using vibe coding.
  • The tool aims to address the gap between shipping code and understanding what was built.
  • It repositions idle time during AI agent use into learning time, inspired by video game loading screens.

Inference The positioning is that of a developer education companion, aimed at non-programmers or those new to coding who are using AI tools to build projects. The claim evolution suggests moving from "AI as a productivity tool" to "AI as a learning enabler."

Back to contents

Target Customer & ICP

The description states:

  • The author is a product manager who "can't really read code."
  • The tool is designed for non-programmers or those unfamiliar with technical concepts.
  • It aims to help users "ship the project and keep the knowledge."

Inference The target customer is likely non-technical professionals or beginners using AI coding tools (e.g., Codex, GitHub Copilot) to build software but who lack deep technical understanding.

Not evidenced No evidence of actual customers, personas, or segmentation beyond the author’s own experience.

Back to contents

Business Model & Pricing Evidence

The description states:

  • No pricing information is provided.
  • The tool is described as a prototype built for a hackathon.
  • There are no mentions of monetization, subscriptions, or sales channels.

Inference There is no evidence of a business model or pricing structure. It appears to be an experimental project with no commercial traction.

Back to contents

Technical & Delivery Signals

The description states:

  • Built end-to-end with Codex (GPT-5.6) in a single session.
  • Node.js MCP server + SSE + a single-file web UI.
  • GPT-5.6 generates the knowledge tree and every lesson card at runtime.
  • The project was submitted to the OpenAI 2026 hackathon.

Inference The technical stack is minimal and experimental, built for rapid prototyping. It uses AI to generate content dynamically and integrates with a coding agent via an MCP interface.

Back to contents

Traction & Maturity Signals

The description states:

  • The project was submitted to a hackathon (OpenAI 2026).
  • The author has shipped 60+ projects using vibe coding.
  • No mention of users, customers, or adoption beyond the author’s experience.

Inference There is no evidence of traction or user adoption. The tool appears to be in a prototype or early-stage development phase.

Back to contents

Competitive Context

The description states:

  • The tool is inspired by video game loading screens and Duolingo-style learning.
  • It aims to improve the learning experience during AI-assisted coding.
  • No mention of existing competitors or market analysis.

Inference There is no evidence of a competitive landscape. The product appears to be novel in its approach but lacks any indication of similar tools or market positioning.

Back to contents

Key Risks & Red Flags

The description states:

  • It is a hackathon project with no commercial traction.
  • No revenue, customers, or monetization strategy are mentioned.
  • The tool is built for one specific AI agent (Codex) and may not scale beyond that.

Inference Key risks include lack of commercial viability, unclear user demand, and limited scalability due to its experimental nature and narrow integration scope.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the actual user base for this tool? Are there any users beyond the author?
  2. How does the tool plan to monetize or scale beyond a hackathon prototype?
  3. Is there a specific market or persona that you are targeting, and how did you identify them?
  4. What are the technical limitations of using GPT-5.6 for generating content in real time?
  5. Are there plans to support other AI agents beyond Codex?

Back to contents

Investment/Partnership Verdict

The description states:

  • The project is a hackathon submission with no commercial traction or revenue data.
  • It is built by two people and appears to be experimental.

Inference There is no evidence of a viable business model, user base, or market demand. The tool is in an early prototype phase and lacks any indication of commercial readiness or scalability.

Verdict Not evidenced as a viable investment or partnership opportunity at this stage.

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.