The /dr-continue Command — Deprecated Alias for /dr-next
Why /dr-continue still works, what it actually does when invoked, and why all new work should use /dr-next instead.
/dr-continue is a deprecated alias. Invoking it runs the same logic as /dr-next — the command that resumes work on the current Datarim task from its last checkpoint. The alias exists to preserve operator muscle memory and older automation scripts while the command surface transitions.
Why aliases exist
A workflow tool accumulates users and scripts over time. When a command is renamed — usually because the name was imprecise or the new name better reflects what the command actually does — renaming it immediately breaks every existing reference. A deprecated alias keeps the old name functional through a defined transition window, giving existing usage time to migrate without forcing an urgent update.
In this case, /dr-continue suggested a direction ("keep going") rather than the mechanism ("resume from the last snapshot of this task"). /dr-next describes the actual behaviour: load the most recent stage snapshot, restore context, and continue from where the work stopped.
What happens when you invoke it
The alias applies the same task resolution and snapshot-first resume semantics defined by /dr-next. There is no difference in behaviour for the current Datarim 2.21.x line. The only difference is that /dr-continue carries a deprecation notice in its source file, signalling that it will be removed in a future release.
Removal is not before the next minor release after 2.21.x, and only after explicit operator approval.
What to use instead
All new instructions, CTA blocks, examples, and documentation should reference /dr-next. Existing automation that calls /dr-continue will continue to work through the transition window — there is no need for an emergency migration.
Read the what Datarim is post for context on how task resumption fits into the broader pipeline.