RepOS (repos-cli)
RepOS is a multi-panel, REPL-based command environment that runs inside your terminal. It acts as a lightweight “operating layer” on top of your shell, letting you organize commands into panels (Git, OS, Python, Docker, etc.), store aliases persistently, and move between contexts without shell scripts or dotfile sprawl. This package installs the RepOS CLI.
Installation
pip install repos-cli
Python 3.10+ required.
Usage
Start RepOS:
repos-cli
You’ll enter the root REP panel.
Create project level database:
repos-cli init
You’ll enter the root REP panel. This takes no other arguments and will create a .repos file in the current directory.
Exit at any time with:
ZZ
What RepOS Does
- Provides a panel-based REPL inside your terminal
- Stores aliases persistently using SQLite
- Executes real shell commands (not simulations)
- Tracks command history and execution results
- Uses YAML configuration for system and panel defaults RepOS is not a shell and does not replace Bash/Zsh — it runs on top of your existing shell.
Configuration & Defaults
On first run, RepOS initializes a local data directory under:
~/.local/share/repos/
This includes:
- a core SQLite database
- default panel definitions (Git, OS, Python, Node, Docker, etc.)
- system configuration loaded from packaged YAML defaults You can customize panels and aliases from inside RepOS itself.
Project Status
This is an early-stage release focused on establishing the core REPL, execution engine, and persistence model. The interface and internal architecture are still evolving.
Licensing
RepOS is licensed under the Business Source License 1.1 (BSL 1.1).
- Free for personal use and internal development
- Not permitted to be sold or offered as a hosted service before the Change Date
- Automatically converts to Apache License 2.0 on January 1, 2029 See:
LICENSENOTICElegal/directory for commercial licensing and contribution terms RepOS™ and TriFactoria™ are trademarks of Andrew Blankfield.
Support
If you find RepOS useful and would like to support its continued development, donations are welcome. GitHub Sponsors: https://github.com/sponsors/trifactoria
Metadata
Release files for repos-cli 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| repos_cli-0.0.4.tar.gz | 93.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| repos_cli-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 152.1 kB
Release files / repos_cli-0.0.4.tar.gz
| Download URL | repos_cli-0.0.4.tar.gz |
|---|---|
| Size | 93.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dddef06a1666f05f089c4ec082d4bd52074b83fc8d93426f769cdb3624adfe2
|
|
BLAKE2b-256 checksum How to use checksums |
d8a250f6a39a55a9d5b9f5d4f297b7550d3b3212517ecf2f71b0f01073a467e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 18, 2025.
Transparency logRelease files / repos_cli-0.0.4-py3-none-any.whl
| Download URL | repos_cli-0.0.4-py3-none-any.whl |
|---|---|
| Size | 58.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da7521efbfee36b6f8e6e769f11549ed863cc53896a1366315dbf222b5198d45
|
|
BLAKE2b-256 checksum How to use checksums |
c5d6d5793779c9ded66f42634444a28198f84acc9307769948cafdf723fd4bd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 18, 2025.
Transparency log