​
CLI Usage

The AIUS CLI is a terminal interface for data work. The agent loop runs through AIUS; the CLI renders the conversation, executes approved tools locally, and pauses when your input is needed.

​
Installation

curl -fsSL https://dev.aius.co/install.sh | bash
See Installation for platform details.

​
Sign in

The recommended flow is: 
aius auth login
AIUS prints a short code and approval URL, opens that URL when possible, and waits for browser approval. The printed link can be opened on another device, which also works for SSH or headless machines. Sign in with Google or email/password in the browser. If your account belongs to more than one workspace, the approval page asks which workspace this terminal should use. With one accessible workspace it is bound automatically. Teammates get independent credentials even when they share the same workspace and budget. Email/password login is also available directly: 
aius auth login --email you@company.com
Omit --password to receive a secure password prompt. To create an account from the terminal: 
aius auth register
The product has no paste-key login or API-key dashboard. AIUS stores the browser- or password-issued terminal credential locally with restricted file permissions; it never stores your password. Useful auth commands: 
aius auth status
aius auth logout
For the restricted dev environment, put the global flag before the command: 
aius --dev auth login

​
Start work

Run aius from the folder you want it to work in: 
cd /path/to/work
aius
A folder with meaningful project/data content can enter the structured data pipeline; an empty folder starts general work mode. You can explicitly request the pipeline with: 
aius --mode process
AIUS surveys the structure it finds. A fixed context/ plus data/ layout is not required.

​
Run CLI commands from chat

You can type these commands directly into the AIUS chat prompt. AIUS runs them locally without asking the model to interpret them and places their output in the conversation: 
aius project list
aius auth status
aius artifacts list
Project create, rename, and unlink are also available from chat when all required arguments are present. AIUS shows an explicit confirmation before it runs them—for example: 
aius project create --name "Q4 churn"
aius project rename "Retention analysis"
aius project unlink
Delete and reset commands are intentionally terminal-only. Run those in a separate terminal so AIUS can perform its full destructive-action confirmation. Other interactive commands, including login and logout, are terminal-only too.

​
Common options

aius --continue
aius --session <id>
aius --dev
aius --reset
aius --delete
aius --log-level DEBUG
aius --print-logs
--reset rewinds local synced state while preserving the remote project and your login. --delete removes the remote project and resets its local runtime state; it requires explicit project-name confirmation. To leave a long conversation behind without resetting the project, type /clear in the TUI. AIUS opens a new empty chat in the same project while keeping the previous transcript in session history and preserving every file, artifact, result, and project setting. If an agent run or tool is still active, pause it with Esc or /pause before clearing the chat. For retained conversations from another device, use /shared-sessions in a linked project. Sharing is an explicit per-device, per-project choice; see Shared Sessions for consent, access, and retention. The model is selected by AIUS. You do not pass a client-side model or provider key.

​
Update

aius update
aius update --check
aius update <version>
aius update --force
Updating preserves the locally stored login. On Windows, rerun the installer if the running executable cannot replace itself.

​
Security

  • Local shell and file actions are governed by permission prompts.
  • The terminal credential is stored with restricted permissions.
  • A removed workspace member’s credential is rejected immediately by the live membership check, even if cleanup delivery is temporarily unavailable.
  • A temporary membership-service problem is reported as retryable; it never becomes an unbilled run.