CLI reference

Deploy and manage EOS resources from a terminal or coding agent with the same workspace permissions as the dashboard.

Deploying an app or creating a database from the CLI does not require login. To invite users or manage collaboration in a guest workspace, first sign in and claim it with eos workspace claim WORKSPACE_ID. See guest workspaces for the 14-day deadline and device credential requirements.

The EOS CLI gives developers and coding agents a repeatable way to deploy applications and manage the resources around them. It uses the same identity, workspace boundaries, and resource permissions as the dashboard.

This gives AI-assisted development a path beyond generating code: an agent can provision resources, connect them to an application, deploy it, and help inspect the result. Developers can use the same commands to make the workflow repeatable across iterations. Administrative command coverage is described below.

Install or update the CLI, then use its current help as the command reference:

curl -fsSL https://enterprise-os.stacksync.ai/downloads/install.sh | sh
eos update
eos --version
eos --help

The tables below focus on common workflows. Capitalized values such as WORKSPACE_ID and KEY_ID are placeholders for IDs returned by EOS. Append --json to supported data commands when scripting.

eos auth login
eos auth status
eos workspace list
eos workspace switch WORKSPACE_ID
eos workspace current

Follow the browser sign-in URL. Select the workspace explicitly before managing resources. eos auth logout removes this endpoint's account sign-in while preserving any unclaimed guest credential and guest workspace selection; it does not delete cloud resources.

Applications and deployments

Command	Purpose
`eos app list`	List applications you can access.
`eos deploy --dry-run --project=partner-portal`	Inspect the planned deployment without uploading.
`eos deploy --project=partner-portal`	Build and deploy the current directory.
`eos deployment versions partner-portal`	Inspect deployment history.
`eos deployment logs DEPLOYMENT_ID`	Read deployment build and rollout output.
`eos deployment variables DEPLOYMENT_ID`	Retrieve version variables; output can contain secrets.
`eos deployment download DEPLOYMENT_ID ./source.zip`	Download retained source.
`eos app delete partner-portal`	Delete an app after exact-name confirmation.

Deployment flags include --variable=KEY=VALUE, --memory=1Gi, --max-instances=5, and --region for a new app. See deployment settings.

Databases

eos database list
eos database create 'Partner portal production'
eos database credentials DATABASE_ID
eos database share DATABASE_ID teammate@example.com editor

Creation and credential retrieval return secrets. Capture their output privately. Database deletion requires both the ID and exact display name and permanently removes its data.

AI inference

eos inference --help
eos inference models
eos inference keys list
eos inference keys create 'Support assistant' --limit 100 --every 1 --unit months
eos inference logs KEY_ID --json
eos inference usage

Use STACKSYNC_AI_KEY for eos inference chat; management commands use EOS sign-in. Key creation returns a secret once. See AI inference for model selection, budgets, and revocation.

Storage

eos storage --help
eos storage buckets list
eos storage buckets create 'partner-documents' --region EU
eos storage keys create BUCKET_ID 'Portal backend' --scopes read,write,list

File commands use the bucket key in STORAGE_API_KEY:

eos storage upload ./contract.pdf partners/acme/contract.pdf
eos storage objects list --prefix partners/
eos storage download partners/acme/contract.pdf ./contract.pdf

Bucket and key management use EOS sign-in. See storage API access for scopes and upload behavior.

eos workspace users --json
eos workspace groups --json
eos workspace groups create 'Operations' --json
eos workspace groups add GROUP_ID user USER_ID
eos access list apps APP_ID --json
eos access grant apps APP_ID group GROUP_ID operator
eos access revoke apps APP_ID group GROUP_ID

Resource sharing requires Owner; group management requires workspace Admin. See access and permissions for recipient types and inherited access.

Use EOS with a coding agent

eos skill
eos skill save

The published EOS skill provides the current agent workflow. Saving it makes that workflow available in the project. Let the agent use CLI help to discover commands as EOS evolves.

Core resource workflows can be automated through the CLI. Some administrative actions, including changing app runtime presets, inviting workspace users, and editing the workspace model policy, currently use the dashboard or documented APIs rather than dedicated CLI subcommands.

Troubleshooting

Symptom	Next step
Authentication required	Run `eos auth login` again.
Resource missing	Check the selected workspace and your direct or group grants.
Command unavailable	Run `eos update`, then inspect `eos --help` or the product subcommand's help.
Deployment fails	Read its deployment logs and check the manifest, dependencies, start command, and runtime port.
Storage upload conflicts	Choose a new path or inspect the existing object; uploads do not overwrite.
Inference allowance exceeded	Check the key's remaining and reserved allowance and its reset time.

Use the actual URLs and IDs returned by EOS. Do not infer a resource ID or construct an app URL from its display name.

Open your selected workspace with eos open. Dashboard links include /workspace/{workspace_id} so copied links retain their context. See workspace URLs and opening EOS.

Sign in and choose a workspaceCopy Anchor Link

Applications and deploymentsCopy Anchor Link

DatabasesCopy Anchor Link

AI inferenceCopy Anchor Link

StorageCopy Anchor Link

Sharing and groupsCopy Anchor Link

Use EOS with a coding agentCopy Anchor Link

TroubleshootingCopy Anchor Link

On this page