The Virlow blog
Notes on working with your notes.
Practical notes on privacy, AI workflows, and note-taking.
Virlow for Codex: memory that carries from one session to the next
The Virlow plugin for OpenAI Codex sets up the local connector and adds five small hooks. Codex checks what a project already knows at the start of a task, and is reminded once to save what is worth keeping.
Use Claude with your Virlow notes: a practical walkthrough
Connect Claude to Virlow, try a small project-summary exercise, check each decision against its source note, and close access when you finish.
What to let an AI assistant remember about your work
A memory is a fact an assistant will read back in a later session, in a context you did not plan. Decide what earns that status, keep secrets and unfinished work out, and review what was written.
What the name Virlow stands for
Vir, for a virtual workspace that is yours. Low, for flow, and for keeping a low profile: your notes are encrypted on your device before they reach our servers.
Link notes instead of copying them
When the same fact lives in several notes, one of them goes stale. Give each fact one home, link to it from everywhere else, and read the backlinks before you change it.
Write project notes your future self can use
A project-note template for recording what was decided, why it changed, who owns the next step, and which questions are still open.
What happens to your private notes when you connect an AI assistant?
Encryption protects stored notes. Connecting an assistant introduces another boundary: who can read the content returned by its tools.
A weekly note review: keep, act, or archive
Review an existing collection of notes: keep useful reference, give unfinished work a next action, and move outdated material out of the active pile.