Remember
Paste a dormant GitHub app; get it back running in a sandbox, or an honest refusal when it can’t be made safe.
- Context
- Daytona HackSprint Singapore, team project
- My part
- Much of the build, with Kendrick: the run workspace, the live Daytona flow and more
- Stack
- Next.js, TypeScript, Daytona, OpenAI, Nosana
- Year
- 2026
- What it is
- A repository resurrection service. It clones a public repo into an isolated Daytona sandbox, keeps a pristine seed, checks whether it runs, and if not races three repair candidates forked from that seed. OpenAI plans the repairs as structured actions; verification, not the model, picks the winner.
- What I did
- I worked across the product with Kendrick. I built the workspace people watch the run in (repository submission, sandbox provisioning, the repair race and preview dialogs) and wired it to the live Daytona flow, with tests on the provider and server config. More of my work went in from his laptop, so the commit history undercounts it.
- Result
- A preview is published only after verification passes. Failed runs keep their evidence and publish nothing, losing candidates are cleaned up, and credentials never leave the server.
