Lokindi CLI
Run every Lokindi service — standard & custom encryption, semantic encoding, steganography, Auralith image→audio, storage — straight from your terminal (cmd / PowerShell / macOS Terminal / Linux shell).
pip install lokindi-cli # or: pipx install lokindi-cli
lokindi login # then pick a service by number, or:
lokindi --help # commands are built from the server manifest
lokindi encrypt standard --content "hello" --package <code> --network <code>
lokindi encrypt file --in ./secret.pdf --package <code> --network <code>
lokindi usage quota
After lokindi login you get an interactive menu of the services your
account unlocks: pick a number (e.g. Encryption), then choose Text
or File. Text input is capped at the platform's per-message character
limit (enforced before the request is sent); files are uploaded and
encrypted server-side. The same flow is available any time via
lokindi services.
Architecture (thin client)
The CLI runs no cryptography locally. It authenticates, fetches a
per-account command manifest from GET /api/v1/cli/manifest/, and
builds its commands dynamically from that manifest. Every command maps
to a REST endpoint on the Lokindi API; the server stays the single
source of truth for behaviour, limits, and billing.
- Auth: JWT Bearer; tokens stored in the OS keyring (Windows Credential Manager / macOS Keychain / Linux Secret Service).
- Config:
~/.lokindi/config.toml(profiles, API base URL). - Manifest cache:
~/.lokindi/manifest.json+ ETag, so--helpworks offline and revalidates cheaply (If-None-Match→ 304).
Static commands (login, logout, whoami, version, config) are
built in; only service commands come from the manifest.
Development
- Layout & internals: see ARCHITECTURE.md.
- Editable install:
pip install -e .(installslokindiandlokindi-admin). - Debugging a missing-commands
--help: setLOKINDI_DEBUG=1to see why the dynamic manifest didn't load (offline / not logged in). - Switch environments:
lokindi config set-url <url> --profile devthenlokindi --profile dev …(tokens are stored per profile).
Release files for lokindi-cli 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lokindi_cli-0.1.0.tar.gz | 217.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lokindi_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 493.7 kB
Release files / lokindi_cli-0.1.0.tar.gz
| Download URL | lokindi_cli-0.1.0.tar.gz |
|---|---|
| Size | 217.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2a01cef5a4430704d56a9ec225261a7d8c4e81ad22c35dc8f3b8f624616d495
|
|
BLAKE2b-256 checksum How to use checksums |
a76724961115c81f20660a6c5fa87964e6332f1c0df4ca3724d4ed3838f0914d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Release files / lokindi_cli-0.1.0-py3-none-any.whl
| Download URL | lokindi_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 276.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56082110455a0b227be610589c1787411541a582f9a5049f0a1c71cbbbfe7bfe
|
|
BLAKE2b-256 checksum How to use checksums |
a05af3da1ea68c8dc3a094ee0243312dd8b0a41ecf1ff36ef3ecb6f3147cff18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|