Run Your App with Secrets

The most common workflow. Map a directory to your workspace once (in the desktop app), then use lol run every time you start your app:

# Start your app with secrets injected
$ cd ~/code/my-api
$ lol run -- npm run dev
lol: injecting 5 env vars into process

Your app receives all project keys for the mapped environment as environment variables. No .env file required.

Switching Environments

Test against staging or production configs without changing any files:

$ lol run --env staging -- npm run test:integration
$ lol run --env production -- npm run build

Pre-Flight Check Before Deploying

Before a deploy or handoff, run lol doctor to verify everything is in order:

$ lol doctor
  app reachable    ok  localWiki v0.4.2
  vault unlocked   ok  ready
  directory mapped ok  ~/code/my-api -> my-team
  secrets available ok  5 secrets
  no conflicts     ok  injection would succeed

If any check fails, doctor tells you what is wrong. Common fixes:

• App not reachable — start the localWiki desktop app.
• Vault locked — unlock the vault in the desktop app.
• Directory not mapped — add a directory mapping in the Project Keys panel.
• Unresolved conflicts — resolve them in the desktop app.

Check Connection Status

Quickly verify the CLI can talk to the desktop app:

$ lol ping

Or get more detail about the current workspace mapping:

$ lol status

List Available Keys

See which keys would be injected for the current directory:

$ lol list

Use --json for machine-readable output:

$ lol list --json

Override Workspace or Directory

If you need to inject keys from a different workspace or pretend you are in a different directory:

$ lol run --workspace other-team -- npm start
$ lol run --dir /path/to/other/project -- cargo run