@glassly/cli
The glassly command: the one CLI for developing, releasing, and publishing
Glassly miniapps. Install it globally (bun add -g @glassly/cli). Scaffolded
projects also carry it as a dev dependency, and inside a project the global
glassly hands off to that copy, so each project runs the version it pins.
glassly update updates both the project's Glassly packages and the global
command, and the CLI prints a notice once a day when either is behind
(GLASSLY_NO_UPDATE_CHECK=1 turns that off).
The project-side commands (dev, build, pack, release, manifest,
permission, hardware, schema) are implemented in
@glassly/miniapp-cli,
which this package wraps. The account and Store commands (login, org,
miniapps, releases, listing, media, publish) talk to the Glassly
Developer Console.
Bun-only. This CLI ships as TypeScript and runs under Bun (
#!/usr/bin/env bun). Usebun/bunx, notnpx/Node.
Install
bun add -g @glassly/cli
glassly --help
Or run without installing:
bunx @glassly/cli --help
Run without hardware
glassly sim # desktop simulator: glasses display, input controls, phone page
glassly sim --detach # start it in the background and return once ready
glassly sim screen # what is on the glasses, one element per line
glassly sim screenshot a.png # the display as a PNG
glassly sim tap # also double-tap, hold, swipe-up, swipe-down, look-up, button
glassly sim say "hello" # speech, delivered as a transcription
glassly sim logs # console output from both layers
glassly sim stop
The subcommands talk to the simulator running for the current project, so a
script or a coding agent can drive a miniapp end to end. glassly sim --help
lists all of them.
Develop and test on a phone
glassly dev # hot-reload dev server + QR; signed dev identity when logged in
glassly release # build, pack, and serve a QR that installs on phones over LAN
glassly build # build both layers into dist/
glassly pack # production-build and zip into build/<pkg>-<version>.zip
glassly manifest # interactive miniapp.json wizard
glassly permission add MICROPHONE
glassly hardware add DISPLAY REQUIRED
glassly schema print # the miniapp.json JSON Schema
dev and release take --qr sm|md|lg and --qr-output <path>; dev --no-iroh
prints a LAN-only QR. Every
project command takes --cwd <path> to run against another directory.
Publish to the Glassly Miniapp Store
glassly login # sign in to your Glassly developer account (opens a browser)
glassly publish # build, pack, sign, upload, and submit for review
glassly miniapps list # miniapps owned by your org
glassly releases list <packageName>
glassly listing set <packageName> --tagline "..."
glassly media add <packageName> ./store/screenshots/01.png
Run glassly <command> --help for the full option set.
Report a gap or bug
glassly feedback "No simulator for the R1 ring"
Sends your text to the Glassly team with the CLI, SDK, and runtime versions and the miniapp package name attached. No login needed; when signed in, the report carries your account. Coding agents: use it when you hit a missing feature or a docs/source mismatch. See https://docs.glasslyos.com/app-devs/reference/feedback.
Backend selection
The CLI talks to the production Glassly backend and Developer Console by
default; nothing needs configuring. To point it at another deployment, set
CLOUD_CORE_URL, CLOUD_CONSOLE_URL, and that backend's public WorkOS
AuthKit client id in WORKOS_CLIENT_ID. Logins and the bundle signing key are
stored per backend URL in ~/.glassly/cli/, readable only by your user;
glassly logout removes the login.
Your org, releases, and API keys are managed in the Developer Console at
https://console.glassly.ai. For CI or a coding agent without a browser, create an
API key on its API keys page and set it as CLI_TOKEN instead of running
glassly login.