What is new in cterm https://cterm.dev/blog/ 2026-10-16T00:00:00Z cterm https://cterm.dev/blog/cterm-has-a-home/ 2026-10-16T00:00:00Z 2026-10-16T00:00:00Z

cterm moves to its own domain. The site, the documentation and this blog are public at cterm.dev, and the app itself answers at app.cterm.dev.

<p>cterm started as a way to stop losing track of Claude Code sessions. One Mac, a dozen terminals, and the nagging feeling that one of them had been waiting for an answer for twenty minutes. It grew from there: a browser view of every session, the same view on a phone, a roadmap per project with a steward that keeps it in order, sessions that take an item and build it on a branch of their own, and one chat for whatever comes to mind.</p> <p>Until now all of that lived behind a sign-in form on an address borrowed from another project. Today it gets a home of its own.</p> <h2 id="what-lives-where">What lives where</h2> <ul><li><strong>cterm.dev</strong> is the front door: what cterm is, how it works, and pictures of it at work.</li> <li><strong>cterm.dev/docs</strong> is the documentation, now public. It is the same set of pages the app shows under Help, one page per area, from the first session to the steward, the master chat and monitors.</li> <li><strong>cterm.dev/blog</strong> is this blog: releases, how the parts work, and what comes next.</li> <li><strong>app.cterm.dev</strong> is cterm itself, for those with an account.</li></ul> <figure class="shot"><img class="for-dark" src="https://cterm.dev/img/ui-landing-session-dark.png" alt="A session waiting for an answer: the sessions of three projects on the left, the conversation with its tool cards in the middle, the request to push at the bottom." width="1440" height="900" loading="lazy" decoding="async"><img class="for-light" src="https://cterm.dev/img/ui-landing-session-light.png" alt="A session waiting for an answer: the sessions of three projects on the left, the conversation with its tool cards in the middle, the request to push at the bottom." width="1440" height="900" loading="lazy" decoding="async"><figcaption>A session waiting for an answer: the sessions of three projects on the left, the conversation with its tool cards in the middle, the request to push at the bottom.</figcaption></figure> <h2 id="how-the-app-is-reached">How the app is reached</h2> <p>cterm still runs where it always has: on a Mac, driving the real <code>claude</code> in terminals of its own, on its owner's Claude login. Nothing about that changes. What changes is the way in. The Mac now keeps an outbound tunnel to Cloudflare, which serves app.cterm.dev with its own certificate, so no port is opened at home and the old address keeps working while everyone moves over.</p> <p>The site you are reading is different: it is static, built from the repository's markdown on every change, and served by Cloudflare Pages. It stays up when the Mac sleeps.</p> <h2 id="a-note-on-the-screenshots">A note on the screenshots</h2> <p>Every picture on this site is drawn by a script from made-up people and projects, never captured from someone's real work. Before a picture is published, a scan reads the text in it and holds it back if it shows anything private. Some of the documentation's pictures are still being redrawn that way, so a few pages show fewer pictures than the app's own Help for now.</p> <h2 id="what-comes-next">What comes next</h2> <p>Accounts are still made by hand, and cterm still runs on one Mac. The next steps are about letting people bring their own machines: a runner on your computer that dials cterm, so your sessions run on your hardware while you use the same app from anywhere. More on that here when it is ready. <a href="https://cterm.dev/blog/feed.xml">Follow the feed</a> to hear first.</p>