A terminal spreadsheet with full xlsx compatibility is not the kind of tool that usually gains traction, but tuisheet has found a niche among developers who want spreadsheet functionality without leaving the command line.
The project, written in Go, draws its interface inspiration from VisiCalc and Lotus 1-2-3, the programs that defined spreadsheets before graphical interfaces took over. It reads and writes OpenXML files, the standard format used by Excel and LibreOffice, so documents created in tuisheet open in mainstream applications without conversion.
Go was a deliberate choice. The language produces a single static binary with no runtime dependencies, uses little memory, and cross-compiles cleanly to Linux, Windows, Solaris, AIX, and BSD. For a tool meant to run on any terminal a developer might encounter, those properties matter more than language ergonomics.
How it was built
The developer describes tuisheet as mostly vibe coded. The project started with questions on LLM web sites, moved to Codex with ChatGPT for a short period after seeing an advertisement, and settled on OpenCode as the primary development tool. When free token allowances ran out on one model, the developer switched to another: DeepSeek free, then 0x Alpha, then Muse Spark Free.
The result is a functional spreadsheet that the developer says has completely replaced LibreOffice and Excel for daily work. That is a strong claim for a terminal application, but the combination of keyboard-driven navigation, mouse support, and xlsx compatibility covers the core workflow that most spreadsheet users need.
Interface and navigation
The interface is keyboard-first. F1 opens help. The slash key brings up a menu, and you navigate by pressing the capital letter of each option or using arrow keys. Opening a file is the sequence slash, F, R. Quitting is slash, Q. The menu system is discoverable without memorization, which matters for a tool that aims to be usable, not just impressive.
Mouse support works for clicking cells, and right-click menus are available on cells, rows, columns, and the sheet tabs bar. The dual input model makes the tool accessible to people who are comfortable with both keyboard shortcuts and point-and-click interaction.
The developer notes that testing and daily use have been far more thorough on Linux than on other platforms. Cross-compilation ensures the binary runs elsewhere, but the polish is concentrated on Linux terminals.
Why a terminal spreadsheet matters
Spreadsheets are one of the oldest software categories, and they are also one of the most deeply tied to graphical interfaces. Most spreadsheet work happens in a browser tab or a desktop application, which means it requires a GUI environment. That is fine until it is not. Developers working over SSH, writing scripts that generate or parse spreadsheets, or working on headless servers do not have a GUI available.
A terminal spreadsheet fills that gap. It lets you view, edit, and create xlsx files in environments where LibreOffice or Excel cannot run. The xlsx compatibility is the key differentiator from other terminal tools. CSV works for simple data, but spreadsheets with formatting, formulas, and multiple sheets need a real format. tuisheet provides that.
The VisiCalc and Lotus 1-2-3 influence is visible in the interface design. Those programs were built for terminals and keyboard-only interaction. Modern spreadsheets added ribbons, toolbars, and mouse-driven formatting that increased visual complexity without always improving the core spreadsheet experience. tuisheet strips that back to the fundamentals: navigate, enter data, format cells, manage sheets.
The AI-assisted development angle
What makes the project noteworthy beyond its functionality is how it was built. The developer is upfront about using LLMs as a coding partner throughout the process, switching models as free tiers expired. The project did not depend on a single AI provider or a paid subscription. It was assembled from whatever was available at the time.
That approach produced a stable, fast application that replaced commercial software for real work. It is a data point, not a methodology, but it suggests that the bar for useful tools built with AI assistance is lower than many developers assume. The constraint is not the AI. It is knowing what to build and whether it works when you are done.
The developer offers a characteristically honest disclaimer about xlsx compatibility: the software is provided as is, without warranty. That is standard for open source projects, but it is worth noting for anyone planning to use tuisheet as part of a data pipeline or workflow that depends on perfect xlsx round-tripping.