MilkStraw AI CLI for authentication, onboarding, and stack management.
Before running milkstraw setup, you need the AWS CLI installed and configured with credentials that have access to your AWS Organization management account.
Configure credentials using one of:
aws configure # Access key + secret
aws configure sso # SSO login (recommended)Verify your credentials are working:
aws sts get-caller-identityIf using SSO, make sure your session is active:
aws sso login --profile <your-profile>npx @milkstraw/cli setup| Command | Description |
|---|---|
milkstraw login |
Interactive browser login |
milkstraw logout |
Revoke token and clear local auth |
milkstraw setup |
Complete onboarding and deploy stacks |
milkstraw status |
Check deployment status |
milkstraw update |
Update deployed stacks to latest templates |
milkstraw org list |
List accessible organizations |
| Option | Description |
|---|---|
--org <id> |
Specify organization ID |
--aws-profile <name> |
Override the AWS named profile |
--json |
Output as JSON |
--quiet |
Output data only |
--markdown |
Output as Markdown |
--verbose |
Enable verbose output |
--agent |
Agent-safe mode (no prompts, no spinners) |
| Variable | Description |
|---|---|
MILKSTRAW_ORG |
Default organization ID |
MILKSTRAW_AWS_PROFILE |
Default AWS profile name |
The CLI uses the AWS SDK for JavaScript v3 credential provider chain.
Without --aws-profile, credentials are resolved in this order:
- Environment variables:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_SESSION_TOKEN - SSO token cache at
~/.aws/sso/cache - Shared credentials file at
~/.aws/credentials(default profile) - Shared config file at
~/.aws/config - ECS container or EC2 instance metadata
With --aws-profile <name> (or MILKSTRAW_AWS_PROFILE), the SDK skips environment variables and uses the named profile from ~/.aws/config and ~/.aws/credentials.
Tokens are stored at ~/.config/milkstraw-cli/token. Login uses the OAuth device code flow via browser.
npm install
npm run build
node bin/milkstraw.js --help