ROS Index
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
 |
 |
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged dendros at Robotics Stack Exchange
Package Summary
| Version | 1.0.0 |
| License | MIT |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/mlisi1/DendROS.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-07-14 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Michele Lisi
Authors
- Michele Lisi
Color-coded ROS 2 output — because a wall of white text from 32 nodes is nobody's debugging tool.
You launched your stack. Nav2, SLAM, hardware drivers, your own nodes — all printing to the same terminal, all the same color. By the time you find the line you were looking for, it has scrolled past.
Vanilla ros2 launch
|
With DendROS |
|---|---|
|
|
DendROS assigns each group of nodes its own color. You could have localization in blue, navigation in green, hardware in orange — defined once in a small YAML file that lives inside your package. No launch file edits. No new ROS 2 dependencies. Packages without a config pass through completely unchanged. It also features some quality of life improvements for ROS outputs.
Features
-
Color by group
One config file per package maps node groups to colors, badges, and display rules
-
All main
ros2CLI commands wrappedros2 node list,ros2 node info,ros2 service list,ros2 action list,ros2 topic list,ros2 param list, andros2 param describe— all colorized with the same group colors and badges, no extra config required. → Full feature list -
One command to get started
Too lazy to look up how DendROS config works? We got you covered:
dendros initscans your launch files and generates an initial config for you
-
Crash alert
An inline banner flags crashed nodes the moment they die, lists the exit code, and repeats periodically so you don’t miss it in fast-scrolling output
-
Traceback highlighting
Python tracebacks are colored automatically: bold red for the header and exception line, dim red for the frames; configurable per session
-
Keyword highlighting
Mark specific words or patterns in bold or in a custom color — per group, or package-wide.
-
Parameter change alert
When a node’s parameter changes at runtime — via
ros2 param setor any parameter service client — an inline notification appears in the launch terminal showing the node, parameter name, and old→new value. Two styles: compact inline and a full-width inverted block that’s hard to miss in busy logs.
File truncated at 100 lines see the full file