Tue, 13 Oct
The home page shows Fork as it is now
The home page is back to the Fork window that slides up over the opening words as you scroll, and the window now looks like Fork 1.2: F0RK at the top of the sidebar, Workspace info, the Files buttons, What’s new, settings and help at the bottom, and the prompt in the terminal. The page with little Mac windows stays a preview.
why? The window still showed the app from before the redesign in a few places. Now what you see on the site is what you get when you download it.
Fri, 9 Oct
A new home page, with little Mac windows (preview)
The whole home page is rebuilt on a preview page. The nav is a Mac menu bar; “Fork” sits in the middle with five little retro windows around it, each playing a real recording of Fork, and you can drag them around. Then a row for each thing Fork does, with a chat bubble and a bigger recording, a note from the maker, the latest changes from What’s cooking, questions and the download. Every window has a soft tinted title bar with shiny traffic lights.
why? The earlier tries looked like templates and were turned down. This one is playful and shows the real app moving instead of drawings of it.
The footer is Fork’s own folder
The end of the page now lists its links as a folder of files, the way Fork’s Files tab shows them: download, install.sh (click to copy the install command), what’s cooking, the source and where to find me. Beside it, the latest version with Fork’s square and when it shipped. Under both, a little keyboard with four keys spelling FORK sits at the foot of the page; point at a key and it presses down.
why? The old footer was a doodle and two icons, with no way to download or find the source from the bottom of the page. Now the last thing you see says what Fork is, where it’s at and where to go next.
The window at the top tells the whole story
The Fork window on the home page now shows your site live while the agent works, reloading as each edit lands. When it finishes, the panel moves to Changes and wipes from before to after, then to Design, where the colour the agent changed eases to its new value. In dark mode the site is dark too.
why? The window only showed the before and after, in white even on a dark page. Seeing the app, the change and the design system one after another shows what the panel is for.
A shorter home page that says what Fork does
The first line now says the job: the terminal that tells you when an agent needs you. The games and themes sections became cards in “Also in Fork”, next to new ones for reading beside the terminal and for the safety nets, so the page is about a screen shorter. What’s cooking moved into the same greys, with the latest version drawn in light lines.
why? “Meet Fork” didn’t tell a new visitor what Fork is, and the page took a long time to get to the point. What’s cooking still had the old cream and pink.
The home page shows the new Fork
The home page now shows Fork as it is today: workspaces as tabs, the status squares, Workspace info, and the panel’s Changes and Design tabs, all in Fork’s own greys and in dark mode when your Mac is. The blob and the colour shaders are gone. Line drawings that answer your pointer take their place, and each plays once as you reach it.
why? The redesign changed how Fork looks and what it’s best at, so the page should show the real thing. The drawings match the pictures inside Fork itself.
- 🍜 Fork 1.2.0 served at 2:27 pm
A new way to start a workspace
⌘N opens a quick search box: type a name to make a folder, paste a GitHub link to get a project, or pick one you’ve used (a project you already have comes first, so you don’t make it twice). With no workspace open, three cards show the ways to start, each with a little line picture that moves when you point at it.
why? Starting something was a long list to read. Most of the time you already know what you want, so one box you can type into is quicker; the first time, pictures explain the choices better than words.
Name your workspaces and terminals
Double-click a workspace tab, or press ⌘R, to rename it. Terminals take the name of the task your AI tool is working on, like “Fix login bug”, and keep it after it finishes; double-click one, or press ⌥⌘R, to name it yourself. Esc now cancels a rename instead of saving it.
why? With a few workspaces and terminals open, “Terminal 2” and a folder name didn’t say which was which. The task is the name you’d have given it anyway.
Your app’s address lives in Workspace info
The “Your app is running · Show it” bar under the terminal is gone. The address in Workspace info is now a link: click it to see your app.
why? The bar said the same thing as Workspace info and took space from the terminal every time a dev server started.
- 🍜 Fork 1.1.0 served at 1:30 am
See what your AI tool changed: Changes
When your AI tool finishes while your app is running, Fork takes a picture of your app before and after. Open Changes (⌘P) to compare them side by side or with a slider, and see which files changed. You can turn it off in Settings → General.
why? After an AI tool edits your project, the first question is “what does it look like now?”. Fork already sits beside your app, so it can show you without you hunting for the difference.
Your project’s design, in one place
The new Design tab (⌘P → Design) gathers your project’s colours, spacing, type and corner radii from its CSS, Tailwind and code.
why? Designers think in tokens, but they’re scattered across files. Seeing them together makes it easy to spot a stray colour or check what an AI tool just added.
A Files tree with colours
Every file in the Files tree has a coloured icon for its type, including logos for React, Tailwind, Next, Docker, Python and more.
why? You find a file by its look before you read its name. Colour and familiar logos make a long list quicker to scan.
Fork opens about twice as fast
Fork shows its window without waiting for your shell to finish loading. On a Mac with a busy shell setup, opening went from 1.85 seconds to 0.85.
why? Fork was waiting a whole second for something it only needs later. Things that do need it, like Ask AI, wait for it on their own.
The needs-you pulse settles
When a workspace needs you or something failed, its square pulses three times and then stays lit, instead of pulsing forever.
why? A pulse that never stops kept your Mac busy even while you weren’t using Fork, which costs battery. Three pulses catch your eye; the colour stays as the reminder.
Workspaces keep their folder after a restart
Each workspace reopens in its own project folder after you quit and open Fork again, with the right name, files and changes.
why? Before this fix, a workspace reopened in whatever folder its terminal was last in, so its name and files could be wrong after a restart.
Wed, 7 Oct
⌘N for a workspace, ⌘T for a terminal
⌘N opens a new workspace: Home, a recent folder, a new folder or a project from GitHub. ⌘T adds a terminal to the workspace you’re in.
why? A new project and another terminal for the same project are different things, so they get different keys.
A new look: workspaces along the top
Your work is organised into workspaces, one per project folder, each with its own terminals. They sit along the top of the window, and the sidebar shows the one you’re in: its folder, its files and search.
why? Designers work project by project. Grouping terminals by folder keeps everything for one project together and makes switching between projects one click.
Tue, 6 Oct
Settings in four pages
Settings is split into Appearance, General, Notifications and Privacy.
why? One long scrolling list made things hard to find. Four short pages each fit on screen.
A better code preview
Code in the preview is coloured more accurately, and you can pick lines to send to your AI tool.
why? Pointing at the exact lines you mean is clearer than describing them.
Files that changed are marked
The Files tree marks files that are new or changed, like your code editor does.
why? When an AI tool edits your project, you can see at a glance where it worked.
Sun, 4 Oct
A soft chime when something finishes
Fork plays a soft chime when something you were waiting on finishes. Turn it off in Settings → Notifications.
why? You’ve often switched to another app while a long task runs. A gentle sound tells you it’s done without you checking.
Squares show each workspace’s state, and the blob retires
Each workspace has a small square: it ripples while something’s working, and turns yellow or red when it needs you or something failed. The blob is gone for now, and so is the bottom bar.
why? With several workspaces open, you need to see every one’s state at once, right where you switch between them.
Light, Dark or System
Pick Light, Dark or System in Settings → Appearance. Colour themes for the terminal are paused for now while the new look settles, and will come back.
why? The new look is built on one set of colours, so it can follow your Mac between light and dark.
- 🍜 Fork 1.0.2 served at 11:06 am
Check for Updates… in the Fork menu
The Fork menu now has Check for Updates…. It tells you straight away if you’re up to date, or shows the new version and what’s in it. The menu also says About Fork, Hide Fork and Quit Fork now, so Fork goes by its own name everywhere.
why? Fork checks for updates by itself every hour, but when you hear a new version is out you shouldn’t have to wait for it. Every Mac app has this item, so it’s where people look.
- 🍜 Fork 1.0.1 served at 10:36 am
The notch is off until you turn it on
Fork no longer shows up in your notch on its own. If you’d like to see what your terminals are doing from any app, turn on “Show what’s happening in the notch” in Settings → Notifications. With it off, you get the usual Mac notifications instead.
why? The notch is prime space on your Mac, and not everyone wants an app living there. It should be your choice to switch it on, not something to hunt down and turn off.
Sat, 3 Oct
- 🍜 Fork 1.0.0 served at 12:04 pm
Fork updates itself
When a new Fork is out, it downloads quietly in the background. Once it’s ready, a Restart pill shows in the top bar: click it to update now, or keep working and it updates the next time you quit Fork. Your tabs come back either way.
why? Updating used to mean clicking the pill and waiting while Fork downloaded itself again. Now that Fork is signed, macOS can swap in a new version safely, so the waiting happens while you work.
Fork opens without Apple’s warning
Fork is now signed with an Apple Developer ID and checked (notarized) by Apple. Downloading Fork.dmg from this site no longer shows “Apple could not verify Fork”, so there’s no trip to System Settings to click Open Anyway.
why? That warning was the first thing a new person saw, and it made Fork look unsafe. Now that we have an Apple Developer account, Apple can vouch for every release.
Fork remembers it’s allowed into your Downloads folder
Terminals in Downloads, Desktop or Documents kept failing with “operation not permitted”, and macOS’s “allow access” question could freeze Fork with a spinning cursor. Now one Allow lasts through every update, Fork keeps responding while macOS asks, and What went wrong? explains it and opens the right page in System Settings.
why? macOS saw every new version of Fork as a brand-new app and forgot the permission. Fork was also checking your folders in a way that made it stop and wait for the answer.
Fri, 2 Oct
No stray black bar in Mission Control
When you swipe up to Mission Control, the notch no longer shows up as an empty Fork window with a black bar. Your real Fork windows still show as usual.
why? The notch is meant to blend into your Mac, not look like a broken window when you're switching between apps.
A calmer landing page
The colours behind each section no longer shift when you move your mouse. The “See your work beside it” card is a soft green instead of crumpled paper. And the thank-you letter is now a plain white sheet, folded in three, that unfolds as you reach it. The envelope is gone.
why? The moving colours and the paper texture didn’t feel right for Fork. The page should feel quiet and clean, and a letter that simply opens says thanks without the extra props.
The notch stays a notch
While Claude works, the blob sits just left of the notch and how long it’s been sits just right of it, all inside the menu bar. When something’s done, failed or your app is ready, the notch says Done, Failed or Ready for a few seconds, and clicking it takes you there. Hovering still opens the list of every tab.
why? The notch used to grow down into a big black card every time something happened, which pulled your eyes away from what you were doing. Status should be there when you glance at it, not jump at you.
No more windows popping up or a missing Dock icon
Fork no longer hides and reshows its windows by itself, and its icon stays in the Dock. The notch now only rebuilds when it really moves, like when you close the lid or plug in a screen.
why? Since the notch arrived, setting it up briefly hid all of Fork, Dock icon included, and it set itself up again every time the screen changed. That looked like windows opening on their own and the icon going missing.
Thu, 1 Oct
- 🍜 Fork 0.4.0 served at 3:17 pm
Fork lives in your notch
On a MacBook with a notch, while you’re in another app, the notch grows down to show what your terminals are doing. You’ll see “Claude is working” with the blob thinking and how long it’s been. Then for a few seconds it shows when something’s done, when a command failed (click for “What went wrong?”) or when your app is ready (click to see it). Hover the notch to see every tab and jump to any of them. It replaces the Mac banners on these Macs, and you can turn it off in Settings → Notifications.
why? You go to another app while Claude or a build works, and you shouldn’t have to keep coming back to check. The notch is right where your eyes already go.
No “What’s new” repeat after you update
Updating from the pill in Fork no longer opens the new version with a “What’s new” window. You read those notes just before clicking Update and restart. Updating any other way, like downloading it again, still shows them once.
why? After an update Fork should pick up right where you left off, not show you the same thing twice.
OpenCode and other terminal apps work fully in Fork
Apps that run inside the terminal, like OpenCode, now get everything they ask for. That means full colour, pictures in the terminal, copying to your clipboard (apps can never read it) and links you can ⌘-click. Fork also knows when OpenCode, Codex or Gemini is working: the bar says “OpenCode is working.”, Esc stops it, and the tab’s blob shows when it’s done, just like Claude. When something finishes or needs you while you’re in another app, a Mac notification and a dock badge tell you, and clicking it takes you to that tab. You can turn that off in Settings → Notifications.
why? The OpenCode team’s OpenTUI kit showed us what modern terminal apps expect from a terminal, and Fork was quietly missing some of it. OpenCode’s copy didn’t work, for one. Fork is for whatever tools you use, so they should all feel at home in it.
The Fork window rises over the headline as you scroll
On the home page, the headline now stays where it is when you start scrolling, and the Fork window slides up over it, growing to full size while the headline fades back. Once it’s covered, the page scrolls as normal. On phones it just scrolls, and with reduced motion on nothing fades or grows.
why? It hands you from the promise straight to the thing itself, the terminal, in one motion.
Wed, 30 Sep
The home page is about the terminal, not one AI tool
The “Built around Claude Code” section and its link in the menu are gone. The headline, the games section and the questions now talk about the terminal itself: say what you want, understand what went wrong, see your work beside it, and use whatever tools you like in it.
why? Fork is a terminal for everyone and doesn’t favour any one platform. People can use it however they want.
The sticky note comes off the home page
The “just cooked!” note is no longer taped to the Fork window at the top of the home page. What’s cooking is still a click away in the menu and the footer, and the note stays on the first landing page at /v1.
why? The window is the thing to look at, and the note was covering part of it.
The home page says hello when it opens
Opening the home page is a little show now. “Meet” and “Fork” rise out of a soft blur, the blob pops in between them and smiles, and the fork doodle is tossed into place. Then the Fork window tips up onto the page, its prompt types itself, Claude’s reply comes in a line at a time, and the “just cooked!” note is slapped on last. With reduced motion on, it’s all simply there.
why? First impressions count, and this shows Fork working before you’ve scrolled. The buttons are ready from the first moment, so nobody waits for the show.
The first landing page lives on at /v1
The original pink page, with the noodle and the snowman, is kept at /v1. The new page stays the home page.
why? It's where Fork's website started, and worth keeping around to look back at.
A bigger Fork window at the top of the home page
The patterned background behind the Fork window at the top is gone. The window now sits straight on the page, and it's bigger.
why? The app is the point of the page, and the pattern was competing with it.
The new home page is the home page
fork-terminal.vercel.app now opens on the page that walks through what Fork does, and old /v2 links land there too. It ends in one panel, edge to edge, with the thank-you letter and the footer together.
why? It explains Fork before you download; the old page was one line and a picture. Ending in one panel makes the letter and the sign-off read as one goodbye instead of a stray strip at the bottom.
Rounded corners on every window
The Fork windows and the small window snippets in the feature cards now have rounded corners at the bottom too, like a real Mac window.
why? The square bottom corners made the windows look cut off.
A thank-you letter, and this page in the new look
At the bottom of the new home page, an envelope opens the first time you scroll to it, and a letter slides out with a thank-you note. Its P.S. says the soft moving colours are Paper Shaders, with
npm i @paper-design/shaders-reactand a Copy button. The letter paper is a Paper shader too. What’s cooking moves to the same cream paper: flat cards, each day’s date pinned on the left, and a quiet shader behind the title.why? The shaders are someone else’s lovely work, so they get a proper credit, and anyone who likes them can grab them in one click. This page should look like it belongs with the new home page.
A new home page that shows what Fork does
A second version of the home page, at /v2 for now. It walks through Fork one idea at a time: ⌘K in plain words, “What went wrong?”, suggestions and safety nets, your app beside the terminal, the Claude Code features, a real game of Snake, and a theme picker that re-colours the Fork window. The blob from the app says hello in the headline, and soft Paper shaders move behind the demos. It’s on cream paper, like the app icon.
why? The old page had one line and a picture, so you had to install Fork to find out what it does. This one explains it before you download, and each part is measured, so we can see what people actually read.
The home page fits phones
On a phone the sticky note on the Fork window shrinks to a small “just cooked!” tab on its corner, so the window shows through. The Download button spans the screen, with View on Github centred under it.
why? On phones the full note covered almost half the Fork window, and View on Github wrapped onto its own line in an odd spot. The tab still takes you here.
Tue, 29 Sep
What's cooking: this page
A changelog for everything that goes into Fork, with the time it landed and why it was made. It's updated with every change, big or small. The newest one is pinned to the Fork window on the home page as a sticky note.
why? Fork changes a lot, often several times a day. Release notes say what changed, but not why. This keeps the whole story in one place for anyone curious, and for me.
“Claude is working” only while it's actually working
The bar at the bottom shows only while Claude is working on your prompt. It says “Claude is working.” and Stop sends Esc, the key Claude listens for. When Claude is waiting for you, the bar is gone and the tab's blob shows Ready. If Claude finishes in another tab, that tab says “Finished while you were away”.
why? Before this, the bar said “Something is running” the whole time Claude was open, even when it was just sitting there waiting for you. The cause was a small bug: the shell told Fork only the first letter of one-word commands, so plain
claudewas reported as “c”. Fixing it also means Claude reopens properly after a restart.
Mon, 28 Sep
Read a book while Claude works
Open a PDF or EPUB in the side panel (⌘P → Read, drag one in, or click it in the file list) and read next to your terminal. Books keep their own fonts and white pages. Read a page at a time or as one long scroll. Fork remembers your place in every book, and when Claude finishes a gentle note says so, with a link back to the terminal.
why? Waiting on a long prompt is dead time, and plenty of people would rather read a few pages than stare at a spinner. The panel already showed files and your running app, so a book fitted right in.
Sun, 27 Sep
A dashboard for the website
A PostHog dashboard, “Fork website — who visits”: visits per day and week, where people come from, countries, desktop vs phone, how many visits turn into a download, and who finds the snowman.
why? The app had a dashboard but the website didn't, so there was no way to see whether people actually reach the Download button. Its charts are kept as code, so it stays in sync.
- 🍜 Fork 0.3.1 served at 4:59 am
Smarter matching, without a key inside the app
Smarter matching now goes through Fork's own server, so the app carries no secret key. It works exactly as before.
why? Anything inside an app can be dug out by someone determined. Keeping the key on the server is the safe way to ship it.
The website answers Fork's questions
fork-terminal.vercel.app/api/jev: the server that ⌘K's smarter matching talks to. It holds the TypeSafe key, accepts only Fork's two questions, and limits how often each person can ask.
why? It lets the app use TypeSafe without shipping the key. It's rate limited and fussy about what it accepts, so nobody can borrow it for anything else.
- 🍜 Fork 0.3.0 served at 4:45 am
⌘K: names that match come first
Typing “play snake” opens Snake, and exact names beat loose matches. Game cards also say what each game is.
why? Asking for something by name and getting something else first felt broken.
Games open beside the terminal
Snake, Stack and Space Run open in a split next to your terminal (or their own tab if there's no room), in small square pixels. Esc goes back to the terminal, and the game pauses when Claude or a command finishes.
why? Games are for the wait, so they should sit next to the thing you're waiting on, not cover it up.
Ask AI answers sooner
Fork gets Claude ready in the background while ⌘K is open, so answers arrive in about 5 seconds instead of 8 to 10. Nothing is sent until you press Ask AI.
why? Most of the wait was Claude starting up, not thinking. Starting it early removes that without sending anything you didn't ask for.
⌘K answers in place
Type what you want and ⌘K shows the answer as a card: what it does, the command, and Run. Commands that need a name ask for it right in the card.
why? Before, ⌘K typed half a command into your terminal and left you to finish it. If you're new to terminals, that's exactly the scary part.
⌘K understands plain words
“take me up one folder” or “save my work” finds the right command in under a second, without Claude. “What went wrong?” also recognises errors worded differently from the ones it knows. You can turn it off in Settings → Privacy.
why? People describe what they want in their own words, not in command names. Claude could handle that, but it's slow for something this small.
“What went wrong?” knows 35 common errors
Missing tools, typos in folder names, a port already in use, Git asking who you are, merge conflicts and more are explained instantly, even offline, with a fix Fork types for you. For anything unusual, Ask AI takes a look.
why? Most errors people hit are the same few dozen. Answering those instantly and for free beats waiting on AI every time.
The app dashboard keeps itself in sync
The dashboard's charts live in code. Checks fail if Fork sends an event no chart shows, and every release updates the dashboard.
why? Dashboards quietly go stale. This way a new feature can't ship without being counted.
A dashboard for the app
“Fork — how it's going”: 20 PostHog charts on new installs, the first run, and which features people use.
why? To learn where new people get stuck, from real use instead of guesses. It's all anonymous, and never your commands or files.
Sat, 26 Sep
Open things in their own apps
Settings → Links & files: turn off “Open links and files inside Fork”, and your app opens in your browser and files open in Preview, Figma or whatever your Mac uses for them.
why? Some people like everything in one window, others have their browser just so. Both are fine.
Find, clickable links, and a much longer memory
⌘F finds text in a terminal. ⌘-click opens any web address. Each terminal keeps 10,000 lines instead of 1,000, and your Mac's graphics chip draws them, so long output scrolls smoothly.
why? Claude conversations get long. Scrolling up to find something that had already vanished, or stuttering through it, got old fast.
Fork reopens the way you left it
Quit, close or update, and next time your tabs, splits, folders and what was on screen are back. If Claude was running, it picks up the conversation where it left off.
why? Updates restart Fork, and losing your whole setup every time you update is a good reason not to update.
- 🍜 Fork 0.2.1 served at 7:53 pm
Updates show up within the hour
Fork checks for a new version every hour and whenever you switch back to it, instead of every 6 hours.
why? Fixes were landing faster than people were getting them.
One command to ship a release
npm run releasechecks everything, bumps the version, turns the changelog into release notes, builds, verifies and publishes. Betas never get pushed to people on the normal releases.why? Releasing by hand has a dozen steps to forget. Now every release goes out the same careful way.
- 🍜 Fork 0.2.0 served at 5:21 pm
Fork looks for updates by itself
When there's a new Fork, a small pill shows in the top bar. Click it for what's new, then Update and restart. The first time you open a new version, its notes show once.
why? Nobody should have to reinstall an app by hand to get fixes.
A welcome for people new to terminals
Three short cards with the blob explain what a terminal is and that Fork does the typing. Then a spotlight tour lights up one part of the window at a time. You can replay it from Settings → Help.
why? Fork is for designers, and a blinking cursor is a scary first thing to see.
Every tab has its own blob
Each terminal in the sidebar has a little blob that shows what it's doing: ready, running, failed, finished while you were away, or dozing.
why? With a few tabs open, you couldn't tell which one needed you without clicking through them all.
Light, dark or follow the Mac
Appearance can be Light, Dark or System. System picks a light and a dark theme and swaps between them when your Mac does.
why? Plenty of people switch to dark mode at night. Their terminal should follow.
Back and forward through folders
← → in the sidebar (or ⌘[ and ⌘]) move through the folders you've visited, like Finder.
why? Designers already know how Finder moves around. Fork should work the same way.
Anonymous usage
Fork sends which features get used, under a random ID. Never commands, file names or what's on screen. You can turn it off from the start screen or Settings → Privacy.
why? To make Fork better for people new to terminals, I need to see where they get stuck. It's anonymous, so nobody gives up their privacy for that.
Shift+Enter starts a new line in Claude
Shift+Enter adds a line instead of sending your message. Enter still sends.
why? Sending half-written prompts by accident is the worst.
An installer that looks like Fork
Opening Fork.dmg shows a warm cream window with a hand-drawn arrow: “Drag Fork into Applications”.
why? The installer is the first thing anyone sees of Fork, and it was a plain grey box.
A live Fork window on the website
The screenshot at the top became a working copy of the Fork window. You can hover it and type in its terminal (nothing actually runs). The noodle, bowl and snowman doodles came to life too.
why? A terminal you can poke at says more than a picture of one. The doodles make it feel like a person made it, because one did.
Fork gets a website
fork-terminal.vercel.app, built from the Figma design: Download for Mac, why Fork exists, and a thank-you.
why? Fork needed a home that isn't a GitHub page, somewhere to send people.
- 🍜 Fork 0.1.0 served at 2:37 am
Fork is public, and a real Mac app
Fork is public on GitHub and installs as a real Mac app, with a hand-drawn fork for its icon.
why? It had been living as a side project on one Mac. Time to let other people try it.
The blob shows when something is working
Bloub, the blob mascot, replaced the green pulsing dot. It thinks while a command runs and follows your theme's colours.
why? A dot tells you something is happening. A blob that thinks along with you is nicer company.
Fri, 25 Sep
One set of icons everywhere
Lucide icons across the whole app, and files show what they are: images, code, styles and docs each get their own icon.
why? The mix of hand-drawn icons and text characters looked unfinished.
See your files and your app next to the terminal
⌘P opens a side panel. Click a file to preview it (images, video, Markdown, code with colours), and it updates live as Claude edits it. When your app runs on localhost, “Show it” opens it right there.
why? Designers want to see what Claude is changing without opening a code editor. Watching the edits land is half the fun.
Settings, 27 themes and your fonts
Settings (⌘,) with 27 themes, four bundled coding fonts plus any on your Mac, font size, and a live preview. The whole app follows the theme.
why? People spend hours in their terminal. It should look the way they like.
Splits, sidebar and ⌘B
Drag to resize split panes and the sidebar. ⌘B hides the sidebar, and the bottom bar only shows when it has something to say.
why? More room for the terminal, and less for everything else.
That’s everything so far. More soon.