Skip to main content
Preview the recommended configuration without writing anything:
Apply it explicitly:
The profile is local-first and hardware-aware. It prefers a runnable local backend, keeps symbolic routing first, enables fallback and local memory, and requires previews for risky writes. Missing cloud credentials are handled as a normal fallback condition; setup never creates or copies secrets. Inspect or reset only Arka’s managed configuration:
Environment values and project .env values take precedence over the managed defaults. Existing values are preserved when applying the profile.

​
Share a configuration

Export a portable, safe-to-share bundle:
The bundle includes managed defaults, model/provider preferences, and selected non-secret environment values. API keys, tokens, passwords, cookies, webhook secrets, and other credentials are never exported; they are listed under required_env so the recipient knows what to fill locally. Import is preview-only unless --apply is passed:
Natural language also works: “share my Arka config” routes to a share export.

Related topics

Connecting Gmail and Google Calendar via OAuthLong-term memory with Supermemory syncAutomatic MCP configurationConfiguration, env vars, and API key setupKalshi prediction markets