FILES, NEVER CREDENTIALS.
The vault carries context — memory, tasks, sessions. Every machine keeps its own login. No token, no key, no session ever crosses.
EVERYONE CALLS ME IZZY.
I SHIP THINGS FOR A LIVING.
SCROLL.
I MAKE THINGS.
Things, plural — that’s the maker. Right now I’m making one thing, and this page is about it. Keep scrolling.
I’VE SHIPPED STORES, SITES, TOOLS — THEY PAY FOR THIS ONE. NO VC. THEY’RE OFF THIS PAGE ON PURPOSE.
The always-on-context console for Claude Code.
You run Claude Code on more than one computer. Every time you switch chairs, it forgets you — the project, the decisions, the half-done tasks. AWAKE keeps that context alive: memory, tasks, and session history that follow the repo to any machine, over storage you already own.
WE SYNC YOUR FILES, NEVER YOUR CREDENTIALS.
CONTINUITY, NOT QUOTA ROTATION.
Not released. Being built right now — every chip on this page is the real status.
WANT IT WHEN IT’S REAL? SAY SO.The vault carries context — memory, tasks, sessions. Every machine keeps its own login. No token, no key, no session ever crosses.
Your files follow you. Your logins don’t. Nothing here juggles accounts or games limits — that’s the point of the first line.
The vault rides git, Drive, or Dropbox — storage you already have. The console runs local. No AWAKE cloud, no server reading your files, nothing to trust but your own disk.
People are asking for this in public. The top open issue on the Claude Code repo — “Portable project memory across machines” — sits at 33 reactions at last count (July 2026). People keep asking; nobody’s shipped it. Until then —
READ ISSUE #25739 DEMAND: CHECKABLEDAY 4 — CROSS-MACHINE HANDOFF PROVEN IN THE EXIT TEST. ADOPTED A PROJECT ON MACHINE A, CLONED IT TO A DIFFERENT PATH ON MACHINE B, SAME IDENTITY RESOLVED, CONTEXT INJECTED. 371/371 TESTS GREEN.
The repo is private, so that number is my word, not your receipt. That’s why this is a diary and not a benchmark. When there’s something public to check, it moves up a section.
BUILD LOG: MY WORD