Arcane.environment

This focused page is derived from the mechanically checked full member inventory.

Syntax

Arcane.environment

Member kind

Namespace

Description

App-authorized native environment-profile operations.

Overview

Arcane.environment manages the Vault application's authorized environment profile. It separates listing, protected reads, writes, and deletion, and marks known sensitive names as protected by default when set() is called without an explicit protection choice.

Availability and security

The namespace is restricted to app id vault on Core or Android hosts. Listing requires environment.read, protected reads require environment.protected.read, and mutations require environment.write and an exclusive mutation boundary. Never print protected values in examples or logs.

Example

const access = await globalThis.Arcane.capabilities.list();
const canListEnvironmentNames = access.methods.includes('environment.list');

console.log('Environment inventory admitted:', canListEnvironmentNames);

Members

• Arcane.environment.list() — Lists the native Arcane environment profile. Ordinary values are returned; protected values are exactly •••••. Requires environment.read and explicit application admission.
• Arcane.environment.get() — Gets one configured entry. This is the deliberate plaintext-reveal operation: a protected entry's real value crosses the native bridge to the authorized renderer. Requires the separate environment.protected.read capability.
• Arcane.environment.set() — Creates or replaces a desktop user-scoped or Android app-scoped entry. Android rejects PATH; the SDK defaults sensitive-looking names to protected storage, and the returned protected value remains •••••. Requires environment.write and explicit application admission.
• Arcane.environment.remove() — Deletes one configured entry. Requires environment.write and explicit application admission.

Reference group

Namespace, constructor, and values