Validate
Reject unknown fields and anything outside the closed metadata DTO.
Counts + opaque ref + UTC day
A research prototype built on one assumption: as hacking tools get cheaper, personal computers will be compromised more often. So the secrets belong on a separate hardware key you plug in, not on the computer.
sesame :: research prototype :: key not built
Work in progress. This browser prototype models the journey with fixed synthetic data. It reads no source or credential value.
Attacking a personal computer is getting cheaper. AI tools already help find vulnerabilities, write exploits, and sift a stolen disk for credentials. It is reasonable to plan for a laptop being compromised at some point, and to ask what is on it when that happens.
Today that is usually everything: Chrome’s password store, the macOS Keychain, a password manager, and API keys in .env files across old projects. Plaintext env files are readable by any script or agent with file access; the rest are often one export or permission prompt away.
Sesame tests a different split. The computer keeps only a map: labels, locations, opaque IDs. The values live on a separate hardware key with its own encrypted storage. Each value is copied to the key and verified first; removing the original is a separate step you approve, never something Sesame does silently.
With the key plugged in, when a project needs a secret (say npm run dev asking for an API key), Sesame hands that one value straight into that process after a PIN and a fresh fingerprint. No copy-paste, no .env left behind.
This narrows what a compromise can take. It does not make a compromised machine safe: a value in use still sits in that process’s memory.
Illustration of the proposed design with synthetic names. The key has not been built.
In this browser demo no source is opened and no credential value exists.
The full flow, step by step, on synthetic data. Nothing on your machine is read.
Sesame Agent · macOS
Simulation only · biometric v2Step 1 of 7 · Key disconnected
IdleIdle. Simulated Sesame Key disconnected. Nothing has been read.
Passwords & browser credentials · designed import flow
Selected macOS items · scoped access
Selected vault items · designed flow
Variables in selected project folders · first native connector
8 demo candidates · 8 shown for approval
the only place a value rests
no secret values at rest
never values, usernames, domains, paths, hashes, biometrics or key material
limit: an approved credential is necessarily present, transiently, in the authorised process’s memory while it is in use. The production design minimizes and clears that exposure best-effort. It cannot protect a value from a fully compromised host during an authorised release, and this prototype does not claim otherwise.
A Swift menu-bar app and CLI run the same nine-step flow natively.
$ ./scripts/run-native-demo.sh
menu-bar app
./scripts/run-native-demo.sh --menudeterministic cli
./scripts/run-native-demo.shFour compile-time synthetic records; buffers cleared after the simulated release. The app never opens Chrome, Keychain, 1Password, project files, or a physical device. It reads no sensor and creates no biometric sample, template, score, or stable identifier. Its result is not identity, intent, liveness, spoof-resistance, or deployed-hardware evidence.
[ view source ]Scheduling modules are source-tested, but no signed app is installed here. This control only models cadence and approval; it starts no background scan and reads no source or sensor.
checkdiscover changesaskrequire the keycopy + verifyleave original
This prototype is set to model about 4 times a month. It schedules no real scan; a future product must hold every change for approval.
Only counts and a status ever leave the Mac, never values. If you turn this report on, the hosted workflow (Render) keeps each one for 30 days.
Render Workflow · synthetic replay
Stage 4 of 4: Persist result
Reject unknown fields and anything outside the closed metadata DTO.
Counts + opaque ref + UTC day
Derive protected, residue, and total counts from the same snapshot.
Deterministic posture state
Emit bounded recommendation codes with affected counts, never free-form data.
Closed action codes
Return one report. Render retains task inputs and results for 30 days.
One retained report
Never sent
Retention boundary
Render receives the root input before validation. It retains every task input and returned result for 30 days. Sesame does not claim early deletion or permanent storage. An independently authorized Render caller is outside this client boundary and could submit invalid data that Render still retains.
Pre-existing work disclosure. A separate, earlier project by the team established the names-only discovery and scoped-read patterns that Sesame’s connector design borrows from. That work predates this build, is not part of this submission, and its trusted helper binary is untouched here.
Source-tested means repository tests passed for that boundary. It does not mean a signed, installed, independently assessed, or physically verified product exists.