diff --git a/docs/changelog.txt b/docs/changelog.txt
index 3748134c1..a55473335 100644
--- a/docs/changelog.txt
+++ b/docs/changelog.txt
@@ -44,6 +44,7 @@ changelog.txt uses a syntax similar to RST, with a few special sequences:
 - `tiletypes`: no longer resets dig priority to the default when updating other properties of a tile
 - `automaterial`: fix rendering errors with box boundary markers
 - `autolabor` & `autohauler`: properly handle jobs 241, 242, and 243
+- `autolabor` & `autohauler`: refactored to use DFHack's messaging system for info/debug/trace messages
 - `autofarm`: add missing output flushes
 - `hotkeys`: correctly detect hotkeys bound to number keys, F11, or F12
 - `labormanager`: fix quern construction labor
diff --git a/docs/plugins/autohauler.rst b/docs/plugins/autohauler.rst
index 08c84327a..09c3c2f8f 100644
--- a/docs/plugins/autohauler.rst
+++ b/docs/plugins/autohauler.rst
@@ -22,6 +22,9 @@ Autohauler allows a skill to be used as a flag to exempt a dwarf from
 autohauler's effects. By default, this is the unused ALCHEMIST labor, but it
 can be changed by the user.
 
+Autohauler uses DFHack's `debug` functionality to display information about the changes it makes. The amount of
+information displayed can be controlled through appropriate use of the ``debugfilter`` command.
+
 Usage
 -----
 
@@ -42,8 +45,6 @@ Usage
     Show the active configuration for all labors.
 ``autohauler frameskip <number>``
     Set the number of frames between runs of autohauler.
-``autohauler debug``
-    In the next cycle, output the state of every dwarf.
 
 Examples
 --------
diff --git a/docs/plugins/autolabor.rst b/docs/plugins/autolabor.rst
index 63b830dfe..4b92e5fd8 100644
--- a/docs/plugins/autolabor.rst
+++ b/docs/plugins/autolabor.rst
@@ -56,6 +56,9 @@ labor, then to additional dwarfs that meet any of these conditions:
 
 We stop assigning dwarves when we reach the maximum allowed.
 
+Autolabor uses DFHack's `debug` functionality to display information about the changes it makes. The amount of
+information displayed can be controlled through appropriate use of the ``debugfilter`` command.
+
 Examples
 --------