The thing I keep noticing in 2026 is how much software is built to outlast its own usefulness. A weather app that wants you to subscribe. A notes app that wants your location. A search box that wants your history forever. The terminal page at google.com/search?q=terminal goes the other direction. It is built like a small museum exhibit, not a product. The room is open. The lights are on. You can look at it for ten minutes. Then you walk out and the lights go off behind you.
I went looking for it after a friend mentioned it on a forum thread, and I spent a Saturday afternoon poking at it. The product is called gsh 1.4. The visitor prompt at the top of the screen reads visitor@google:~$. Below that is a fake filesystem, a list of commands that work, and a couple of hidden commands that are not listed anywhere. None of that is the point. The point is that somebody at Google shipped a tiny, free, throwaway interactive exhibit on the most-trafficked search page in the world, and they did it without an upsell, a sign-up wall, or a prompt to install an app.
That kind of restraint is the rare thing in 2026. The exhibit does not want anything from me. It does not save my session. It does not call home. It does not beg me to come back tomorrow. It is what software looked like when people shipped it for the joy of the thing.
The exhibit does not pretend to be a product, which is the design
Most modern software is dressed up as a friend, a coach, or a therapist. The terminal page does not pretend anything. It is a shell, with a fake filesystem, that behaves like a shell. The visitor types commands. Commands return text. There is no narrative arc. There is no “Hello, how can I help you today?” preamble. There is no attempt to make the visitor feel seen.
I think this is more interesting than it sounds because the design choice is honest. A search box and a command line accept text in, return text out, and let the visitor refine until the answer is useful. That loop is the same one your browser, your IDE (integrated development environment, the application programmers use to write code), your terminal multiplexer, and your chatbot all share, even when the visual design hides it. The exhibit pulls the curtain back. It says: this is what every interface you use is doing, and here it is without the costume.
That posture is rarer than it used to be. Most products are built to extract attention, time, or money. The exhibit is built to give you five minutes of clean interaction with a primitive you have probably forgotten existed. The fact that it sits on the most-visited search page on the internet and has not been turned into a sign-up funnel is itself the news.
- It behaves like the underlying primitive. Text in, text out, refine.
- It does not dress the loop in costume. No friend, no coach, no chatbot preamble.
- It survives on the page without monetization. No upsell, no prompt, no second-screen popup.
- It is built for the joy of the thing. Not the metrics of the thing.
The two details that earn the title of exhibit, not toy
Most fake terminals feel cheap inside ten seconds. The exhibit gets two specific things right, and those two are why it earns its place on the list of products I trust.
The first is up-arrow history. Press the up arrow once and you see what you typed before. Press it again and you see what you typed before that. For anyone who has ever typed into a real shell, that affordance (a design clue that suggests how to use something, where the up arrow here signals that the past is reachable) is the difference between a tool that remembers you and a tool that asks you to start over every time. The exhibit has it. Most browser toys do not.
The second is single-match tab completion. Type the first letters of a command and hit tab. If there is only one match, the exhibit fills in the rest. If there is more than one match, it does nothing. That is not the polished fuzzy matching of modern shells, but it is enough to make your hands reach for the habit instead of the help text. The pair of affordances is what tells you the engineer who built it is a working shell user. You cannot fake that with a CSS animation. You can feel the difference the moment you start typing.
- Up arrow walks back through history. A real affordance, not a mock.
- Tab fills in single matches. Limited but real.
- Both together signal working engineering. The kind of detail you cannot fake.
- The help text is honest. It lists what works and does not overpromise.
The list of commands is honest about what is missing
The official help lists tree, cat, grep, search, man, uptime, whoami, date, history, and clear. That is a fair list, and I appreciate it being a fair list. Many toys list ten commands and you find out only seven of them work. This exhibit lists ten and all ten do what the help text says.
Two more exist that are not listed. I will not spoil which ones. The hint is that they start with letters nobody thinks to type on a first visit. The reason I am leaving them for you to find is that finding them is part of why the exhibit feels like a museum instead of a tour. A tour tells you everything. A museum lets you look.
What surprised me is how quiet the exhibit stays while you poke around. There is no scoring. There is no progress bar. There is no “you have explored 60 percent of the museum” nag (an unwanted reminder prompt). You type commands. The exhibit responds. You walk away when you are done. That quietness is the thing most modern products have forgotten how to ship.
- Ten listed, all working. No overpromising in the help text.
- Two hidden, findable. Part of the museum experience.
- No scoring, no progress, no nag. The exhibit does not chase you.
- Quiet is the design. A rare thing in software that wants your attention.
What this teaches anyone who pays attention to software
If you build anything that people touch, this exhibit is a useful artifact to keep in your back pocket. It is a search engine admitting it is built on a primitive that is older than its visual design. That admission is a teaching moment disguised as a toy. You can show it to a class on interface history and let them feel the loop their chatbot hides. You can show it to a class on product design and let them argue about why the missing onboarding is the design. You can show it to a writer who is trying to explain why some products feel good and others do not.
The deeper lesson is that the loop is older than the design language sitting on top of it. The exhibit makes that visible. That observation is worth more than any feature comparison chart, because it tells you which products are respecting the loop and which products are trying to dress it up so you forget what is happening.
The exhibit is also a useful test for any team building software today. If your product cannot survive being looked at for ten minutes without asking the user for something, you have a different kind of problem than the exhibit does. The exhibit can survive the ten minutes because it does not want anything. Most modern products cannot, and that is a design choice you can reverse.
- A useful artifact for teachers. Old loop, new costume, exposed.
- A useful test for product teams. Can your product survive ten quiet minutes?
- The loop is older than the design. Search boxes, chat boxes, voice assistants all share it.
- Restraint reads as confidence. A small thing, and the point.
Trade-offs
The exhibit is not free in attention. If you actually start poking around, you will spend ten to twenty minutes on it, which is longer than most people intend to spend on a search page. The fake filesystem is small, so exploration hits a wall faster than you might expect. There is no way to save anything you find. There is no way to share a session.
The privacy posture is the part that needs to be said honestly. Nothing leaves your browser. There is no account. There is no analytics call I could find while poking around. The URL itself still goes through Google’s normal search infrastructure, so your visit is logged the way any visit to google.com is logged. Treat the page as private from the exhibit to you, and public from your browser to Google. That is a fair trade for a free room you did not have to install.
In my case, the cost was a Saturday afternoon I would have spent doomscrolling (scrolling social media without a goal, looking for a feeling that does not arrive) instead. Your math will be different if you are the kind of person who opens a terminal prompt and immediately wants to close it. If you have ever typed into a real shell, this is a clear win. If you have not, the exhibit is a friendly introduction that costs nothing to try and nothing to walk away from.
The thing I gave up to learn this was the assumption that all interactive pages on the internet want something from me. Most of them do. This one does not, and that is the news.
If you only do one thing from this article, open google.com/search?q=terminal, type tree, and spend five minutes looking around. The rest of the visit is up to you.