Skip to main content

outo-models-cli

omc — the user-facing command-line client for self-hosted outo-models servers. Hugging Face CLI surface, adapted to a self-hosted multi-server world.

Install

pip install outo-models-cli

Both omc and outo-models-cli console scripts are installed.

Quickstart

# 1. Log in (prompts for a PAT, masked)
omc auth login --server https://models.example.com

# 2. Verify
omc auth whoami

# 3. Create a model repo
omc repo create my-model --kind model --public --description "My first model"

# 4. Browse the tree
omc ls alice/my-model

# 5. Download everything
omc download alice/my-model --local-dir ./my-model

# 6. Upload a folder
omc upload alice/my-model ./checkpoints --path-in-repo weights --message "v1"

Files larger than 100 MiB are uploaded through Git LFS automatically; the CLI partitions the input set, runs the LFS batch + PUT dance for each large file, and commits the resulting pointer text alongside any small files in a single commit. No git lfs track setup is required on the user side.

Commands

omc auth login    --server <url> [--token PAT] [--set-default]
omc auth logout   [--server <url>]
omc auth whoami   [--server <url>]
omc auth status

omc repo create   <name> [--kind model|dataset|space] [--public|--private]
omc repo delete   <owner>/<name> [--kind ...] [--yes]
omc repo list     [--owner ...] [--kind ...]

omc ls            <owner>/<name> [--path subdir] [--revision main]
omc download      <owner>/<name> [--revision main] [--include ...]
                                       [--exclude ...] [--local-dir ./x]
                                       [--max-workers 8]
omc upload        <owner>/<name> <local-path> [--path-in-repo subdir]
                                       [--message ...]

Every command accepts --server <url> to override the default target.

Environment variables

  • OMC_SERVER — overrides the default server URL.
  • OMC_TOKEN — supplies the bearer credential directly (highest priority).
  • OMC_CONFIG_DIR — overrides the config directory (defaults to $XDG_CONFIG_HOME/omc or ~/.config/omc).

Configuration

Credentials are stored at ~/.config/omc/config.json with mode 0600. The file maps each known server URL to its bearer token; the first login becomes the default target.

License

Apache-2.0.

Metadata

Release files for outo-models-cli 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for outo-models-cli 0.2.3
File Size Uploaded Provenance Actions
outo_models_cli-0.2.3.tar.gz 76.3 kB With provenance Details for outo_models_cli-0.2.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for outo-models-cli 0.2.3
File Interpreter ABI Platform Actions
outo_models_cli-0.2.3-py3-none-any.whl Python 3 none any Details for outo_models_cli-0.2.3-py3-none-any.whl

Total release size: 131.9 kB

Release files / outo_models_cli-0.2.3.tar.gz

Download URL outo_models_cli-0.2.3.tar.gz
Size 76.3 kB
Tags Source
SHA-256 checksum
How to use checksums
09754f23b83fb5e753cf01608d27f7804a1e0e3b652993ed317d1515138f0d18
BLAKE2b-256 checksum
How to use checksums
7dcbcc3b5e59103922baa87ed79e18513ca8e461b737b90129b17808189fffeb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

Release files / outo_models_cli-0.2.3-py3-none-any.whl

Download URL outo_models_cli-0.2.3-py3-none-any.whl
Size 55.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1ca0b4d032d165008430c05661050cc9fb2e21a9d97242d828ece430d4d285cb
BLAKE2b-256 checksum
How to use checksums
162b4396200f7f367ee0678de1b709b78571f3f0d4086e88af4b92c48e3fbd45
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

Security for outo-models-cli 0.2.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for outo_models_cli-0.2.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page