Local vault (apps/cli): clean-room PRMVLT01 format — Argon2id → XChaCha20-Poly1305, AEAD-bound header, atomic writes. vault:* / secrets:* / inject (primora:// refs) / agent credential broker (dummy tokens in the child, real secret on the wire) / TTL sessions / stack:* operator group. Project vault (backend): core.project_secrets, AES-256-GCM via the platform encryptor. Metadata-only list, audit-logged reveal, and secret://NAME refs resolved at job delivery — refs stored, values never. Surfaces: dashboard Vault page (+ local-vault card under the Tauri shell), desktop vault window via IPC to the primora binary, secrets:* --remote CLI mode, metadata/write-only MCP tools so agents consume secrets via secret:// refs without holding plaintext. Authored By: TDvorak <[email protected]> Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
1.9 KiB
@primora/desktop
Tauri 2 shell around a self-hosted Primora deployment. On first run it asks for the deployment URL; after that the webview renders the same SolidJS console the server serves. Nothing is embedded — no backend, no database. The self-hosted model is preserved.
Prerequisites
- Rust (rustup) and Node.js.
- Linux webview deps:
sudo apt install libwebkit2gtk-4.1-dev libgtk-3-dev libayatana-appindicator3-dev librsvg2-dev
Run
npm run dev --workspace @primora/desktop # dev window (debug build)
npm run bundle --workspace @primora/desktop # release bundles → src-tauri/target/release/bundle
Notes
- Config lives at
~/.config/dev.tdvorak.primora/config.json— one field,server_url. - System tray: Show Primora, Change Server… (clears the URL, back to the connect screen), Quit. Closing the window hides to the tray; a second launch focuses the existing window (single-instance).
- The connect screen only checks that the host answers; if the URL turns out not to be a Primora deployment, use the tray's Change Server.
- macOS blocks plain-HTTP loads to non-localhost hosts (ATS). Use HTTPS, or
http://localhostfor a local deployment.
Secrets Vault
The tray menu's Secrets Vault… opens a local window (ui/vault.html) for
the CLI's encrypted vault — init, timed unlock/lock, list with copy-to-clipboard,
add/delete, .env import. Values are never displayed; copy goes straight to the
clipboard.
The desktop app does not reimplement the vault: IPC commands shell out to the
primora binary on PATH (PRIMORA_CLI overrides the binary path). One vault
file, one crypto implementation — terminal and desktop always agree. Requires
npm i -g @primora/cli; without it the window shows install instructions.
Injection and the credential broker stay CLI-only (primora inject,
primora agent).
- Deep links / push notifications: deliberately omitted — nothing needs them yet.