Capture
Save supported browser organization, VS Code workspace/editor context, selected folder/terminal context and service expectations into a durable project checkpoint.
WINDOWS PRIVATE BETA · LOCAL-FIRST
Hibernate your dev workspace.
Come back ready.
Project Hibernate safely puts away supported VS Code, Chrome and development-service context, then reconstructs it later with verification instead of guessing what came back.
✓ Review before close
✓ Verified restore
✓ Local workspace data
Unsigned private beta for Windows 10/11. No installer or auto-updater yet.
Active workspace
Ready to capture
01
Connect & assignVS Code + Chrome windows belong to a project.
02
Capture checkpointSave reconstructable state before anything closes.
03
Review & hibernateFresh preflight checks every selected target.
04
Restore & verifyObserved evidence decides whether the project is ready.
Project readinessVERIFIED READY
VS Code cold restoreChrome profile cold restoreApproved Node/Python servicesEncrypted checkpointsPrivacy-safe diagnostics
THE LOOP
Not “reopen some apps.”
Reconstruct a workspace with evidence.
Hibernate separates capture, destructive action and restore into explicit steps. Unsupported or ambiguous targets stay open instead of being guessed.
Review
See what can actually be reconstructed. Dirty work, unsupported states and ambiguous native ownership block automatic close.
Hibernate
Only reviewed, freshly rechecked targets are closed. A failed or unverified close stops later destructive actions.
Resume
Cold-launch the saved Chrome profile and VS Code workspace, restart approved services, then verify each selected capability before reporting ready.
VALIDATED, NOT HAND-WAVED
The packaged lifecycle has passed end to end.
In the current validated flow, one checkpoint closed VS Code, Chrome and a reviewed service, Project Hibernate itself restarted, then the saved workspace was cold-restored and overall readiness returned to ready.
- 57
- Rust unit tests
- 25
- TypeScript tests
- 1
- real service lifecycle integration
- 100%
- final package hash verification
Actual Windows reboot recovery is intentionally not claimed yet.
GPT-6 ASTRA
BUILT WITH GPT-6 ASTRA
Astra helped with the parts where guessing would be dangerous.
Astra worked alongside the project on Windows process/window ownership, durable native-close verification, cold-start recovery, service lifecycle design, safety boundaries and end-to-end validation.
Example: shared-process VS Code windows
Two VS Code workbenches can share one GUI process. Astra investigated the native HWND/process topology and found no trustworthy supported primitive that mapped the exact integration instance to the exact workbench window. Project Hibernate therefore blocks automatic close in that ambiguous case rather than relying on titles, focus state or timing guesses.
PRIVATE BETA SCOPE
Useful now. Deliberately honest about the edges.
VS Code
Saved local workspace/editor context, reviewed native close when unambiguous, and cold restore back to the same integration identity.
Chrome
Profile-bound capture and cold restore with tab/group verification. Quick Sleep can discard eligible background tabs separately.
Dev services
Explicitly reviewed direct Node/Python service definitions with verified ownership, graceful stop and checkpoint-driven restart.
Explorer + terminals
Folders and verified instrumented prompt working directories are restored as context. Arbitrary terminal history, panes and commands are never replayed.
CURRENT LIMITS
Fail closed beats pretending.
- Windows only for this beta.
- Actual Windows reboot recovery has not yet been validated.
- Multiple VS Code workbench windows sharing one GUI process block automatic close.
- Explorer and arbitrary Windows Terminal windows are Context Restore, not automatic Hibernate.
- The build is unsigned and uses a portable setup helper rather than a polished installer.
PROJECT HIBERNATE 0.1.0 · PRIVATE BETA
Close the workspace.
Not the context.
Try the Windows beta and tell me which developer environments Hibernate should learn next.