Over the past few weeks I’ve been working on a small tool called TermBoard.
It’s a terminal dashboard for running project tasks without having to remember how each project is set up.
One project uses uv, another uses poetry, another has a plain virtual environment, and before long I find myself checking the README just to remember how to run tests or start the application.
TermBoard tries to remove that friction.
It automatically detects the Python environment for the current project and runs tasks in the right environment. At the moment it supports:
- uv
- poetry
- pipenv
- standard .venv
Instead of opening multiple terminals, tasks run in the background and their logs appear in a scrollable panel inside the dashboard. That means I can keep an eye on several long running commands without filling my terminal history with thousands of log lines.
Configuration is done with a simple termboard.toml file, so adding project specific tasks is straightforward.
The project is built with the Textual framework, which made it possible to build a terminal interface that still feels responsive while multiple tasks are running.
If you’re happy with make, just, or shell scripts, those tools are great. TermBoard isn’t trying to replace them. It’s more about giving those tasks a persistent interface where you can start, stop, monitor, and inspect them from one place.
If you’d like to try it:
uv tool install termboard
# or
pipx install termboard
GitHub: https://github.com/HeyShinde/TermBoard
Documentation: https://heyshinde.github.io/TermBoard/
The project is still evolving, so I’d genuinely appreciate feedback. If there’s something that would make your own workflow easier, I’d love to hear about it.
Top comments (0)