514-cli
514 CLI Basics
The 514 CLI manages authentication, projects, and deployments on the hosting platform.
Command shape: 514 <resource> <action> [args] [flags]
All commands accept --json for machine-readable output and -o <ORG> to override the active organization.
1. Authentication
Log in (opens browser for OAuth):
514 auth login
Check who's logged in:
514 auth whoami --json
Log out:
514 auth logout
Organizations
List orgs the user belongs to:
514 org list --json
Switch the active org:
514 org switch <ORG>
2. Projects
List projects in the active org:
514 project list --json
Linking a project
If the user already has a local repo and a 514 project, link them:
514 project link [ORG/PROJECT]
When ORG/PROJECT is omitted the CLI shows an interactive picker. Use --force-relink to switch to a different project.
Setting up a project from scratch
Clone a 514 project and set up the local dev environment:
514 project setup <ORG/PROJECT>
Useful flags:
--path <DIR>— parent directory for clone--branch <NAME>— create a feature branch--no-branch— skip branch creation--run install— run dependency install after clone--push— push the branch after creation
3. Deployments
List deployments for a project:
514 deployment list --project <ORG/PROJECT> --json
Useful flags:
--status <STATUS>— filter by status (repeatable)--branch-id <ID>— filter by branch--limit <N>— number of results (default: 20)
When running inside a linked repo, --project can be omitted.
4. Docs
Search the 514 documentation from the terminal:
514 doc search <QUERY>
Show a specific page:
514 doc show <PAGE>
List all available pages:
514 doc list --json
5. Updating the CLI
514 cli update
Quick reference
| What | Command |
|---|---|
| Log in | 514 auth login |
| Who am I | 514 auth whoami --json |
| Log out | 514 auth logout |
| List orgs | 514 org list --json |
| Switch org | 514 org switch <ORG> |
| List projects | 514 project list --json |
| Link project | 514 project link [ORG/PROJECT] |
| Set up project | 514 project setup <ORG/PROJECT> |
| List deployments | 514 deployment list --project <ORG/PROJECT> --json |
| Search docs | 514 doc search <QUERY> |
| Update CLI | 514 cli update |
More from 514-labs/agent-skills
clickhouse-best-practices-ts-py
Use when designing, implementing, reviewing, or optimizing MooseStack data models, ClickHouse schemas, queries, indexes, materialized views, or ingestion configs — including during greenfield authoring when schema-design or performance choices need guidance. When invoked, pick the 1-2 rules directly relevant to the immediate decision and apply them inline while you continue to write code. Do NOT pause to read six rule files and emit a "Rules Checked / Findings" audit template unless the user explicitly asks for a formal review or audit.
19514-debug
>
4514-perf-optimize
>
4moose-basics
>
3moosestack-clickhouse-best-practices
MUST USE when reviewing MooseStack data models, ClickHouse schemas, queries, or configurations. Contains 28 rules with MooseStack TypeScript/Python examples. Always read relevant rule files and cite specific rules in responses.
3514-production-rollout-plan
>
1