Security & privacy

Lumen runs on your Mac. Your code, memory and threads stay there; the only thing that leaves is what a model needs to do its job, sent to the provider you chose.

What stays on your machine

• Your folders and their history.
• Every thread, handoff and memory entry, under .lumen/ in the workspace.
• API keys, in the macOS Keychain.

What leaves it

When a crew member works, Lumen sends that member's context to its provider's API: the task, the relevant files and its own memory. Nothing is sent to Lumen's servers. Each provider handles the data under its own API terms.

Human in the loop

Models stream live updates back to you. Risky actions wait for approval, and every decision is written to a log you can read. See Review & approve.

Access control

Each member sees only the folders it's given and can only do what permissions allow. Files in .lumenignore are never sent anywhere.

Sandboxing soon

We're adding isolation in lightweight micro-VMs, so every model's commands run in their own contained environment.