Browse pre-built Routines from Hamster. Enable one for your workspace, or fork it and make it your own.
Writing a Routine from scratch means learning what triggers are available, drafting instructions, running test iterations, and checking the output before you trust it in production. That is the right investment when you need something specific — but it is a lot to ask of a team that just wants to see whether automating a recurring task is even worth it.
The Routines Library removes that friction. It gives your team pre-built Routines — authored and maintained by Hamster — that you can enable for your workspace with a single toggle. Your team can read exactly what each one does before deciding whether to adopt it as-is or fork it into something tailored to your process.
Select Methods in your workspace sidebar to open the Library, then select the Routines tab. Your own Routines live under Routines in the same header, with a Runs tab for run history.
Each library Routine row shows:
Select a row to open the routine and read its instructions and triggers.
Toggle a library Routine on to make it active for your workspace. Some library Routines start enabled; the Active switch shows the current state for your workspace.
Toggle it off to disable it for your workspace without removing it from the Library. It stays available; you can re-enable it at any time.
Library Routines that are enabled for your workspace and that you haven't forked also appear in your Routines list with a from Library label so you can tell them apart from your own automations.
When you want to customise a library Routine, select Fork on its row. The dialog lets you rename the routine and adjust its triggers; select Save as my copy to create the fork.
Forking creates an account-owned copy in your Routines list that you fully control — you can edit the instructions, adjust the triggers, rename it, or remove it. Your fork is independent: changes Hamster makes to the library original do not affect your copy.
After forking, the library version is disabled for your workspace and its row reads Forked — your fork takes its place. You can re-enable the library version at any time if you want both enabled.
Your fork carries a from Library badge that links back to the original.
Library Methods can bundle library Routines, but enabling a library Method doesn't enable its Routines; each keeps its own switch in the Routines tab. Saving your own copy of the Method forks its Routines into your Routines list and disables the library versions; see Enabling Versus Saving a Copy.
Hamster maintains the content of each library Routine. When the instructions or trigger configuration of a library entry improves, the library version in your workspace reflects it — you get the improvement without doing anything.
If you have forked a library Routine, your copy does not update automatically, because it is your content to control. When the library source changes, an Update available indicator appears next to your fork in the Routines list, and the from Library badge in the routine reads Library updated.
You have two options:
You can fork again after a reset.