Watch your code explain itself.

One change at a time, in the right order, with the right reasons. It is the difference between reading a wall of code and watching a YouTube tutorial of the work that just happened.

Walkthrough 3 changes Playlist Close

session.ts src/auth

export async function revoke(sid) { await cookies.clear(sid) }

export async function revoke(sid) { await cookies.clear(sid) // The cookie outlives the token, await tokens.revoke(sid) }

refreshToken.ts src/auth

async function rotate(token) { const fam = await tokens.get(sid) // A live family is honoured. return mint(fam)

async function rotate(token) { const fam = await tokens.get(sid) if (!fam || fam.revokedAt) { throw new Revoked(sid) }

session.test.ts src/auth

it('refuses a dead token', async () => { const old = await login() await revokeSession(sid) await expect(rotate(old)) .rejects.toThrow()

Playing Paused That’s everything. Esc to stop 1×

Code review made easy

Spot something wrong when the AI was explaining the code? Drop a comment and claude will take it from there. Your comments sits on the diff itself, not three scrolls up the chat.

codeio Sessions drop after deploy working

Walkthrough 3 changes Comment 1 2 Close

TS session.ts auth/session.ts

41 export async function revokeSession(sid: string): Promise<void> { 41 export async function revokeSession(sid: string): Promise<void> {

42 await cookies.clear(sid) 42 await cookies.clear(sid)

43 await tokens.revokeFamily(sid)

43 } 44 }

Your note What should change here? Clear the family from the in-memory cache too. Cancel Add ⌘↵

TS refreshToken.ts auth/refreshToken.ts

57 const family = await tokens.family(token.sid) 57 const family = await tokens.family(token.sid)

58 if (!family || family.revokedAt) {

59 throw new TokenRevokedError(token.sid)

60 }

58 return mint(family) 61 return mint(family)

Your note What should change here? Map this to a 401 — the client should re-auth, not error. Cancel Add ⌘↵

TS session.test.ts test/auth/session.test.ts

45 }) 45 })

46 it('revokeSession clears the token family', async () => {

47 const sid = await mint()

48 await revokeSession(sid)

49 await expect(rotate(tokenFor(sid))).rejects.toThrow(TokenRevokedError)

50 })

Submit review 2

Overall comment optional What you make of these changes as a whole. Right approach. Two small things, then it’s good to go. Line notes

TS session.ts Clear the family from the in-memory cache too.

TS refreshToken.ts Map this to a 401 — the client should re-auth, not error.

Discard Submit review ⌘↵

Sessions are dropping a few days after every deploy. Can you find out why?

Grep revokeSession|refreshToken

Read auth/session.ts

Read auth/refreshToken.ts

Found it — and it isn’t the deploy. revokeSession() clears the cookie, but it never touches the token store, so auth/refreshToken.ts goes on serving the old refresh token until it expires by itself.

That’s up to fourteen days, which is why it reads as a deploy problem: the deploy is only what rotates the pods and drops the in-memory cache that was hiding it.

Edit auth/session.ts +6 −1

I’ve moved the revocation into revokeSession() itself and made it idempotent, so a double logout can’t throw.

auth/session.ts ts

export async function revokeSession(sid: string): Promise<void> {
  await cookies.clear(sid)

  // The half that was missing: the token store outlives the cookie,
  // so the family has to die here or it does not die at all.
  await tokens.revokeFamily(sid)
}

Edit auth/refreshToken.ts +4 −1

The refresh path was the accomplice, so auth/refreshToken.ts now refuses a revoked family instead of quietly minting from it.

Edit test/auth/session.test.ts +7 −0

And there’s a test pinning it down: log out, replay the old refresh token, expect a refusal.

One caveat: this only helps sessions minted after it ships. The ones already out there still have to age out.

Walk me through it Summarize · 3 files changed

Review: overall comment + 2 comments

Read auth/refreshToken.ts

Edit auth/refreshToken.ts +2 −1

Edit auth/session.ts +1 −0

Kill the token family on logout TS session.ts 1 of 3

0:02 0:05 0:09 0:14

Playing Esc to close 1×

Press / to type

Opus 5 Thinking

Stop reading. Start listening.

Reading every answer is exhausting. With Codeio, the answers go to your ears, not eyes. Give it one afternoon and scrolling a wall of text feels like something you used to do.

Click a sentence to hear it
←→ step a sentence

codeio Sessions drop after deployOpus 5 · 38%

Sessions are dropping a few days after every deploy. Can you find out why?

GreprevokeSession|refreshToken

Readauth/session.ts

Readauth/refreshToken.ts

Found it — and it isn’t the deploy. revokeSession() clears the cookie, but it never touches the token store, so auth/refreshToken.ts goes on serving the old refresh token until it expires by itself.

That’s up to fourteen days, which is why it reads as a deploy problem: the deploy is only what rotates the pods and drops the in-memory cache that was hiding it.

Editauth/session.ts+6−1

I’ve moved the revocation into revokeSession() itself and made it idempotent, so a double logout can’t throw.

auth/session.tsts

export async function revokeSession(sid: string): Promise<void> {
  await cookies.clear(sid)

  // The half that was missing: the token store outlives the cookie,
  // so the family has to die here or it does not die at all.
  await tokens.revokeFamily(sid)
}

Editauth/refreshToken.ts+4−1

The refresh path was the accomplice, so auth/refreshToken.ts now refuses a revoked family instead of quietly minting from it.

Edittest/auth/session.test.ts+7−0

And there’s a test pinning it down: log out, replay the old refresh token, expect a refusal.

One caveat: this only helps sessions minted after it ships. The ones already out there, like a3f9c1e8-7b42-4d15-9e33-0c8f7a2b6d41, still have to age out.

Ready

Review the plan,
not just the code.

Highlight the line that is wrong, say what you want instead, press Refine — and the code you were dreading never gets written at all.

Plan revising… Select any text to comment

Port the SCM panel to the new tree

Swap the panel’s two hand-rolled lists for the tree component, keeping the staged / changes split as two roots. The rows already carry name, path and status — the tree needs nothing more. Add a comment… One flat list — staged just sorts to the top. Cancel Comment

Add a flat row adapter in scm/rows.ts.
Render ChangeTree with group headers above each root. Add a comment… No headers — badge the rows instead. Cancel Comment
Move the A / M / D badges into the row template — the tree virtualises, so an overlay would detach on scroll.
Wire the empty state: a clean working tree shows the tree’s own placeholder line.
Delete the old list component.

The keyboard map stays: the tree already takes ↑ ↓ and Enter, and the panel’s ⌘↵ commit shortcut never belonged to the list.

Out of scope: the commit box and the push / pull row stay exactly as they are — this is the list’s replacement, not the panel’s.

Ready to build Refine the plan 1 note 2 notes Refine plan Build

Port the SCM panel to the new tree

Port the Source Control panel over to the new tree component.

Read scm/SourceControlPanel.vue

Edit scm/SourceControlPanel.vue

Edit scm/ChangeTree.vue

Bash npm test -- scm

The panel is on the new tree. The old grouping headings had nowhere to live once the tree started handing back a flat list, so staged files sort to the top instead and keep their own divider.

Everything else came over unchanged — the context menu, the discard confirm, and the keyboard order. The panel tests pass.

Walk me through it Summarize 3 files changed

Press / to type

Opus 4.6 High Accept edits

It tells you
when it is done.

Claude can take minutes to finish. If you have walked away from the screen, sound is the only way it can reach you.

Working
Waiting for your answer
Finished while you were away
Ended in an error

It is a full IDE

Codeio has the whole workspace built into it, so you never miss your code.

Transcript keep-awake.ts verbalize.ts


                
                
                
                  1
                
                function apply(): void {
                
                
              
                
                
                
                  2
                
                  hold(forWork, working && getSettings().keepAwake, 'prevent-display-sleep')
                
                
              
                
                
                
                  3
                
                  // No setting consulted, deliberately. See the note above.
                
                
              
                
                
                
                  4
                
                  hold(forVoice, announcing, 'prevent-app-suspension')
                
                
              
                
                
                
                  5
                
                }
                
                
              
                
                
                
                  6
                
                /** The first turn started, or the last one ended. */
                
                
              
                
                
                
                  7
                
                export function setWorking(next: boolean): void {
                
                
              
                
                
                
                  8
                
                  working = next
                
                
              
                
                
                
                  9
                
                  apply()
                
                You, just now · uncommitted
              
                
                
                
                  
                      1098
                    
                
                }
                
                
              
                
                
                
                  
                      11109
                    
                
                /** The voice took the floor, or the queue drained. */
                
                
              
                
                
                
                  
                      121110
                    
                
                export function setAnnouncing(next: boolean): void {
                
                
              
                
                
                
                  
                      131211
                    
                
                  announcing = next
                
                
              
                
                
                
                  
                      141312
                    
                
                  apply()
                
                
              
                
                
                
                  
                      151413
                    
                
                }
                
                
              
                
                
                
                  
                      161514
                    
                
                /** Shutting down. Drop both holds; nothing here outlives the app. */
                
                
              
                
                
                
                  
                      171615
                    
                
                export function dispose(): void {
                
                
              
                
                
                
                  
                      181716
                    
                
                  working = false
                
                
              
                
                
                
                  
                      191817
                    
                
                  announcing = false
                
                
              
                
                
                
                  
                      201918
                    
                
                  apply()
                
                
              
                
                
                
                  
                      212019
                    
                
                }

Playing “…so a turn you walk away from does not die with the machine.”

Problems Output Terminal

~/codeio $ npm test
  ✓  holds the display only while a turn runs
  ✓  holds the system for as long as the voice speaks
  28 passing (412ms)
~/codeio $

The same shortcuts
you already use.

The editor keeps VS Code’s bindings rather than inventing a dialect, and the voice is driven the same way. There is nothing new to learn to move over.

The editor

⌘P: Open any file by name
⌘⇧F: Search the project
⌘S: Save
⌘J: Terminal
⌘1–9: Jump to a tab

The voice

⌘T: Hold to talk
Space: Play or pause
←→: Back or forward a sentence
⇧,.: Speak slower or faster
Esc: Stop talking

These are the ten you will use most. There are plenty more available.

The voice runs on
your own computer.

Both models come inside the app. There is no voice service to sign up for and nothing to download later. The voice works the first time you open it, even with no internet.

your computer

Kokoro 82M Speaks the answers ~90 MB
Whisper base.en Hears what you say ~76 MB
codeio.db Every chat, on your disk SQLite

Both models are in the download. The app is not allowed to fetch one while it runs.

what you type
the code Claude reads

Anthropic

Claude Code still does the thinking, so what you type and the code it reads go to Anthropic — exactly as they do when you run claude in a terminal. Codeio only changes how the answer comes back. Full details

No new subscription.
No sign-up.

Codeio runs on the Claude Code you already pay for. Nothing else to buy, paste, or set up.

A second subscription It runs on the Claude Code plan you already pay Anthropic for.
An API key Codeio never asks for one, and never handles billing.
An account with us There is no Codeio server for one to live on.
Models to download The voice and transcription models are already inside the app.

A working claude command If that runs in your terminal, you are ready. How to check

Put your headphones on and get back to work.

Codeio is in beta. macOS first, then Windows and Linux.

Get Codeio

Free while it is in beta · Uses the Claude Code login you already have

The IDE that talks back.

Working

Waiting for your answer

Finished while you were away

Ended in an error

Put your headphones on and get back to work.