Show HN: OpenAI Apps Handbook

Show HN (score: 5)
Found: October 28, 2025
ID: 2153

Description

API/SDK
Show HN: OpenAI Apps Handbook I went swimming in the ocean of OpenAI's Apps SDK… and came back with a handbook!

Over the past few weeks, I’ve been diving deep into the ChatGPT App SDK: exploring its APIs, tools, and hidden gems. Along the way, I built, broke, fixed, and reimagined a bunch of little experiments.

P.S: Indeed OAIs official docs is the source of truth, this is just a rough notebook

Maybe, I can create a CLI tool to scaffold app?

More from Show

Show HN: Identifiy test coverage gaps in your Go projects

Show HN: Identifiy test coverage gaps in your Go projects

Show HN: Swatchify – CLI to get a color palette from an image

Show HN: Swatchify – CLI to get a color palette from an image A fast, cross-platform CLI tool that extracts dominant colors from images using k-means clustering.

Show HN: Wozz – Agentless Kubernetes cost auditor (open source)

Show HN: Wozz – Agentless Kubernetes cost auditor (open source)

Show HN: Zephyr3D – TypeScript WebGPU/WebGL 3D engine with an in‑browser editor

Show HN: Zephyr3D – TypeScript WebGPU/WebGL 3D engine with an in‑browser editor Hi HN,<p>I’ve been working on Zephyr3D, an open-source 3D rendering engine for the modern web, plus a visual editor that runs entirely in the browser.<p>- Written in TypeScript - Supports WebGL&#x2F;WebGL2&#x2F;WebGPU - Comes with a visual editor that runs in the browser (no installation required)<p>With the recent updates, a few things might be interesting to people here:<p>Engine &amp; rendering ------------------<p>- WebGL&#x2F;WebGPU abstraction with a TypeScript API - PBR rendering - Cluster lighting &amp; Shadow Maps - Clipmap-based terrain for large landscapes - Sky Atmosphere &amp; Height-based fog - FFT water system - Temporal anti-aliasing (TAA) - Screen-space motion blur<p>The goal is to make it possible to build reasonably complex 3D experiences that run directly in the browser, without native dependencies.<p>In-browser editor -----------------<p>The editor is a web app built on top of the engine and runs completely in the browser. It currently supports:<p>- Project management - Scene editing - Node-based material blueprints - Animation editing - Script binding and a scheduling system - Prefabs for reusing entities across scenes - Preview and one-click publishing to the web<p>All project data is handled via a virtual file system (VFS) that can plug into different backends (in-memory, IndexedDB, HTTP, ZIP, DataTransfer, etc.), so saving&#x2F;loading works entirely on the client side.<p>Links -----<p>Homepage: <a href="https:&#x2F;&#x2F;zephyr3d.org" rel="nofollow">https:&#x2F;&#x2F;zephyr3d.org</a> Editor (runs in the browser): <a href="https:&#x2F;&#x2F;zephyr3d.org&#x2F;editor&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zephyr3d.org&#x2F;editor&#x2F;</a> GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;gavinyork&#x2F;zephyr3d" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;gavinyork&#x2F;zephyr3d</a><p>I&#x27;d love feedback on:<p>- How the in-browser editor workflow feels (performance, UX, what’s missing) - Whether the VFS approach for project data makes sense for real projects - Any red flags you see in the engine architecture or WebGPU&#x2F;WebGL abstraction - What would be deal-breakers or must-have features for using this in games, data viz, or other interactive web experiences<p>I’ll be around to answer questions and can go into more detail about the rendering pipeline, the editor internals, or anything else you’re curious about.

No other tools from this source yet.