HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
unconed
TermKit
JavaScript2011–2026
unconed / TermKit

TermKit

Experimental Terminal platform built on WebKit + node.js. Currently only for Mac and Windows, though the prototype works 90% in any WebKit browser.

29Distinct people
31Mentions
0Explicit recommenders
4.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Experimental Terminal platform built on WebKit + node.js. Currently only for Mac and Windows, though the prototype works 90% in any WebKit browser.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year31 dated mentions

Observed mentions: 2011-05-12 19:57:39 UTC to 2026-02-14 12:27:22 UTC.

02462011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC615
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC615
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC606
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC404
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
TermKit Goal: next gen terminal / command application Built out of WebKit and Node.js. Runs as a desktop app on Mac, Windows and Linux, and can be hacked into any WebKit browser (Chrome, Safari). Follow TermKit on Twitter for the latest news and updates. For the background and architecture, please read and comment on: http://acko.net/blog/on-termkit Warning: Alpha version, still under development. Nothing works yet. Some cool features Smart token-based input with inline autocomplete and automatic escaping Rich output for common tasks and formats, using MIME types + sniffing Asynchronous views for background / parallel tasks Full separation between front/back-end TermKit is not a... ...Web application. It runs as a regular desktop app. ...Scripting language like PowerShell or bash. It focuses on executing commands only. ...Full terminal emulator. It does not aim to e.g. host 'vim'. ...Reimplementation of the Unix toolchain. It replaces and/or enhances built-in commands and wraps external tools. (but you could make it do most of those things with plug-ins) How to use: Detailed instructions are available from these sources: Mac OS X (OS X Daily) Windows (Redpoint blog) Linux, Python GTK Linux, Chrome only (Easytech blog) Unfortunately, TermKit currently requires some assembly. Install the Mac development tools (Xcode and friends). Install node.js. If not covered in #2, install npm: curl http://npmjs.org/install.sh | sh Install node-mime: npm install mime Clone the TermKit repository: git clone https://github.com/unconed/TermKit.git --recursive Users of older git versions will need to type: git submodule update --init Run the NodeKit daemon: cd TermKit/Node; node nodekit.js Mac: Unzip and run the Mac app in Build/TermKit.zip Linux: See Linux/Readme.txt Tip: Press ⌥⌘C to access the WebKit console. API Preliminary instructions on how to write TermKit native commands can be found here: https://github.com/unconed/TermKit/blob/master/Node-API.md Credits TermKit by Steven Wittens (@unconed). Windows port by James Rhodes (@hachque). Linux Python/GTK wrapper by Lucas S. Magalhães. Includes: “NSImage+QuickLook” by Matt Gemmell (http://mattgemmell.com/source). SyntaxHighlighter by Alex Gorbatchev (http://alexgorbatchev.com/SyntaxHighlighter/) jQuery and jQuery UI
Read the full README on GitHub

What Hacker News says

31 sources
I found this which is by far the closet to what I’m on about. Imagine this but with inline UI controls too (keyboard-controllable, natch), probably based on Nushell (I like Nushell), and maybe an “alternate display mode” type thing for UIs that want to take over more and not act as a transcript. And, no offence, but more visually appealing and implemented with a common-denominator subset of native UI controls where possible. Clearly the issue is not building it, but adoption. I don’t have an answer for that. https://github.com/unconed/TermKit
In Building a TUI is easy now
First time I saw an idea like this was with termkit [1], which I thought was great and was sad to see it didn't get continued development. I really feel like we overlook the ways in which we limit ourselves by having our CLI interfaces be tied to a thing that emulates a terminal from the 80s. The composability, scriptability, history, etc. of CLIs is great, but why should that preclude us from being able to quickly show a PNG or graph a function? Maybe it's an idea whose time has come. [1] https://github.com/unconed/TermKit
In Waveterm
There are many related attempts to make the terminal more modern, by including some HTML in it, improved auto-completion, and many other ideas. For example: - TermKit (https://github.com/unconed/TermKit, https://news.ycombinator.com/item?id=2559734) - GateOne (https://github.com/liftoff/GateOne) - DomTerm (https://domterm.org/) - Extraterm (https://extraterm.org/) - GraphTerm (https://github.com/mitotic/graphterm) - HTerm (https://news.ycombinator.com/item?id=7539648) - Terminology (https://www.enlightenment.org/about-terminology) I wonder about the state of these, or in general about terminal emulators. I really miss some extended features, like foldable text (https://gitlab.freedesktop.org/terminal-wg/specifications/-/...) or even just standardized image support (https://gitlab.freedesktop.org/terminal-wg/specifications/-/...). And mayb
Read the rest
e this could be further extended to also directly support sth like this autocomplete support. It becomes tricky when you think about how this works well together with tmux, SSH, Mosh, etc.
In Launch HN: Fig (YC S20) – Autocomplete for the Terminal
I miss TermKit[1]. Its a real shame that the developer abandoned it after it got a lot of hype. There's a huge opportunity for someone to come along and make either a new terminal encoding which allows rich, interactive output or extend VT somehow to which allows the same. If you could extend the terminal protocol, you might even be able to get it to work over SSH. HTML+JS seem like the obvious way to do it - even though the web is an awful platform, its standard, cross-platform and fully featured. Its the perfect worse-is-better solution for this. I think the hardest part would be figuring out how to reconcile browser-like UI events and file streams. Maybe you'd need to make a standardized event serialization format so your process could receive serialized events via stdin or something like that. I think it'll be a really hard sell if we
Read the rest
have to abandon our unix pipes entirely. [1] https://github.com/unconed/TermKit Previous hackernews discussion around termkit: https://news.ycombinator.com/item?id=2559734
In Rich Command Shells
I get excited each time I see an attempt to improve the shell, e.g. Mosh [1] and TermKit [2]. I believe that there is room for improvement. But I also think that the UI itself might be in its best form because it is as simple as: type the command, hit enter, get the result. And also equally important, its very efficient. I don't see that it can replace Bash but it can be useful in some cases. I really liked the Git functionalities. [1] http://mosh.mit.edu/ [2] https://github.com/unconed/TermKit
In Xiki: The Command Revolution

Showing the 15 most recent of 31 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.