CLI reference
The magmell CLI stores user configuration locally and can also use environment variables for
non-interactive operation.
Global behavior
Section titled “Global behavior”magmell <command> [options]| Option | Purpose |
|---|---|
--json |
Print machine-readable JSON on supported commands |
--team ID |
Select a team for this command |
Environment variables override stored configuration:
| Variable | Purpose |
|---|---|
MAGMELL_BASE_URL |
Gateway origin, normally https://api.magmell.siloga.cloud |
MAGMELL_API_KEY |
Team API key for non-interactive use |
Authentication
Section titled “Authentication”magmell login [--url URL] [--email EMAIL] [--password PASSWORD]Authenticates a user and saves the access token. Omitting email or password prompts interactively.
Avoid --password in normal use because shell history can retain it.
whoami
Section titled “whoami”magmell whoami [--json] [--team ID]Displays the signed-in user and team memberships. This command requires a user session; an API key cannot substitute for one.
Deployments
Section titled “Deployments”deploy
Section titled “deploy”magmell deploy <dir> --name NAME --version VERSION \ [--requirements a,b] [--setup COMMAND]... [--wait] [--json] [--team ID]Reads the top-level files in dir, creates a handler deployment, and optionally waits for its build.
When --requirements is omitted, a top-level requirements.txt is installed automatically.
--setup is repeatable and commands execute in the order provided before Python dependencies.
deployments list
Section titled “deployments list”magmell deployments list [--limit N] [--json] [--team ID]Lists active deployments for the selected team.
magmell run <handler|deploymentId> \ [--version VERSION] \ [--input JSON | --input-file FILE] \ [--wait] [--json] [--team ID]A non-UUID argument is a handler name. --version applies only to names and is ignored with a
deployment ID. Input defaults to {}.
runs list
Section titled “runs list”magmell runs list [--deployment HANDLER] [--limit N] [--json] [--team ID]Lists recent runs, optionally filtering across all versions of one handler.
runs events
Section titled “runs events”magmell runs events <handler>#<number> [--level LEVEL] [--json] [--team ID]magmell runs events <runId> [--level LEVEL] [--json] [--team ID]LEVEL is one of debug, default, warning, or error.
Secrets
Section titled “Secrets”secrets set
Section titled “secrets set”magmell secrets set <handler|deploymentId> KEY=VALUE [KEY=VALUE ...] [--team ID]Replaces the deployment’s complete secret set. A name selects its latest active version; use a deployment ID to target an exact older version.
secrets list
Section titled “secrets list”magmell secrets list <handler|deploymentId> [--json] [--team ID]Lists configured secret names. Values are never returned.
API keys
Section titled “API keys”magmell keys create <name> [--json] [--team ID]magmell keys list [--json] [--team ID]The full key is shown only once when created. Save it immediately in your secret manager. Key revocation is currently available through the web console or SDK.
Team members
Section titled “Team members”magmell members list [--json] [--team ID]magmell members add <email> [--role member|owner] [--json] [--team ID]magmell members set-role <email|userId> <owner|member> [--team ID]magmell members remove <email|userId> [--team ID]magmell members leave [--team ID]Adding, changing, or removing other members requires the owner role. Membership commands require a user session rather than an API key.
Exit behavior
Section titled “Exit behavior”0: command completed successfully1: API or operational failure2: invalid CLI usage
When run --wait observes a failed run, it prints the failure and exits 1.