Sesame[ github ]

Sesame. Secrets live on the key. Your Mac keeps only the map.

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.

01

The idea

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.

  1. 01 mapnames and locations only, never values
  2. 02 approveyou choose what goes to the key
  3. 03 sealeach value is copied to the key and verified; you remove the original when ready
  4. 04 releasekey plugged in, a project asks: PIN + fresh fingerprint, straight into that process, then cleared

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.

02

Simulation

The full flow, step by step, on synthetic data. Nothing on your machine is read.

Synthetic hardware simulation · not deployed

Sesame Agent · macOS

Simulation only · biometric v2

Step 1 of 7 · Key disconnected

IdleIdle. Simulated Sesame Key disconnected. Nothing has been read.

  • Chrome passwordsWaiting

    Passwords & browser credentials · designed import flow

  • macOS KeychainWaiting

    Selected macOS items · scoped access

  • 1PasswordWaiting

    Selected vault items · designed flow

  • .env filesWaiting

    Variables in selected project folders · first native connector

8 demo candidates · 8 shown for approval

03

Where things live

on the key

  • encrypted secret values
  • on-device policy material
  • proposed matcher · no host biometric material

the only place a value rests

on the mac

  • labels and opaque IDs
  • routes, schedules, allow-lists
  • audit events

no secret values at rest

in the cloud (opt-in)

  • counts, if you enable sync
  • workflow state

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.

04

Mac app

A Swift menu-bar app and CLI run the same nine-step flow natively.

$ ./scripts/run-native-demo.sh

  1. 01scan synthetic metadata
  2. 02record explicit approval
  3. 03connect the simulated key
  4. 04confirm synthetic enrollment-present
  5. 05acknowledge the simulated PIN step
  6. 06request a simulated fresh fingerprint
  7. 07choose a synthetic match result
  8. 08store and verify in memory
  9. 09release, then clear

menu-bar app

./scripts/run-native-demo.sh --menu

deterministic cli

./scripts/run-native-demo.sh

Four 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 ]
05

Scheduled checks

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

Scan cadence
Scan cadence

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.

06

What leaves the Mac

optional · off by default

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

  1. 01

    Validate

    Reject unknown fields and anything outside the closed metadata DTO.

    Counts + opaque ref + UTC day

  2. 02

    Compare

    Derive protected, residue, and total counts from the same snapshot.

    Deterministic posture state

  3. 03

    Recommend

    Emit bounded recommendation codes with affected counts, never free-form data.

    Closed action codes

  4. 04

    Persist result

    Return one report. Render retains task inputs and results for 30 days.

    One retained report

Never sent

  • Secret values
  • Usernames and domains
  • Paths and file contents
  • PINs and biometrics
  • Hashes and hardware key material
Where the report goes: retention and retries

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.

Root validation
0 retries
Pure child work
Up to 3 retries
Repeat DTO
Same report
Separate request
Separate retained run
08

What is real today, stated plainly

  • working
  • source-tested · not shipped
  • simulated
  • planned · unavailable
  • working demo · synthetic onlyBrowser product journeyThe interactive scan, approval, factor, transfer, receipt, and release states run with fixed synthetic metadata. The browser never reads a source or credential value.
  • working demo · synthetic onlyNative macOS presenterThe menu app and CLI run a Swift coordinator against compile-time synthetic bytes and a volatile in-process adapter. They do not open sources, spawn a release target, or contact hardware.
  • source-tested · not shippedLocal agent, connectors, and schedulerNative modules cover explicit source selection, metadata discovery, scheduling, approval, import, release, and audit boundaries in tests. They are not a signed, installed, end-to-end product.
  • source-tested · default offRender posture workflowThe workflow and native client accept only a closed count/status DTO. No production route enables submission, and this site replays a fixed synthetic report without a network request.
  • planned · unavailableSigned macOS applicationThere is no downloadable, signed, notarized, installed Sesame app and no signed multiprocess or OS-permission evidence yet.
  • planned · unavailablePhysical Sesame KeyNo physical key, secure element, flash vault, USB-C/NFC transport, PIN verifier, fingerprint sensor, or physical security evidence exists yet.
  • planned · unavailableAutoFill, Credential Exchange, and Chrome bridgeThese consumer-facing OS/browser integrations are not complete or enabled. Default-off protocol code does not make a usable product surface; the browser demo never fills, reads, or delivers a value.

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.