# \[ANN\] Tachikoma.jl — A terminal UI framework for Julia

**URL:** https://discourse.julialang.org/t/ann-tachikoma-jl-a-terminal-ui-framework-for-julia/135878
**Category:** Package Announcements
**Tags:** announcement, terminal, tooling
**Created:** [February 27, 2026, 3:37am UTC](https://discourse.julialang.org/t/ann-tachikoma-jl-a-terminal-ui-framework-for-julia/135878 "2026-02-27T03:37:39Z")
**Posts on this page:** 1
**Showing post:** 80

<div class="post-metadata">

### Author: ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)
#### Post date: [March 16, 2026, 6:49pm UTC](https://discourse.julialang.org/t/ann-tachikoma-jl-a-terminal-ui-framework-for-julia/135878/80 "2026-03-16T18:49:16Z")

</div>

> [@Mikhail\_Kagalenko](#):
>
> That’s the sort of attitude that, among other things, strongly motivates me to avoid  
> having anything to do with LLM-coded software.

It’s also _very_ borderline with respect to [the requirements for registered packages](https://github.com/JuliaRegistries/General?tab=readme-ov-file#is-there-any-policy-regarding-the-use-of-llms-in-registered-packages)! There’s a very fine line here between AI-_assisted_ coding and code deployed by LLMs without human intervention, aka vibe-coding, which is NOT acceptable for registered packages.

While it’s great that you’re creating this framework, I would urge you to curb your AI enthusiasm just a little bit, and remember that the fundamental design, the quality, and reliability of your package are still your responsibility, and not something you can delegate to an LLM. Moving fast and _breaking things_ is not something that leads to a healthy ecosystem

---

_[View the full topic](https://discourse.julialang.org/t/ann-tachikoma-jl-a-terminal-ui-framework-for-julia/135878)._