Hello everyone, I want to share my experience over the past six months building an open-source web application system (with the help of Cloud Code and Codex). The system is real, not just a UI; everything you see here was built as an application on top of the system and is not part of it. Plus, it continues to work even if you close the browser (unlike Puter, for example).
source
https://github.com/PhreshOS/system
demo (around 5 people at a time, if it's full there's a timer)
docs
how can I benefit from it? I build all my own tools on top of it, thus benefiting from remote access, a single authentication system, and communication. All I write is the business logic and how the interface will look. Any AI agent can access and use this application without me having to build a custom interface for it.
Top comments (2)
The "keeps working after the browser closes" part is the distinction I'd want to see demonstrated. If an app starts a long-running job, then the tab closes and reconnects, does it reattach to the same job ID and stored output? A short demo showing that path, plus what happens when authentication expires mid-job, would clarify the execution lifecycle more than another desktop screenshot. I haven't run the demo, so this is a question about the contract rather than a claim about its behavior.
Creating a video explaining the concept is part of the plan, but here's a brief overview:
Every application consists of two parts: a server and a client, connected by a two-way communication channel.
The idea is that the state remains on the server side of the application, while the browser interface only displays that state. There are other solutions for simpler uses.
Generally, this documentation covers everything. If you give it to GROK AI along with your use case, it will tell you if it will help you.
phreshos.com/docs
Here's a general explanatory video:
phreshos.com/media/phreshos-deskto...