gibsonhu/rosmon2

``json { "i": 0, "repo": "GibsonHu/rosmon2", "stars": 5, "lang": "Python", "ok": true, "char_count": 1847, "text": "rosmon2 is a tool for launching and monitoring robotics software built with ROS 2, a framework for writing robot programs. It runs existing launch files written in Python, XML, or YAML without changes, preserving their arguments and structure. The project is inspired by an older ROS 1 tool called rosmon but is built independently for ROS 2 and does not require ROS 1 to be installed.\n\nAfter building it inside a ROS 2 workspace, you start it with a simple command pointing to a launch file. You can pass standard ROS 2 arguments like namespace assignments directly on the command line. The tool provides a terminal interface that shows every running process and its current state in a status bar. You select a process by pressing its assigned key, then use short keyboard commands to start it, stop it, mute its output, or even restart it under a debugger. Global keys let you start or stop all processes at once, filter for warnings, search for nodes by name, and shut everything down gracefully.\n\nA namespace mode groups processes by their ROS namespace and shows live counts of alive versus dead processes, with color coding: green when all are alive, yellow when some are dead, and red when none are running. You can act on an entire namespace at once, or drill into it to control individual processes.\n\nBeyond the terminal interface, rosmon2 exposes a session-based API. Each launch creates a private Unix socket that other terminals, scripts, or coding agents can connect to. Commands like status, logs, restart, and wait return structured JSON, making it possible to automate supervision from another program. A streaming JSON events mode outputs one machine-readable event per line, covering process starts, exits, control actions, and log records.\n\nThe project also includes an MCP server, which lets AI coding assistants like Codex inspect and control a running session through a standardized protocol. The same supervisor backs the terminal interface, the JSON command-line tools, and the MCP server, so all three control the same set of processes. The full README is longer than what was shown.", "error": null } ``