A fixed top bar names the project, session and repo
A dark bar stays pinned at the top with the project name, the session name and the repository. With logs from several projects open, you can tell the tabs apart at a glance.
Acme Shop · checkout-fixacme/shop
02
Session Name First
The session name leads the tab title and the top bar
When several sessions run on one project, their logs would otherwise look identical. The session name goes first in the browser tab, where titles get cut off last, and is highlighted in the top bar, so you reply to the right one.
checkout-fix· Acme Shop log
billing-bug· Acme Shop log
Same project, two sessions, no mix-ups
03
Did My Reload Land?
A version marker shows you have the newest page
The status bar reads like "v3 · updated Nov 2 · entry 14" and goes up with every republish. After you reload the same link, you can see at once whether the new version arrived.
6 / 9 readv3 · updated Nov 2 · entry 14
6 / 9 readv4 · updated Nov 2 · entry 15
Reloaded: new entry is in
04
Newest on Top
The latest message is always the first thing you see
Messages are listed newest first, each with a number, a title and a status chip such as Your move, Background, Queued or Done. You open the page and the thing that needs you is right there.
14 · Approve the refund flowYour move
13 · Tests runningBackground
12 · Next: email copyQueued
11 · Cart bug fixedDone
05
Headline, Then Detail
One plain sentence first, the specifics underneath
Each message opens with a full-strength summary sentence, with the detail below in quieter text. You can skim the headlines and read deeper only where you need to.
The cart bug is fixed and tested.
06
Facts at a Glance
A short bar of live facts: branch, tests, what's live, what's waiting
Three or four current facts sit near the top: the working branch, whether tests pass, what is live, and what is waiting on you. You get the state of play without reading every message.
branch: fix-carttests: 412 passing
live: v2.3waiting on you: 2
07
How to Get Back Here
The exact command to reopen the page
The page tells you how to reopen it, because you will close the tab: the exact command if your project has an opener script, or the place the project keeps its links. You don't have to dig for the link later.
Reopen this page
$ open-log checkout-fix
08
Easy on the Eyes
A wide page, large text and big buttons and tick boxes
The log uses most of a laptop screen with large body text, and the parts you actually click, the option buttons, note fields and tick boxes, are larger still. It is meant to be read comfortably, not squinted at.
Approve the refund flow?
Yes, ship itWait
2How you reply
09
Tick It Off
A Read this tick per message dims what you've seen
Every message has a Read this tick that dims the card and updates the read count. What you haven't seen yet stands out from what you have.
14 · Approve the refund flow
13 · Tests running
Read1 / 2
10
Questions Up Top
Anything waiting on you sits above the log
Questions and checks for you have their own sections at the top of the page, and log entries never ask. If something has buttons, it is waiting on you.
Waiting on you
Ship todayWait for review
Tests are running
Log entry, no buttons
11
Only the Sections You Need
Waiting on you, Checks for you, Log and Decided
The page has four sections, and each appears only when it has something in it. A quiet session is just a log.
Waiting on you1 question
Checks for younone, hidden
Log3 entries
Decidedfolded
12
Say It in Your Words
A note field on every message, plus an anything-else box
Each message has its own note field, and there is one more box at the end for anything else. Your reply isn't limited to the options offered.
14 · Approve the refund flow
yes, but keep the old email too
13
Close the Tab, Keep Your Place
Ticks and answers are saved in your browser
Your ticks, answers and notes survive a closed tab. They are saved per project and per session, so two logs open at once never overwrite each other.
checkout-fix4 ticks · 2 answers saved
billing-bug1 tick saved
Kept apart, never overwritten
14
What Failure Looks Like
Any command you're asked to run comes with its error text
When a message asks you to run something, it shows what success prints and the most likely failure message. You can tell how it went even if your terminal is hard to read.
Expected: Deployed version 2.4
If it fails: permission denied (missing token)
3Sending it back
15
One Paste Back
Copy my replies puts everything on your clipboard
One button copies plain text with every message marked read or unread, plus your answers and notes. You paste it into chat, which works even when reading the terminal doesn't.
Copied replies open with project, session, repo and time
The copied text starts with a short block naming the project, session, repository, the round of work and when you exported it. The session that receives it can tell straight away whether the reply belongs to it, and an old paste doesn't pass for a fresh one.
WORKING LOG — my replies
project: Acme Shop
session: checkout-fix
repo: acme/shop
exported: Nov 2 14:05
4Keeping it current
17
Same Link, Every Update
Each update goes to the link you already have open
The page is republished to the same link every time, from the same folder, so the tab you keep open just updates. A new link would leave you reading a stale page.
v1→v2→v3same link
18
Decided, Folded Away
Answered questions leave the top at once
As soon as you answer a question, it leaves Waiting on you and becomes one line in Decided, folded at the bottom. Finished log entries go there too, or go entirely. The top of the page is always what still needs you.
14 · Approve the refund flow
12 · Email copy question
Decided · 6 ▸
19
Back on Track After a Reset
After a reset, Claude updates your page instead of starting another
If the conversation is reset mid-task, Claude looks up the log's saved link and updates that page rather than starting a second one you aren't looking at. Each session keeps its own log, so two sessions never overwrite each other's messages.
Session resetlook up saved link
Same page updatedyour tab stays current
20
Tested Before You See It
Every button is clicked and the layout looked at before publishing
Before each publish the page is loaded and clicked through to confirm ticks, answers and the copied text all work, including the session name. Then one real screenshot at laptop and phone width checks that nothing scrolls sideways or squeezes text into a narrow column.
buttons work export has session no sideways scroll
21
Where the Page Goes
A private link, a local file, or your Wi-Fi
Your project picks where review pages go: a private claude.ai link, an HTML file that opens in your browser, or that file served on your home Wi-Fi so a phone can open it. Nothing is ever uploaded or tunneled in the Wi-Fi mode, and the server stops when the review ends.