scic-cli
A ready-to-use interactive shell client for applications built with
scic-framework.
scic-cli does not implement application business logic. It creates an
independent SCICSession, presents the registered context tree, resolves user
instructions, executes functions, and renders structured results.
Features
- Interactive shell based on
prompt-toolkit. - One independent SCIC navigation session per client.
- Context-aware resource completion.
- Persistent command history.
- Rich tables, JSON, errors, descriptions, and tree rendering.
- Native support for synchronous and asynchronous SCIC functions.
- Built-in navigation and inspection commands.
- Works on Linux, Windows, and macOS.
- Programmatic API and
python -m scic_clilauncher.
Installation
python -m pip install scic-cli
For development:
python -m pip install -e ".[test,build]"
pytest
Application integration
from scic_cli import CLIConfig, SCICCLI
cli = SCICCLI(
scic,
config=CLIConfig(application_name="OpenShell Manager"),
)
raise SystemExit(cli.run())
Inside an existing event loop:
await cli.run_async()
Each SCICCLI creates its own SCICSession, so several CLI, WebGUI, API, or
DesktopGUI clients can share the same frozen SCIC registry without sharing
navigation state.
Generic launcher
Expose a SCIC object or zero-argument factory from a Python module:
# my_application.py
application = build_scic_application()
Launch it without writing a dedicated CLI entrypoint:
python -m scic_cli my_application:application --name "My Application"
A factory is also valid:
python -m scic_cli my_application:build_application
Shell commands
| Command | Purpose |
|---|---|
help, ? |
Show help |
ls |
List the active context |
cd <context> |
Enter a child context |
back, .. |
Move to the parent context |
root, / |
Return to the root context |
pwd |
Print the active context path |
describe [path] |
Describe a context or executable |
tree |
Render the complete registry tree |
clear |
Clear the terminal |
exit, quit |
Close the shell |
Any other line is forwarded unchanged to SCICSession.execute().
Example:
scic > ls
scic > cd math
scic/math > add 20 22
42
scic/math > describe add
scic/math > back
scic > exit
SCIC quoting uses the framework parser. Complex values can be passed as JSON
strings where the registered Executable supports them.
Design boundaries
scic-cli owns presentation and interactive navigation. It does not own:
- SCIC registry construction;
- business functions;
- permissions or authentication;
- remote transport;
- HTTP APIs;
- application persistence.
Those concerns remain in the application or in other SCIC clients.
Publishing
Run checks and build distributions:
./check.sh
Publish to TestPyPI:
./publish.sh --test
Publish to PyPI:
./publish.sh
The included GitHub Actions workflow can publish releases using PyPI Trusted Publishing after the repository/environment is configured.
License
MIT.
Metadata
Release files for scic-cli 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| scic_cli-0.1.1.tar.gz | 17.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scic_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.2 kB
Release files / scic_cli-0.1.1.tar.gz
| Download URL | scic_cli-0.1.1.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de40687d741c577d08acd254f600f12dd14ee9540b112413444c24b21324e117
|
|
BLAKE2b-256 checksum How to use checksums |
d712ad30af32407d6a9bc7ec05e3312189f7d0305545d3e1e38a10fd7c53607a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / scic_cli-0.1.1-py3-none-any.whl
| Download URL | scic_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
03438021857943bd97057f0e208145229bfd4411863514449bbf809281b27d0f
|
|
BLAKE2b-256 checksum How to use checksums |
85083ed47708711189aba60e7cffed12619a69583c8b9864288753da14eb01fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for scic-cli 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.