For Claude CodeWorks with the setup you already have

Working memory for Claude Code.

WORKINONIT wraps Claude Code. It knows which client and project every folder belongs to, and it works out from your sessions what's done and what's left. Claude gets all of it before you type your first prompt.

macOS · runs on your Mac · no server to manage

127.0.0.1:7337
NowDiaryMastersInboxSearch /
Monday, November 17 · MacBook

You're working on Rossi Studio site.

● active session1h 07 this week

Rossi Studio site

Rossi Studio · ~/Clients/Rossi/site · 6 min ago
NextMerge the menu branch and deploy to Lightsail.
Waiting onNew photos from the client, due Friday.
Resume in ClaudeFolderDetails
hours with Claude · 7 days3 masters
22h09min
Macs2 online
  • MacBookthis one
  • Office Mac mini2 unpushed commits
  • iMac3 h ago
Urgent4
  • Renew the domain by Nov 30Rossi Studio
  • Ship the builds to TestFlightBrand Nova
  • Winter prices in the catalogAlpi Shop
≈ 100 tokensof context at every start, however big your archive gets
0 agentsto write or maintain: Claude Code stays as it is
20 minutesafter a session ends, the handoff is already written
Every Macin sync through iCloud, with no server
The problem

Every Claude session starts from zero.

Claude Code is brilliant inside a session. Between sessions it remembers nothing: which client you're working for, what you decided yesterday, what you left half-done on the other Mac.

> ok so this is the Rossi Studio site, hosting is on Lightsail, yesterday we did the menu, the client wants…

You re-explain everything, every time

Every session opens with you rebuilding the context by hand. Whatever you forget to mention, Claude doesn't know.

agent-rossi-site.md
agent-nova-app.md
agent-alpi-shop.md
last edited: 3 months ago

Custom agents go stale

One prompt per client and per kind of work turns into a matrix to maintain. The corrections you make in a session never make it back in.

searching "hosting" in 2,340 notes…
opening 14 files…
reading 38,000 tokens to answer

A second brain costs you on every question

A notes vault read by the agent has to be explored every time, by the most expensive model. The bigger it gets, the more it costs, and it can't tell what's still true.

How it works

Put the specialization in the place, not the agent.

The model and its tools stay generic. WORKINONIT ties instructions and memory to the scope you're in (client, project, folder), and it finds that scope from the folder where you open Claude.

From the traces of your work
›_Claude Code sessionstranscripts, files touched, commands
⎇git and GitHubbranches, commits, unpushed changes
✎Explicit notesfrom Claude, the CLI, your phone
▤File systemwhich project each folder belongs to
workinonit
  1. Derivescans transcripts and repositories, without you writing anything
  2. Consolidatea small model summarizes every session and types the notes
  3. Injectwhen Claude starts, it passes only that scope's context
master → project → placelocal SQLiteiCloud sync
Inside Claude Code
$ claude hook SessionStart ↓ Rossi Studio › Site Next: merge and deploy - [urgent] domain by Nov 30 - [decision] hosting on Lightsail - [fact] only replies on WhatsApp
1 · Derive

Memory writes itself

Most of the memory nobody writes. It comes from your sessions, from git and from GitHub. You just work.

2 · Consolidate

Pay the cost once

When a session stops, Haiku summarizes it in four lines. One small call, made once, instead of a search on every question.

3 · Inject

Claude starts up to speed

A Claude Code hook resolves the scope from the folder and passes the brief. No semantic search: the folder is the query.

Features

Everything Claude should know, right when it matters.

Every folder knows who it belongs to.

You organize your work into masters (a client, an agency, a product line) and projects. One project can live across many folders, repos, sites and servers.

  • A folder resolves by longest path prefix, deterministically.
  • A master's notes apply to all of its projects. Other clients never see them.
  • If a folder belongs to no master, Claude asks you once and links it.
~/Clients/Rossi/site/src→Rossi Studio › Site
~/Clients/Rossi/brand→Rossi Studio › Brand
~/dev/nova-app→Brand Nova › App
server: shop.alpi.it→Alpi Shop › Shop
~/Downloads/test→no master · asks where it goes
Rossi Studio [fact] only replies on WhatsApp
├─ Site ~/Clients/Rossi/site · github rossi/site · rossistudio.com
└─ Brand ~/Clients/Rossi/brand

The handoff writes itself.

Twenty minutes after a session stops, Haiku reads the transcript and writes the handoff: where you are, what you did, what's next, what you're waiting on. The next session, on any Mac, picks up from there.

  • It runs isolated: no hooks, no ghost sessions.
  • Each handoff replaces the last one, so the context stays short.
  • On first run it rebuilds the history of every project.
  1. 10:02“fix the menu on mobile”
  2. 10:09Edit header.css, nav.js
  3. 10:21git commit -m "mobile menu"
  4. 10:24“the new photos arrive Friday”
20 min idle
handoff · Rossi Studio sitewritten by haiku · 10:44
State
Mobile menu done on menu, not in main yet.
Done
Rewrote header.css and nav.js, commit 3f2a1c.
Next
Merge and deploy.
Waiting on
New photos from the client, Friday.

Notes with a type and a natural expiry.

An open todo, a decision you made and a note from six months ago shouldn't weigh the same. Every note has a type, and the type decides how long it stays in context.

  • todo leaves once it's done. Urgent ones stay on top everywhere.
  • decision and fact stay: Claude won't reopen what you've already settled.
  • lesson (coming soon) will carry over to similar projects too.
urgentRenew the domain by Nov 30stays on top
decisionHosting stays on Lightsailpermanent
factOnly replies on WhatsAppmasterpermanent
lessonWeb images always in WebPcoming soon
todoPlaceholder photos in /aboutdone · out of context

Three Macs, one memory, no server.

Each Mac keeps its own local database and writes only to its own folder in iCloud. It reads everyone else's and rebuilds the state. If you left unpushed work somewhere else, the brief tells you before you touch the project.

  • Append-only event log, last-write-wins: no locks, no conflicts.
  • Which Macs are online, what's in progress, what isn't pushed.
  • The shared code means every Mac runs the same version.
MacBooksync/air/
working on Rossi site
Mac minisync/mini/
idle for 2 h
iMacsync/imac/
offline
iCloud · each Mac writes its own folder, reads all the others
⚠
on Mac mini: 2 unpushed commits in Rossi site
pull/push before touching the project

Corrections become rules. coming soon

workinonit learn will reread a project's sessions and find the moments you corrected Claude: rejected requests, reverted edits, redone operations. Each correction will become a lesson in the context.

  • It will get better the more you use it, without rewriting prompts.
  • Pipelines already make a proven method portable: record it once, run it in any master. How they work
session, Nov 4“No, images go in WebP, not PNG.”
↓ workinonit learn
correction foundmistake: exported PNG · rule: web images always in WebP
↓ from the next session on
brief for Rossi site and similar sites[lesson] Web images always in WebP
Dashboard

All your work, on one local page.

The dashboard runs on your Mac. It shows where you left every project, what's urgent and what changed on your other Macs.

Diary

What you did yesterday or last week, by master and by project, with real active minutes. Breaks over 10 minutes don't count.

tuewedthufrisatsunmon

Notes from your phone

Dictate a voice note and it shows up transcribed in the Inbox, ready to assign to a project.

“call Alpi about prices”2 min
“light version of the Nova logo”1 h

Search everything

One query on the local database, across every master.

/ logo
Rossipalette approved Nov 12
Novalight version of the logo

Masters at a glance

Every client with its projects, how recent they are and what's still open.

Rossi Nova Alpi

Flat cost

Startup context doesn't grow with your archive: Claude reads only the brief for the current scope.

≈ 100tokens per session, with 10 notes or 10,000
Compare

Why not an agent, or a second brain.

WORKINONITCustom agentsSecond brain read by the agentBuilt-in memory
SetupNone: context grows from your workOne prompt per client and taskConstant writing disciplineNone
Knows which project a piece of information belongs toYes, from the folderOnly if it's in the promptOnly if you search wellNo
Startup cost≈ 100 tokens, flatFixed, often highGrows with the vaultVaries
Tells open from closedYes: types and lifecycleNoNoNo
Learns from correctionsComing soon, with learnOnly if you rewrite the promptNoPartly
Multiple machinesYes, with warnings on unpushed workDependsWith vault syncTied to the account
Under the hood

Local, readable, yours.

Data on your Mac

SQLite database in ~/.workinonit. No account, no third-party cloud.

Open formats

The catalog is masters.json, notes are a .jsonl log. You can read them and version them.

No new model

Summaries go through your own Claude Code, with Haiku. Memory lives outside the model: switch models and you lose nothing.

Adds to, doesn't replace

A SessionStart hook, a skill and a CLI. Claude Code stays the tool you know.

FAQ

Questions

What is it, exactly?

A layer between you and Claude Code. It catalogs your clients and projects, derives memory from your sessions and from git, and hands it to Claude when you open a session. It's not another assistant: it's the context the one you already use was missing.

Do I have to change how I work?

No. Open Claude in the project folder like you do today. The one rule is that every project lives inside a master: when you open an unknown folder, Claude asks you once where it goes.

How many tokens does it cost?

The starting brief is about 100 tokens. Haiku writes the session summaries, once per session, in the background. Your main model never acts as a search engine over the archive.

Where does my data go?

It stays on your Mac, in a local database. If you use several Macs, they sync through your own iCloud. There's no WORKINONIT server.

Does it work on Windows or with other models?

Today WORKINONIT is for Claude Code on macOS. Memory lives outside the model, so the format isn't tied to any vendor.

Early accessLimited spots

Your AI. Just less stupid.

WORKINONIT runs every day across dozens of real projects. Write to us and we'll help you set it up on your own work.