Vega devmode login / vega devmode enable-device not recognized — "Unknown arguments: devmode, login" on SDK 0.24.x

Vega Open Beta Bug Reports
1

Device: Fire TV Stick, Vega OS 1.2

SDK versions tested (both from the official portal installer, same Amazon developer account):

  • 0.24.12112
  • 0.24.9914

vega devmode login

returns:

Vega CLI argument error: Unknown arguments: devmode, login

Vega SDK CLI
Usage: vega [options] | [command] [command options]

Commands:
vega build [options]
vega clean
vega device
vega exec [command] [args…]
vega platform
vega project
vega run-app [appId]
vega which
vega virtual-device

There is no devmode (or dev) top-level command in either installed build. I also checked:

  • vega update → “Unknown argument: update” (also documented in the community FAQ, also missing)
  • vega --version → prints a single version string only (e.g. 0.24.9914), not separate CLI/SDK versions as referenced elsewhere
  • vega device -h → no pairing/enrollment subcommand (checked set-dev-mode, enable-dev-mode, pair, enroll, add, login — none exist)

Interestingly, the bundled KeplerCLI package (packages/KeplerCLI/…/dist/cli.js) does contain internal GetDevMode/SetDevMode classes in @amzn/kepler-device-manager, but nothing exposes them as a public vega/kepler command in this distribution.

Both SDKs were downloaded via the personalized install command from Amazon Developer Sign-In (–directed-id=amzn1.account.AH3HHVVFIM423T6OM5KFOUIUVOJA), so this should be the standard public distribution for a regular developer account.

Question: Is vega devmode gated behind a vendor/account flag that hasn’t been enabled for all accounts yet, or is this a packaging regression? Is there any currently-working way (CLI or portal) to enable Developer Mode on a Vega OS 1.2 Fire TV Stick for a regular developer account today?

Any pointers appreciated — happy to share full vega -h / vega device -h output or logs if useful.

4

Hi @Alejandro_Garcia,

Welcome to Amazon Developer Community!!

Thanks for the detailed write-up. To answer your main question directly: devmode is not gated behind a vendor or account flag - vega devmode login and vega devmode enable-device --code <6-digit code> are the current, public commands for all developer accounts. See Enable Developer Mode ( Enable Developer Mode - Amazon Vega Docs ) (steps 9 and 11) and the Aug 6 announcement ( Authenticate and enable Developer Mode from the CLI ).

A couple of things in your output suggest the vega CLI currently on your PATH isn’t the current Vega
Developer Tools CLI:

Could you share the following so we can confirm what’s on your PATH:

  1. which vega
  2. vega --version
  3. vega -h

In parallel, the documented fix is to reload your shell and/or reinstall the CLI:

  1. Run source ~/vega/env (or open a new terminal), then re-check vega --version. The CLI installs to ~/vega/bin.
  2. If it still shows a single line, reinstall/update via Install the Vega Developer Tools (Install the Vega Developer Tools - Amazon Vega Docs) (the “Update Existing Installation” tab), then open a new terminal.
  3. Once vega --version shows both lines, vega -h should list devmode, and:
vega devmode login
vega devmode enable-device --code <6-digit code>

If devmode is still missing after that, send the three outputs above and we’ll dig in further.

Thanks for helping us improve the Vega platform.

Best regards,
Aishwarya

5

Thanks for the pointers. I retried all three in a fresh terminal with no leftover environment from the install shell:

$ which vega
~/vega/sdk/0.24.12112/bin/vega
$ vega --version
0.24.12112
$ vega devmode login
Vega CLI argument error: Unknown arguments: devmode, login

~/vega/env doesn’t exist in this install, and ~/.zprofile already puts $KEPLER_SDK_PATH/bin on PATH. I don’t think this is a shell or PATH issue.

Possible cause: bin/vega hands every subcommand except build/native to dutyfree-vega, which runs the bundled KeplerCLI cli.js. Both SDK builds I have installed ship the same KeplerCLI build, and it’s the only one under packages/KeplerCLI/:

$ shasum -a 256 ~/vega/sdk/*/packages/KeplerCLI/KeplerCLI-2.0.29145.0/AL2_x86_64/DEV.STD.PTHREAD/build/kepler/dist/cli.js
68ea3f3ebd58195c106f92365bdcd7384650c4339e00acb8a9334fc291d1d4cf  .../0.24.12112/.../cli.js
68ea3f3ebd58195c106f92365bdcd7384650c4339e00acb8a9334fc291d1d4cf  .../0.24.9914/.../cli.js

Both files are identical and were built 2026-08-04. Bumping the SDK version doesn’t change the CLI.

As I mentioned in my first post, the bundle does contain @amzn/kepler-device-manager with getDevMode/setDevMode and validateDevModeAndGetInfo. Nothing wires them to a command, though. Here’s what this build registers:

$ vega --help
Commands:
  vega build, clean, device, exec, platform, project,
  run-app, which, virtual-device

$ vega device --help
  copy-from, copy-logs, copy-to, doctor, get-log-info, info,
  install-app, installed-apps, installed-packages, is-app-installed,
  is-app-running, is-connected, is-port-forwarded, launch-app, list,
  reboot, run-cmd, running-apps, shell, start-log-stream,
  start-port-forwarding, stop-log-stream, stop-port-forwarding,
  terminate-app, uninstall-app

The Enable Developer Mode doc says it was last modified August 7, 2026. That’s three days after this cli.js build. It looks like the docs describe a KeplerCLI build that hasn’t reached the public installer.

Could you confirm which KeplerCLI build should include devmode? Then I can tell whether it’s just not available yet for regular accounts at developer.amazon.com/kepler/open/sdk, or whether something is wrong on my end.

Environment: macOS on Apple Silicon (arm64). Happy to attach the full help output or package manifest if useful.

6

Hi @Alejandro_Garcia ,

Thanks for the thorough follow-up - the SHA-256 digests and the which vega output are exactly what we needed, and they actually point to the root cause.

The key insight: devmode is a Vega CLI command, not a per-SDK KeplerCLI command. That’s why bumping the SDK version (0.24.9914 → 0.24.12112) never adds it - both ship the same per-SDK cli.js, and devmode/update were never meant to live there.

Your which vega resolves to ~/vega/sdk/0.24.12112/bin/vega - that’s the per-SDK launcher, which only exposes SDK-scoped commands (build, clean, device, exec, …). The commands you need (devmode, update) belong to the Vega CLI / SDK Manager, which installs separately to ~/vega/bin. Two signs you’re not on that CLI yet:

  • vega --version prints a single line - the current Vega CLI prints two (Active SDK Version + Vega CLI Version).
  • ~/vega/env doesn’t exist - the current installer creates it.

So this isn’t account-gating or a packaging regression - it’s a stale/incomplete Vega CLI install.

Here’s how to get onto the correct CLI:

Step 1 - (Re)install the Vega Developer Tools CLI Close VS Code, then run:

curl -fsSL https://sdk-installer.vega.labcollab.net/get_vvm.sh | bash && source ~/vega/env

This installs the Vega CLI to ~/vega/bin, creates ~/vega/env, and updates your shell profiles. It’s the “Update Existing Installation” flow and is safe to run over your existing setup.

Step 2 - Open a new terminal Open a fresh terminal (or source ~/vega/env) so the updated PATH and env take effect.

Step 3 - Verify you’re on the correct CLI

which vega          # expect: ~/vega/bin/vega   (NOT ~/vega/sdk/.../bin/vega)
vega --version      # expect TWO lines: Active SDK Version + Vega CLI Version
vega -h             # expect to see 'devmode' and 'update' listed

If which vega still points at ~/vega/sdk/…/bin/vega, it’s a PATH-ordering issue - make sure ~/vega/bin comes before $KEPLER_SDK_PATH/bin in your ~/.zprofile, then open a new terminal and recheck. (vega update is the supported way to keep this CLI current going forward.)

Step 4 - Enable Developer Mode On the Fire TV: Settings → My Fire TV → Developer Options → Developer Mode, select Continue, and note the 6-digit code on screen. Then on your machine:

vega devmode login
vega devmode enable-device --code <6-digit code>

login opens a browser for Amazon Developer Account auth; enable-device enables the device and it reboots automatically. After reboot, confirm with:

vega device list

If devmode is still missing after Step 3, please share your new which vega, vega --version, and vega -h output and we’ll dig in further.

Reference docs

Best regards,
Aishwarya