Build log
This app and site were built in conversation with Claude Code. Here is the order things happened in, what was decided and why, what has been checked and what hasn’t been yet.
Order
- Reading the starting point. Coucou, spotted on Instagram, is an open-source app for keeping an eye on AI coding agents from the Mac notch. It was made by Louis Raillé and its code is MIT-licensed. About 75,000 lines of its source were read and sorted into what could and couldn’t carry over to studying.
- The core didn’t carry over. Coucou’s core receives signals sent by agents, and studying has no agent to send them. That part had to be rebuilt from scratch as distraction checks and reading selected text.
- The first design was a subscription service. Architecture and flows were drawn for a server that calls the AI and keeps course material in an account.
- The screens were checked against UX guidelines. 120 guidelines were applied to the notch screens and 14 things were fixed: failure screens, waiting screens, never relying on colour alone, and so on.
- The direction changed. It runs only on the Mac, with no server, and is used only by clicking, with no shortcuts. Making it work came before making money.
- The app was built and a design system set. Paper, blue-black ink and a highlighter. The app and the site share the same colours and rules.
- After trying it, asking was redesigned. Instead of the notch asking first, a button appears at the top of the right-click menu and the question window opens right there. The list became course names, and the notch’s motion follows Coucou’s.
- Connecting to the Claude app. The Claude app turned out to contain a signed-in Claude Code, so StudyNotch runs that in the background and takes only the answer. Two real questions confirmed answers for both text and a screenshot.
- The island was rebuilt to follow Coucou closely. It peeks when you point at it, opens to a 640pt card with tabs when you click, shows course pills and a record tab, folds by itself 15 seconds after you leave, and carries a mascot of our own that springs between its places.
- The website was rebuilt around a 3D mascot. The mascot became a small pad of paper built in CSS 3D. It sits on the demo screen and jumps into the notch island when it opens. Three reviewers, one each for design, finish and motion, went over it twice, with screenshots and interaction tests in a headless browser.
- The app moved to English. Every screen, menu, error message and mascot line, and the instructions sent to the AI. Answers come back in the language the question is typed in, so a question typed in Korean gets a Korean answer. The labels match the ones this site’s demo already used, and every screen was rendered again to check that nothing longer in English was cut off.
- The mascot became Squat. The paper drafts looked machine-made, so the mascot was redesigned from black silhouettes, through flat cut-outs, to a glossy black droplet drawn in 3D. Its white eyes are painted on its surface, change shape with the state and follow the pointer; their size and the long, tapering smile were tuned by hand. Later its drop tip and feet went, leaving a round body. The same shader draws it in the app (Metal) and on this site (WebGL), with no images and no outside library.
- The colours were cut down. With a colour per course and per state, the screens looked scattered. Now the island is white and grey on black. Its one touch of colour is a faint light, in the state's colour, behind the cards and the mascot. Courses have no colours.
- The website moved into the mascot’s studio. The paper, ink and yellow highlighter looked like another product next to a glossy black mascot. Now the site is a softly lit black with white type in the Mac’s own font, round buttons, and edges caught by the same cool rim light as the mascot. A picked sentence on the demo page turns black with white text, and the app’s screens sit on the page as they are.
- Courses can be linked to folders, and edited. A PDF could only be added after its course existed, and a course could not be changed afterwards. Now the new-course page takes a linked folder or PDFs before “Add” (and forgets them if you close it), and each course has an Edit page for its folders, PDFs, name and removal. Linked folders are read where they are and never written to.
- A course became the AI’s project. Only one matching page used to go with a question. Chat Projects on claude.ai and chatgpt.com can’t be filled by another app, but the tools behind each AI treat a folder as a project. So each course keeps a text copy of all its PDFs, and the AI may open that folder, read-only, when the page isn’t enough. Tried for real: asked for two facts that were not on the page sent, Claude and ChatGPT both opened the files and answered with the file and page.
- The first step became choosing the AI. Someone on another Mac had no clear way to connect an AI. Now the first launch opens at “First, connect the AI that answers you”, with a tile each for Claude, ChatGPT and Gemini that signs in, installs or downloads what is missing. An AI that is already signed in on the Mac (say, in the ChatGPT app) is never used until you press Connect, and “Auto”, which used to answer with whichever was signed in, is gone. Each tile shows the account it would use; “Another account” opens the service’s sign-in page for a sign-in kept only for StudyNotch, and “Test connection” sends one real question to prove it works. Gemini moved to Google’s Antigravity CLI, because the older
geminitool stopped answering personal accounts in June 2026.
Decisions, and why
| Decision | Why |
|---|---|
| No server | To make it work first. It removes accounts, payments and storage altogether. The trade-off: there is no way to charge by usage. |
| Click only, no shortcuts | The hand that selects the text is already on the mouse. |
| It starts from a right-click | Something popping up every time you select text gets in the way. One button is added to what you already do when you want to ask: right-click. |
| Answers open where you clicked, not in the notch | You read the answer next to the sentence. The window can be dragged. |
| No Claude window | You never leave the screen you are studying. Claude only writes the answer, in the background. |
| Distractions are flagged, not blocked | If it blocks, you turn it off. It tells you and lets you choose. |
| No built-in PDF reader | You keep using Preview and your browser. |
| No seconds in the time left | A number that keeps changing is the first thing your eye catches. |
| If it isn’t in the material, it says so | Answers end with “not from your material”. Pretending otherwise would make it untrustworthy. |
What came from Coucou, and what is new
Coucou’s code is MIT-licensed, so it can be reused as long as its notice is included. The notch island follows Coucou’s approach: the spring when it grows, the curve when it shrinks, the timing of content fading out and in, the folded island’s top corners flowing into the edge of the screen, and the set of options for running a signed-in tool read-only. What was borrowed, with the full licence, is listed in the project’s THIRD_PARTY_NOTICES.md.
The name Coucou, the Mochi character, and Coucou’s icons and sounds were not used. They belong to the original author and sit outside the MIT licence. Distraction checks, the right-click button, the question window and finding pages in course material don’t exist in Coucou and were built new.
Code layout
| File | What it does |
|---|---|
AppModel.swift | State and every action: sessions, drift cards, the question flow. |
IslandPanel.swift | The window over the notch: reading the notch size, choosing the screen, letting clicks outside the island through, and which clicks reach the island. |
IslandViews.swift | The island’s shape, motion values, colour tokens and shared buttons. |
Mascot.swift | The mascot in the app: its expressions, blinks, glances, the eased change between faces, a hop, and a glow in the state’s colour. |
MascotRenderer.swift | Draws the mascot in 3D with Metal: the same shader as the website’s. |
IslandScreens.swift | The island’s screens: peek, tabs and cards, course pills, record, add, drift card, summary, connection check, greeting and the closing countdown. |
RightClickWatcher.swift | Shows the button above the right-click menu. |
PopupPanel.swift | The question window. |
SelectionWatcher.swift | Guesses whether text is selected, and reads it when you ask. |
ScreenshotWatcher.swift | Notices new screenshots; captures an area. |
FocusWatcher.swift | Reads the front app, window title and tab address; applies the drift rules. |
Materials.swift | Course folders, extracting page text from PDFs, finding the page of a selected sentence. |
AIEngine.swift | Finds Claude Code inside the Claude app; Codex; the API key. |
Prompts.swift | The questions behind each button and the rules given to the AI. |
AnswerWebView.swift | Renders answers as Markdown with math. |
Config.swift, SessionLog.swift | The settings file and session history. |
DevTools.swift | Self-tests and screen renders. |
site/assets/squat.js | Draws the mascot in 3D with WebGL: the same shader as the app’s. |
site/assets/mascot.js | The website’s mascot: turning toward the pointer, spinning, hopping, changing its face. |
site/assets/demo.js | The website’s demo screen, seven-step tour and mood stage. |
Design sources
Six sources were looked at, and rules were taken from five. The result is summed up on one page in the project’s DESIGN.md.
| Source | What was taken |
|---|---|
| frontend-design from anthropics/skills | Take the visual language from the subject, which is how it became paper, ink and a highlighter. Its list of common looks that give away AI-made design was followed too. |
| ui-ux-pro-max-skill | 120 UX guidelines: the basis for the 14 fixes to the notch screens. |
| awesome-design-md | The format for writing a design system as a single DESIGN.md. No other brand’s design was taken. |
| impeccable | A finishing checklist: contrast, spacing, type, states, and a list of things not to do. |
| vercel-labs/agent-skills | Web interface guidelines: accessibility, focus indicators, motion, reserving image sizes. |
| open-design | Not used: it is a separate design app, with nothing to apply to the code. |
What has been checked, and what hasn’t
Checked
- Building and signing.
- 145 self-tests: drift rules, finding pages in PDFs, reading settings, parsing AI output, positioning the button and windows, island sizes and mascot positions, and study records.
- Renders of every screen state.
- The app launching, with its window on the top row above the menu bar.
- Real answers through the Claude app’s sign-in. A text question took about 2 seconds to its first word, and text inside a screenshot was read too.
- This site’s demo working by clicking, in a headless browser at phone and desktop widths.
Not checked yet
- Clicking the notch and the question window’s buttons with a real mouse.
- Whether the button appears in place above the right-click menu, and whether pressing it opens the window.
- Whether selected text can be read in Preview, Chrome and Safari.
- Whether a screenshot taken during a session is noticed.
- Whether the notch’s motion looks smooth to the eye.
The builder had no way to see or click the screen, so these five need to be tried by the person using it.
What’s left
- Try those five things for real and fix what comes up.
- Bundle the math libraries into the app.
- Edit courses inside the notch instead of in the settings file.
- Settle on the character, the sounds and the name.
- To share it with other people: a developer signature and notarisation, and checking each AI service’s terms.