Skip to content

About

Resurrect your hyprland session after rebooting

Resources

Stars

2 stars

Watchers

1 watching

Forks

Latest commit

 

History

40 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

hyprresurrect

hyprresurrect saves your currently open applications in Hyprland and restores them on reboot (or at any point). Workspaces, groups, tile sizes, layout are all preserved.

Why?

I started using hyprland. I wanted a way to restore my tiles and layout. I tried a few existing tools but wasn't happy, some would dump everything onto one workspace, or not care about multiple monitors, etc. So the natural course of action was to build my own :)

If you're reading this then this is still WIP! But mostly done. Just need the daemon, ✅group support, ✅persisting tile size/layout, ✅terminal contents

Installation

AUR

not yet! sorry!

Go

Requires Go 1.27+

go install github.com/FillipdotS/hyprresurrect@latest

Usage

hyprresurrect save              # snapshot the current windows/layout
hyprresurrect restore           # restore the most recent snapshot
hyprresurrect restore --dry-run # prints the restore plan without actually executing it 
hyprresurrect version           # prints the installed version

Terminal contents

Ghostty windows reopen in the directory they were in, through ghostty's own +new-window. What was running in them is recorded and listed by restore --dry-run, but never started again:

$ hyprresurrect restore --dry-run
...
-- these were running, and are not started again:
   workspace 2: btop
   workspace 3: herdr

With a single instance, every window shares one process, so each window is paired with its shell by creation order. If that instance has any tabs or splits the pairing is ambiguous, so its windows still come back on the right workspaces but open in the default directory. Windows started with ghostty -e <cmd> are relaunched with their original command.

Contributing

Feel free to contribute anything and everything! Just make sure it's tested and makes sense for this tool. Preferably make an issue beforehand so there's alignment.

Testing

Regular unit tests can be run via go test

E2E Tests

These require you to be running hyprland. They spawn a nested hyprland session that uses the real go build binary to run commands and checks via hyprctl clients -j if we got the intended results

HR_E2E=1 go test ./internal/e2e/

The nested session shows the name of the running test. To actually watch one go by, slow every step down:

HR_E2E=1 HR_E2E_SLOW=500ms go test ./internal/e2e/ -run TestRoundTrip

Todo (Roughly in order)

  • ✅ E2E testing hyprland via a nested session

  • ⬜ Autosave daemon

  • ⬜ Auto restore on reboot

  • ✅ Groups. Membership, tab order and the raised tab all round trip

  • ✅ Terminal contents. i.e. "btop" or "herdr"

  • ✅ Remember tile sizes and layout.

  • ⬜ Named workspaces. Only numeric workspace ids are captured. Not sure this is needed

  • ⬜ Flatpak support.

About

Resurrect your hyprland session after rebooting

Resources

Stars

2 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages