nebyoulous CLI covers the parts of the workflow that live on your disk:
inspecting camera cards, managing integration sets, and syncing frames. It
also runs an MCP server over stdio.
Install
The CLI needs Node.js and npm. Releases are built and tested on Node 22. Eachcli-v<version> GitHub release has an npm tarball. The repository is private
for now, so use the GitHub CLI to download the latest one:
nebyoulous login.
Tokens go in the OS keychain through
keytar. macOS and Windows work out of
the box. On Linux, install libsecret (sudo apt install libsecret-1-0 on
Debian and Ubuntu).Sign in
1
The CLI prints a code and opens your browser
It opens the approval page on
www.nebyoulous.space and shows a short
code.2
You approve it in the web app
Sign in if needed, check that the code matches, and approve.
3
The CLI stores the session
The CLI saves an access token and a refresh token in the keychain and
refreshes them as you use it.
Check the session with
nebyoulous whoami. nebyoulous logout revokes the
refresh token and clears the keychain entries.
Conventions
- Topics use a colon. Write
integration-sets:list, notintegration-sets list, and don’t put--before a subcommand. --jsonfor scripts. Commands that print results accept--jsonand write machine-readable output to stdout.- Destructive commands confirm.
integration-sets:delete,:delete-folder, and:delete-assetsask you to type a confirmation phrase. Pass--yesto skip it in scripts. - IDs or titles. Most commands take an integration-set UUID.
sync --to-cloudalso accepts an exact title.
Environment variables
The CLI keeps one session at a time. Signing in against another API replaces
your production session.
Commands
Every flag for every command is in the command reference.