Profiles and Configuration
Keep terminal and agent connections separate.
Use a Named CLI Profile
namera login --profile work --device-name "Work laptop"
namera wallet list --profile workPass the name on each command. Ordinary CLI commands default to personal;
logging in to work does not change the command flag's default.
For a development server:
namera login --profile dev --host http://localhost:8080
namera wallet list --profile devLogin saves the server origin with that profile. Ordinary commands do not have
a --host flag; use the saved connection or API-key environment configuration.
Understand Host Selection
| Operation | API origin |
|---|---|
| Ordinary command with an API key | NAMERA_API_URL, then https://api.namera.ai |
| Ordinary command with OAuth | Saved CLI profile |
login | --host, defaulting to https://api.namera.ai |
session-key import | --host, then NAMERA_API_URL, then saved CLI profile |
| MCP commands | --host, defaulting to https://api.namera.ai |
Before the first personal login, import defaults to the production API.
For a new custom profile, provide --host when importing.
Keep MCP Profiles Separate
namera mcp login --profile codex
namera mcp status --profile codexOK MCP connected to Namera
-> Profile: codex
-> Server: https://api.namera.ai
Permissions
-> View wallets, session keys, and transaction history
-> Send transactions and sign with authorized session keys
-> Stay connectedMCP defaults to default, not personal. Its profile and API origin together
identify a connection. Use the same values when serving, signing in, checking
status, and signing out.
Storage
Nonsecret profile configuration lives in config.json under:
| System | Default directory |
|---|---|
| macOS | ~/Library/Application Support/namera |
| Windows | %APPDATA%\Namera |
| Linux | ~/.config/namera |
XDG_CONFIG_HOME, when set, takes precedence on every platform; Namera uses its
namera subdirectory. Credentials are stored in the OS keyring. Imported
session keys are encrypted files under session-keys, protected by keyring secrets.
Changing directories does not migrate keyring entries. Keep your encrypted backup and avoid deleting storage to resolve an authentication error.
Example output uses fixture accounts and hashes, captured with the CLI's output formatters. Plain-text output is shown without terminal colors; your values and relative expiry dates will differ.