Launched this week
Monospace
ASCII & Box-Drawing Diagram Editor (Rust)
2 followers
ASCII & Box-Drawing Diagram Editor (Rust)
2 followers
Draw ASCII and box-drawing diagrams in your terminal. A Rust editor and CLI for plain-text flowcharts and architecture sketches that diff in git.
Free
Launch Team
Render Sandboxes: a computer for every agentGive every agent its own machine. Starts in under a second
Promoted
Hey Product Hunt! 👋
I’m Andrés, the maker of Monospace — an open-source Rust toolkit, CLI, and interactive terminal editor (TUI) for drawing plain-text ASCII and Unicode box-drawing diagrams.
Why I built it:
Diagrams belong where engineers read and write: inside source files, commit messages, pull request descriptions, and Markdown docs. Binary image files and proprietary canvas formats don’t diff cleanly in git diff and require leaving the terminal. On the other hand, drawing and maintaining ASCII boxes and arrows by hand is tedious as soon as a label changes or a box moves.
What Monospace does today (v0.1.1):
Interactive TUI Editor (monospace): Draw boxes, edit labels in place, resize shapes, and navigate menus with mouse or keyboard shortcuts — with full undo/redo command history.
Self-routing orthogonal connectors: Connect shapes and let connectors automatically route around obstacles and recalculate junctions live as shapes move.
9 built-in glyph sets: Render the same diagram using pure ASCII fallbacks or light, heavy, and double Unicode box-drawing characters, with true junction composition at shared cells.
Non-interactive CLI (monospace-cli) & portable core: Render JSON diagram descriptions directly in scripts, docs pipelines, or CI. The core domain engine is strictly isolated from terminal I/O and compiles cleanly to WebAssembly.
Built one honest commit at a time:
Monospace is in an early stage and is developed strictly via Spec-Driven Development: every slice starts with an issue and an agreed specification before any code is written.
You can grab precompiled binaries for Windows, macOS, and Linux on the website, or install via Cargo with cargo install monospace.
I’d love your honest feedback: What’s the biggest friction you hit when creating or maintaining architecture and sequence diagrams in your repos, and what would you love to see next in Monospace?