The file is open now. Build on it.
kinogaki
kinogaki is built on Prism, a structured format for the data real work is made of: documents, scenes, assets, graphs. The whole file is a typed model your programs and agents read and change directly, not a blob one app keeps to itself. Build on it in C++ or Python. The same interface draws on the desktop and in the browser.
Your work sits inside one app, in a format only that app fully reads. To everything else it is a blob. An agent can touch the surface but not the structure, and exporting it loses whatever the next format has no slot for. Prism turns the file into a typed model, addressable to the smallest value, so any tool or agent reads it in full and changes it precisely. The work is yours, not the app's.
Use the file, or build the whole application on it. Reach Prism in a few lines of C++ or Python, or build the entire app on it: one codebase that runs as a native app on the desktop and in any browser. The app's state is a Prism file behind a typed server, so an AI agent edits it through the same operations a person does, with no extra work. Realms are next: sign in, and every user works in their own tree of one shared system.
Libraries
Open C++ you build on: the document model, the widget toolkit, and the runtime beneath them. Each rests on the one below.
01 · C++ Library
The document model: pure and dependency-free. Path-addressed elements, typed values, an evaluator, native serialization, and a C ABI. Embed it anywhere.
Read docs →02 · C++ Library
A GPU-drawn, retained-mode widget toolkit. The same widgets draw natively on the desktop (Metal) and in the browser as WebAssembly (WebGL2). Author an interface once, run it either way.
Read docs →03 · C++ Library
The runtime layer: OS windowing and input, a Metal render hardware interface, the message and command buses an app edits through, and the transport that pushes a UI over a socket.
Read docs →Software
One document model, reached three ways: in scripts, by agents, and by hand.
01 · Software
The command line: validate documents, convert between formats through Prism, and pack a whole directory tree into a single file.
Read docs →02 · Software
A bridge that lets external tools, including MCP clients like Claude Code, operate on Prism files through stable, typed operations, instead of raw text or fragile binary parsing.
Read docs →03 · Software
A native editor with the server embedded: open a document, connect an agent, and watch its edits land live alongside your own.
Read docs →Examples
Complete applications, and the fullest worked examples of the stack, readable end to end.
01 · Software
A 2-D application for generative geometry and spectral light-tracing: design with nodes, animate any property, and render real light.
Read docs →02 · Software
A focused, fast pixel-art editor: built for making sprites and tiles without the bloat.
Read docs →03 · Software
A novel-writing app where the manuscript (spine, prose, characters, and their links) is one structured file a writer and an AI agent edit together.
Read docs →Next: Realms — one system across users and machines. Sign in, and your work lives at kino://you@realm/path — one address that reaches from the network down to a single value in a file. Machines sync store-and-forward, so laptops sleep and shares wait. A grant shares a subtree with a person; an echo shares it with a team; and every document in a hosted realm has a URL. Read the design →
The file is open now. Build on it.